Tag Info

New answers tagged

0

Read the FAQ, especially http://www.openbsd.org/faq/faq10.html#locales, where it says: If logging in via xdm(1) add a line such as export LC_CTYPE="en_US.UTF-8" to ~/.xsession before starting the window manager (see the section on customizing X for details). This example enables the Unicode (UTF-8) character set and will also cause applications ...


4

The reason is that in your xterm, ^H is the erase character, and tmux apparently translates the erase character to the corresponding control character (^?) for the terminal it emulates, so that erasing works as expected in cooked mode (for instance, what happens when you just type cat). The translation is needed in case you use a terminal with ^? as the ...


0

Check your tmux key bindings. Tmux - ArchWiki Tip: To mimic screen key bindings copy /usr/share/tmux/screen-keys.conf to either of the configuration locations.


1

Unless you use the mostly experimental support for full RBG-colors in some terminals, you're limited to the indexed 256 color palette provided by the terminal. You're right that terminals may slightly deviate in the exact colors used, and that will be noticeable. If you completely reassign colors (turn red into blue etc.), there's nothing that corrects this ...


0

This happens to me most often when I resize while running a full-screen program that makes use of the alternate screen, such as vim or less. You can tell if this is the case if your scrollback buffer seems to disappear when you run the program, and then reappears when you exit. When resizing while running such a program, the alternate screen is updated with ...


0

You could try the settings I have on my mac for my ~/.vimrc file: """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" " => Colors and Fonts """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" syntax enable colorscheme desert set background=dark " Set extra options when running in GUI mode if has("gui_running") set ...


2

This is likely a readline thing. Add set horizontal-scroll-mode on to your readline configuration (usually ~/.inputrc) and restart the shell or re-read the configuration (usually using Ctrl+X Ctrl+R). If not, then you are out of luck, I'm afraid - the terminal is usually meant to do exactly that, i.e. once the data gets too big, if wraps and gets ...


-1

The cause may be that there is a margin set. This can occur if some curses application has not been terminated properly. In such a case, typing reset will reset the terminal, in particular the margin.



Top 50 recent answers are included