Search Results

Search found 191 results on 8 pages for 'xterm'.

Page 2/8 | < Previous Page | 1 2 3 4 5 6 7 8  | Next Page >

  • How do I change the color settings in emacs23 running in a terminal emulator?

    - by Anonymous
    I use xterm and set its appearance in ~/.Xdefaults: XTerm*background: paleTurquoise XTerm*foreground: black I also use emacs, but set its appearance differently in ~/.emacs: (set-background-color "black") (set-foreground-color "yellow") I usually run emacs within the terminal emulator with emacs -nw, rather than creating a separate X window. For some reason, this doesn't work properly for emacs23; instead, emacs retains the pale turquoise background of my xterm window. Looking at what's new in emacs23, I noted that: ** When running in a new enough xterm (newer than version 242), Emacs asks xterm what the background color is and it sets up faces accordingly for a dark background if needed (the current default is to consider the background light). So it's a feature, not a bug? Anyway, is there some way that I can I tell emacs23 to ignore the xterm background settings when running in console mode, and use the settings in ~/.emacs instead? I'll also note that: It works fine in emacs23 running in a separate X window (without the -nw option). It worked fine in emacs22; and I'm not really sure whether I need to use emacs23... Running M-x set-background-color within emacs23 -nw has no effect. It's not just xterm: the same problem exists with $TERM=cygwin, for example.

    Read the article

  • How do I change the color settings in emacs23 running in a terminal console?

    - by Anonymous
    I use xterm and set its appearance in ~/.Xdefaults: XTerm*background: paleTurquoise XTerm*foreground: black I also use emacs, but set its appearance differently in ~/.emacs: (set-background-color "black") (set-foreground-color "yellow") I usually run emacs within the terminal console with emacs -nw, rather than creating a separate X window. For some reason, this doesn't work properly for emacs23; instead, emacs retains the pale turquoise background of my xterm window. Looking at what's new in emacs23, I noted that: ** When running in a new enough xterm (newer than version 242), Emacs asks xterm what the background color is and it sets up faces accordingly for a dark background if needed (the current default is to consider the background light). So it's a feature, not a bug? Anyway, is there some way that I can I tell emacs23 to ignore the xterm background settings when running in console mode, and use the settings in ~/.emacs instead? I'll also note that: Running M-x set-background-color within emacs23 -nw has no effect. It works fine in emacs23 running in a separate X window (without the -nw option). It worked fine in emacs22; and I'm not really sure whether I need to use emacs23... It's not just xterm: the same problem exists with $TERM=cygwin, for example.

    Read the article

  • How can I change the color of xterm titlebar?

    - by tellus55
    Hi, I want to automatically change the color of my xterm titlebar. I would like to put code into my .bashrc so that the color changes automatically (say depending on the directory I am in). I know how to change the prompt and also how to change the text displayed in the titlebar. My question is about the color of the titlebar. Right now the color is orangish. I am using Ubuntu. Thanks

    Read the article

  • Perl Tk button widget size vary with different xterm clients

    - by Manu
    Hi, I have a perl/tk script in which I am creating a button widget of height 1. Now when I execute script through citrix xterm client I get button displayed. Again when I execute script now through xterm client in my PC size of button widget differs. Can someone explain why is this happening, and what should I do so that size of button widget remains constant with different xterm clients.

    Read the article

  • How can one make vim change terminal colors?

    - by amn
    I am using command line vim running from an xterm (which runs sh). I have color in vim according to a color scheme I like. The problem is, as usual with 256-color terminals and truecolor color schemes, colors are wrong. Now, I know I can do a gazillion things to fix this, including installing gvim, but I like my terminal. In fact, using xrdb [-merge] .Xresource file, I now actually have xterm override the color values, and the theme now looks perfect. Since, I may be switching to another theme, I need some workflow to have vim actually do what xrdb does - to reset terminal color pallette. Because right now I have to reset color values with xrdb ... first, then launch another xterm to actually use these values, then launch vim from that newly opened xterm to have the exact colors. The way I understood it is that vim color scheme, just as any other terminal application, uses colors by referencing their ids, and X resources set the values themselves. I think I saw somewhere on Internet, that terminal control character sequences can reset actual color values, in fact, I am sure they can - I managed to set my terminal background color at runtime. How would I make vim execute these sequences to match values for the color scheme? And is there any reference to these control sequences, as part of any standard?

    Read the article

  • OS X Terminal lines don't go into scrollback

    - by Steve Madsen
    I have a problem that crops up when using Mac OS X's Terminal (TERM=xterm): sometimes it gets itself into a state where lines that scroll off the top are not added to the scrollback buffer. I'm not using screen or similar; this is a plain bash shell inside a Terminal tab. It doesn't do this immediately after opening a new tab. I believe it is a side-effect of something I've run in the problem tab. My guess is that it has something to do with the xterm emulation, possibly the scroll region. What hasn't worked: Soft and hard reset via the Shell menu Running reset in the tab Is there a reliable way to reset Terminal and/or the xterm state? Can anyone provide a explanation for what's happening, even if the only fix is to close the tab and open a new one?

    Read the article

  • Using screen, commands like less and man don't clear the screen afterwards

    - by Boldewyn
    In contrast to this question I want the clearing of the screen re-enabled for less. It works fine in my xterm terminal under Cygwin/mintty or Gnome Terminal (both xterms). However, when inside a screen session, the clearing of the screen is somehow disabled. I tried several things, like screen -T xterm or putting the autonuke statement in my ~/.screenrc. Also, inside the screen session export TERM=xterm tset has no effect. So, now I'm out of ideas. Any help appreciated.

    Read the article

  • per terminal bell in ubuntu classic

    - by Owen Maresh
    I'm using natty. I'm using classic. I use raw xterms (the latest build, 270, in fact). I've done xset b 100 pactl upload-sample /usr/share/sounds/ubuntu/stereo/message.ogg bell.ogg But I want something more fine grained than this: I want to say "if the bell originated in some particular pseudoterminal make a particular sound, but if it originated in some other particular pseudoterminal, generate some other sound"

    Read the article

  • How can I set a per terminal bell with xterms?

    - by Owen Maresh
    I'm using natty. I'm using classic. I use raw xterms (the latest build, 270, in fact). I've done xset b 100 pactl upload-sample /usr/share/sounds/ubuntu/stereo/message.ogg bell.ogg But I want something more fine grained than this: I want to say "if the bell originated in some particular pseudoterminal make a particular sound, but if it originated in some other particular pseudoterminal, generate some other sound"

    Read the article

  • How to extend selection in gnome-terminal?

    - by tomasorti
    In a terminal I can select a single line, double clicking with the Left Mouse Button. With xterm, I can extend that selection clicking with the Right Mouse Button in the place I want to extend it. Then can I paste the whole selection with the Middle Mouse Button or paste it in other application. In gnome-terminal, it seems I can extend the selection clicking with the Left Mouse Button, but holding at the same time the Shift key. Visually, it seems the selection is done, but when clicking with the Middle Mouse button or pasting in other application, I only get the primary single line selection. How can I get the whole selection under gnome-terminal? Is it possible to use selections in gnome-terminal as xterm does? Cheers, Tomas.

    Read the article

  • Home and End keys in Emacs don't work when run from Tmux

    - by Jan Stolarek
    When I run Emacs from Tmux, the Home and End keys do not work (Home key runs the Search command as if C-s was pressed). The problem started when I added this in my ~/.bashrc file: TERM="xterm" export TERM I've read somewhere that TERM variable should not be set manually but this was the only way I was able to solve problems with colors. Without this setting I got different colors in Emacs when running directly from the terminal and different when running from Tmux. This option caused some of the keys not to work in Emacs when it was run from Tmux, so I added this line to my ~/.tmux.conf: set-window-option -g xterm-keys on This solved problem with all keys except for Home and End. Any ideas how to make these keys work again?

    Read the article

  • Need a remote desktop to a headless server without logging in first

    - by user17971
    I've been using Linux for many years now but only to run servers. Over the last few days I've been struggling with a technical / configuration issue which I hope someone can help with. I've installed / un-installed many packages but just can't figure out what the "right" way of doing this is. The requirement seems simple Server runs Ubuntu 10.04 with xubuntu and SSH (I do NOT want to connect any screen, keyboard or mouse to the server) I have Windows 7 machine with putty on it and logging in to the server using SSH is fine I want to run an xterminal session on my Windows machine. Amongst the things I've tried is VNU but I can't get it to work because I believe you have to login on the server first. Thanks in advance

    Read the article

  • Mac OS X Terminal.app Ubuntu 9.10 SSHD and incorrect keyboard mapping

    - by Jesse
    Does anyone have any Idea how to handle this? I can't stand connecting to certain Ubuntu boxes via Mac OS X because of issues with keyboard layout etc. I have set TERM=vt100 and TERM=xterm-color in Ubuntu .bashrc and also in the Terminal.app advanced preferences and nothing seems to fix this issue. Trying to use arrow keys on slim silver keyboard results in ^[[A etc. From Answer OS X 10.6.4 When I try to run /lib/terminfo/x/xterm-color I get permission denied? Maybe this is the issue?! Regular bash login shell. If I sudo often it works. Which leads me to believe the above permissions problem is the cause. Output from stty -a: $ stty -a speed 9600 baud; rows 47; columns 181; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = M-^?; eol2 = M-^?; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc ixany imaxbel -iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe -echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke

    Read the article

  • 'less' doesn't clear screen after quit

    - by Dana
    The default behavior for 'less' is to clear the screen after quitting. This behavior stopped when I started using: export TERM=xterm Now 'less' leaves the last page I viewed on the screen, and I want to re-enable the default behavior of clearing the screen. Googling this problem I found that people use the following command in their ~/.screenrc: altscreen on I'm not sure if this is a mac-issue but I don't have this command available. I'm using bash shell on Mac terminal. Thanks!

    Read the article

  • How do I ask screen to behave like a standard bash shell?

    - by thornomad
    Just learned about the screen command on linux - it is genius. I love it. However, the actual terminal/prompt in screen looks and behaves differently than my standard bash prompt. That is, the colors aren't the same, tab completion doesn't seem to work, etc. Is there a way I can tell screen to behave just like a normal (at least, normal as in what I am used to) bash prompt ? Additional Information I am connecting via ssh from a Mac (Terminal) to a headless linux box (Ubuntu). After logging in, I have TERM=xterm-color and when I run screen I have TERM=screen. Am going to try the suggestions below to see if I can change the $TERM value first.

    Read the article

  • Problem with single quotes in man pages

    - by Peter
    When I ssh into my Debian Lenny server and open a man page, single quotes appear to be messed up. Example from the man page of apt-get: If no package matches the given expression and the expression contains one of ´.´, ´?´ or ´*´ then it is assumed to be a POSIX regular expression, and it is applied to all package names in the database. Any matches are then installed (or removed). Note that matching is done by substring so ´lo.*´ matches ´how-lo´ and ´lowest´. If this is undesired, anchor the regular expression with a ´^´ or ´$´ character, or create a more specific regular expression. I'm on Mac OS X and using xterm. If I use Terminal, the problem doesn't happen. My locale is configured correctly as far as I can see: $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= I'm not sure what's wrong with my environment, and I have no idea what to check next. I'd appreciate help.

    Read the article

  • Define custom escape sequences in terminal

    - by Ipkiss
    I would like to change the escape sequences used by some keys in my terminal. My goal is to define custom mappings in Vim (terminal version). In the following I use shift-space as an example, but I would prefer if the proposed solution could be generic. My current terminal (gnome-terminal) uses a simple space as escape sequence for shift-space, as can be seen by typing ctrl-v shift-space. A quick check with the true xterm shows the same behavior. I would like that the shift-space key combo generates another escape sequence (e.g., the one of shift-F30, which I would never use otherwise). So, how would I go about doing that? And is it really a good idea? Let me know if there are better alternatives... Note: I'm aware that this is only part of the problem: after the terminal sends a proper escape sequence for my keys, I still need to teach Vim what it means. But I think I know how to deal with that.

    Read the article

  • How can I invoke a function in bash shell script

    - by sufery
    !/bin/bash one_func(){ echo 'abcd' } echo $(one_func) echo one_func the end I just wonder the distinction calling the function between $(one_function) and one_function in bash shell script. When I set the variable "PS1" in ~/.bashrc, I can't invoke the function by one_func e: export PS1="\n[\e[31m]\$(one_func)" it work export PS1="\n[\e[31m]one_func" it doesn't work

    Read the article

< Previous Page | 1 2 3 4 5 6 7 8  | Next Page >