I keep on accidentally typing altgr+space instead of space, which results in a non-blocking space and a compiler error. I have absolutely no need to use the said character in my code other than maybe in unicode notation, so what's the best way to turn this feature of in Eclipse? Alternatively, a system wide disable for it would be fine too.
I'm running Eclipse Mars & Linux Mint 17.1 Mate
this did the trick
setxkbmap -option "nbsp:none"
You should use the command xev to discover what is the keycode for AltGr on your keyboard (mine is 108). After that, you can use the xmodmap:
xmodmap -e 'keycode 108=NoSymbol'
I would then write this command in rc.local so I don't need to run it manually everytime I restart the machine.
Related
Is it possible to enter mark mode(to mark text in Linux terminal) without mouse. In CMD you can ,alt+space+e+k. Can it be done natively without 3th party programs?
Regardless of your terminal you can enable vi mode for you shell, both bash and zsh support this.
A quick one (without installing third party programs) would be to set -o vi in your shell to enable vi and use the shortcuts
If you don't like it you can always come back to emacs: set -o emacs
Recently my bash has often got into strange states I don't understand (debian squeeze system). For example, after starting a new xterm, Control-l prints "^L" on my screen instead of cleaning it. This happens with a "fresh" xterm, with bash as well as with dash (even xterm -e /bin/dash). Also, a reset did never help.
By contrast, after ssh'ing to another box, Control-l does what I expect.
Can somebody make an educated guess for the cause to this very odd behaviour to me (my Unix knowledge can't help out)?
Sorry, I found it out. set -o vi was the culprit, as for bash. As for dash, it's just normal behaviour... Been a hard one.
Check the stty -aoutput and the $TERM variable. $TERM should be "xterm" or "xterm-color"
I am trying to use rxvt on my cygwin w win XP but the terminal appears and disappears. What could be wrong? This is true for all except rxvt-native . I have tried a few commands found online but with no success. I include 2 I have tried:
start C:\cygwin\bin\rxvt.exe -sb -sl 3000 -fg gray -bg black -fn "Lucida Console-14" -e /bin/bash --login -i
.
path C:\cygwin\bin;%path%
ssh-agent rxvt -e bash --login -i
Another problem I am facing is trying to get vi to work in my cygwin bash shell. Setting term to xterm or vt100 does not work. Hitting enter, I see a string 78 or some other issue pops up. I have never modified my .inputrc.
My main issue was trying to get vi to work properly. I just found out that if I run
/etc/postinstall/terminfo.sh.done , I can now navigate properly in vi. The 78 (newline) M still appears but at least I can navigate in vi.
Feb 25 - This problem went away after a few windows updates. Would it make sense to ANSWER my question on the basis that this is longer reproducible?
Can't answer the first question, but have you tried invoking rxvt from its shortcut in the Cygwin folder of the start menu?
Regarding the second question, the TERM variable tells applications what terminal they're running in, so if you set it to 'xterm' while running in the Cygwin console (where normally TERM=cygwin), they'll be sending xterm control sequences that the Cygwin console doesn't understand. So basically: don't do that!
Btw, you might also be interested in Cygwin's mintty package, which is another terminal that doesn't need an X server. Installing it also creates a start menu shortcut in the Cygwin folder.
I would assume you need an X server running.
You could install Cygwin/X
One thing which may not have been clear was that the whole exercise was to get vi to work. vim did not work either at that time. But after some windows update, the problem went away. Closing it...
I have been using Gvim for quite sometime and I like it very much.
There is a problem I am facing with Gvim.
I type "shell" and go to the command line, When I press the up arrow I get some weird
symbols and I am not able to use backspace also.
The version which I am using.
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Mar 19 2009 15:27:51)
Sadly the reason this is not working is because gvim is an editor, not a terminal emulator. When yoy type :shell in gvim, you do not actually get a shell, you get some weak shell emulation. I say 'weak' because that shell emulation does not know how to deal with color codes, clear the screen or much else.
I stick to terminal vim, that way I can either use :shell, or, as is much more common, ^Z to just drop back into my shell to do something ( ^Z == suspend ) That, plus gnu-screen, plus a good shell is all the IDE I want.
Try some wrappers, e.g. Conque Shell : Run interactive commands inside a Vim buffer ;)
vim is not for such complicated things I think. you can do simple shell operation via :! or :shell, However, vim is only a good if not best editor.
What you need can be done in shell-mode of Emacs.
When running a vim instance in gnu screen hitting shift enter in insert mode adds an 'M' and then a newline, rather than just a newline.
Does anybody know what the problem might be, or where to look?
Relevant system info:
Ubuntu 8.04.1
Screen version 4.00.03 (FAU) 23-Oct-06
VIM - Vi IMproved 7.1 (2007 May 12, compiled Jan 31 2008 12:20:21)
Included patches: 1-138
Konsole 1.6.6 (Using KDE 3.5.10)
Thanks to the comments. When checking the value of $TERM I noticed that it was xterm (as expected), but within screen $TERM was set to screen-bce. Setting TERM=xterm after launching screen resolves this issue.
Adding the following to ~/.screenrc solved the problem without having to do anything manually:
term xterm
Missing info from your question:
Where do you run screen and see this issue? Some terminal app (KTerminal, Gnome terminal, virtual console etc) or remote session (eg putty, ssh from another computer)
do a “echo $TERM” and tell us its output
do a “cat -v”, press Shift-Enter, then Enter, then Ctrl-D and then tell us what is output.
First, you could fix your $TERM for within konsole. Install "ncurses-term" and configure konsole to set $TERM=konsole-256color. Then configure screen with "term screen-256color". Or 'konsole' and 'screen', respectively, if that's your preference. Konsole and screen are not xterm and doesn't support everything xterm does, so using incorrect $TERM can lead to bad things.