Conky inside GNU/Screen session

hi! i was looking around but found nothing similar to what i want...
i was searching for a possibility of use conky INSIDE a terminal instead of the root window (aka "desktop") because i barely see my wallpaper, it's always covered with urxvtc sessions in dwm, so i have a detailed bottom bar inside dwm bottom bar, but i like to trim it to say audio volume + clock and have a conky or another similar program inside a gnu/screen "tab" showing my system activity, i surely want disk I/O usage and free/used space for example
the thing with conky-cli is that it behaves like this: (not cleaning the screen with every refresh)
[aleyscha@aleyscha 39 ~]$ conky
5d 12h/12C | 12%/36.0C/2/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 0k/0k | 0/0 | 20:22 07/10/2008
5d 12h/12C | 20%/36.0C/2/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 16k/7k | 0/0 | 20:22 07/10/2008
5d 12h/12C | 11%/36.0C/1/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 35k/14k | 0/0 | 20:22 07/10/2008
5d 12h/12C | 12%/36.0C/3/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 39k/14k | 0/0 | 20:22 07/10/2008
^C5d 12h/12C | 16%/36.0C/1/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 39k/14k | 0/0 | 20:22 07/10/2008
Conky: received SIGINT or SIGTERM to terminate. bye!
[aleyscha@aleyscha 40 ~]$

LOL, DONE!!
${execp clear} was the answer
here's my conky(cli) rc file (needs work... i'll stole some from your conky configs and screenshots thread, huaahahahaha)
background no
out_to_console yes
update_interval 2.0
total_run_times 0
uppercase no
TEXT
${execp clear}
${time %l:%M:%p}
Uptime: $uptime
CPU: ${cpu}% ${cpubar 5,85} Disk I/O: ${diskio}
RAM Usage: $mem/$memmax - $memperc%
Swap Usage: $swap/$swapmax - $swapperc%
Net Down: ${downspeed eth0} k/s Net Up: ${upspeed eth0} k/s
File systems:
/ ${fs_used /}/${fs_size /}${alignr}${fs_bar 5,120 /}
/home ${fs_used /home}/${fs_size /home}${alignr}${fs_bar 5,120 /home}
/sda1 ${fs_used /sda1}/${fs_size /sda1}${alignr}${fs_bar 5,120 /sda1}
/sda6 ${fs_used /sda6}/${fs_size /sda6}${alignr}${fs_bar 5,120 /sda6}
/downloads ${fs_used /downloads}/${fs_size /downloads}${alignr}${fs_bar 5,120 /downloads}
/sdb5 ${fs_used /sdb5}/${fs_size /sdb5}${alignr}${fs_bar 5,120 /sdb5}
/sdc1 ${fs_used /sdc1}/${fs_size /sdc1}${alignr}${fs_bar 5,120 /sdc1}
/sdd1 ${fs_used /sdd1}/${fs_size /sdd1}${alignr}${fs_bar 5,120 /sdd1}
Top Processes:
Name PID CPU% MEM%
${top name 1} ${top pid 1} ${top cpu 1} ${top mem 1}
${top name 2} ${top pid 2} ${top cpu 2} ${top mem 2}
${top name 3} ${top pid 3} ${top cpu 3} ${top mem 3}
${top name 4} ${top pid 4} ${top cpu 4} ${top mem 4}
Mem usage
${top_mem name 1} ${top_mem pid 1} ${top_mem cpu 1} ${top_mem mem 1}
${top_mem name 2} ${top_mem pid 2} ${top_mem cpu 2} ${top_mem mem 2}
${top_mem name 3} ${top_mem pid 3} ${top_mem cpu 3} ${top_mem mem 3}
${top_mem name 4} ${top_mem pid 4} ${top_mem cpu 4} ${top_mem mem 4}

Similar Messages

  • [SOLVED] GNU Screen - sessions always dead after restart

    I recently started using GNU screen.  I'm able to detach and reattach sessions normally, except after a restart.  Then any detached sessions are marked as dead and all I can do is run a screen -wipe.  My sessions are stored in ~/.screen. 
    I've searched the web and forums but no one seems to have had this problem.
    Any ideas?  Screen's a lot less useful if I can't reattach after restarting.
    Last edited by noahsark1126 (2009-08-18 05:14:42)

    This is sort of related, but sometimes it is possible to use special software to suspend an application as a file, which could possibly be set up with screen to provide a rebootable state. However this software seems to be fairly hard to find and get working well enough to be usable. If you want to investigate more, you can probably google for something like "linux application freezing" or "linux application checkpointing".
    Actually I just found the software I was thinking of as I'm typing this, http://cryopid.berlios.de/. The page doesn't seem to be loading for me, but I think I have used this in the past with limited success. Not sure if it up to date with the latest kernels however.

  • Gnu Screen theme cycle with keybinding

    A guy at work did this and shared with me, so i thought I'd continue spreadin the love.    If you have multiple gnu screen sessions going at once, wouldn't it be nice to visually tell them apart without spending time to read the session name of each or trying to see what was going on within each?   
    The best way would be to color code the caption and hardlinestatus lines and be able to easily select a "color" per screen session and that's what he and I did.  Using C-g, we/you can easily cycle through various "themes".   This could also be useful if you wanted to cycle through mutiple hardstatus lines that displayed different information too if that's the route you'd like to go.   Anyways here it goes:
    #terminfo and termcap for nice 256 color terminal
    # allow bold colors - necessary for some reason
    attrcolor b ".I"
    # tell screen how to set colors. AB = background, AF=foreground
    termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
    # erase background with current bg color
    defbce "on"
    startup_message off
    bindkey ^G screen screen_theme.sh
    caption always "%{= KW}%-w%{= gW}%n %t%{-}%+w %-="
    hardstatus alwayslastline "%{= kW} %-= %{= kG}Session:%u%{= kW} %5` | %{= kG}Host:%{= kW} %H | %{= kG} MEM:%{= kW} %2`MB |%{= kG} SW: %{= kW}%3`MB | %{= kG}Unread: %{= kW} %4` | %m/%d %C %A"
    vbell off
    #Backticks to display information in status bar
    backtick 1 60 60 $HOME/bin/get_uptime
    backtick 2 60 60 $HOME/bin/get_freemem
    backtick 3 60 60 $HOME/bin/get_freeswap
    backtick 4 60 60 $HOME/bin/get_gmail
    backtick 5 60 60 $HOME/bin/get_sessionname
    defscrollback 5000
    screen -t root 0 sudo -s
    screen -t shell 1 bash
    screen -t shell 2 bash
    screen -t shell 3 bash 
    screen -t shell 4 bash
    screen -t shell 5 bash   
    screen -t shell 6  bash 
    screen -t shell 7  bash 
    screen -M  -t irc 8 irssi
    screen -t home 9 ssh home
    select 1
    This script resides in ~/bin which is in my path.  screen_theme.sh:
    #!/bin/bash
    INDEXFILE="$HOME/bin/themes/theme_index"
    # if this is the first time then set
    # the index to 0
    if [[ ! -e $INDEXFILE ]]
    then
    echo 0 > $INDEXFILE
    fi
    THEMENO=`cat $INDEXFILE`
    THEMEMAX=5
    if [[ $THEMENO -eq $THEMEMAX ]]
    then
    THEMENO=0
    else
    THEMENO=`expr $THEMENO + 1`
    fi
    echo $THEMENO > $INDEXFILE
    THEMEFILE=$HOME/bin/themes/theme${THEMENO}
    if [[ -e $THEMEFILE ]]
    then
    bash $THEMEFILE $STY
    else
    # reset the index back to zero if broken
    echo 0 > $INDEXFILE
    fi
    then I created a directory ~/bin/themes.  Within that directory I have the following files:
    $ ls themes/
    theme0 theme1 theme2 theme3 theme4 theme5 theme_index
    Each theme file is another color theme, the index just holds a count of the number of themes.
    An example of theme0  ( remember when doing yours to escape your backticks, otherwise it'll break).
    #!/bin/bash
    # yellow
    SESSION=$1
    screen -S $SESSION -X caption always "%{= KW}%-w%{= yk}%n %t%{-}%+w %-="
    screen -S $SESSION -X hardstatus alwayslastline "%{= kW} %-= %{= ky}Session: %u%{= kW}%5\` | %{= ky}Host:%{= kW} %H | %{= ky} MEM:%{= kW} %2\`MB |%{= ky} SW: %{= kW}%3\`MB | %{= ky}Unread: %{= kW}%4\` | %m/%d %c"
    Here's how my screen started:
    http://tuxtraining.com/images/screen1.png
    After C-g
    http://tuxtraining.com/images/screen2.png
    After C-g again
    http://tuxtraining.com/images/screen3.png
    and so on.
    Last edited by scv5 (2009-10-12 16:38:51)

    thayer wrote:
    steve___ wrote:
    Lich wrote:... useless for most of us as we only use one screen session normally.
    How do you know this?
    Just a guess, but doesn't that sort of defeat the purpose of a multiplexer?  I mean it's like running 20 instances of firefox instead of using a single firefox window with 20 tabs.  I'm sure some folks prefer the former, but I think it's safe to say the majority use the latter method.
    Sort of, I find screen becomes difficult to manage once we're talking more than the original 0-9 windows and you have to C-a-##, there's also the issue of screenspace.  With firefox i can list my tabs vertically giving me a lot more room to manage my tabs, screen doesn't have that option, so they go horizontally.    If i name all my tabs after the IP or name of the machine theiy are logged into, approach 15-20 windows really creaps on the screenspace.
    So typically what i do is have four shells open (grouped together or done in something like terminotor, or tabbed in flux or pekwm) each with 0-9 shells a piece, each session organized into type of servers.   So the upper left may be the email systems i support, the uppser right screen session may hold all the shell of our public facing web environment, bottom left is my local box, bottom right being misc boxes (dns servers, nis/ldap servers, various developement boxes..)  you get the hint.
    take into consideration i get one of these going per monitor that gives me approximately 80 shells, which is quite unmanagable in one screen session if you ask me.

  • [SOLVED] start screen session as different user

    This is driving me nuts. I run an opensim server on system, and currently have a watchdog script used to check that the server is running and either run it or re-start it as necessary (in the event of a server crash).
    The server itself is run in a gnu screen session so that I can log in to the server remotely via ssh. At the moment I run my watchdog at login, which is not ideal. I want to run it at boot so that I don't actually have to login to start. A prime candidate for rc.local. However, starting the script in rc.local always starts the screen session as root, whatever I do, which is not what I want (obviously a publicly accessible server should not be running as root). Here's what I've tried so far:
    in rc.local:
    su user -c `sh /home/steve/scripts/checksim.sh` &
    in the script:
    su user -c 'screen -d -m mono Opensim.exe'
    Both tried together and varying combinations. I've also tried with sudo:
    sudo -u user -n -i ......
    Either the screen session doesn't start, or it starts as root. Any ideas?
    Last edited by Roken (2012-05-19 13:28:56)

    Argghhh - fixed it.
    One of my previous tries resulting in the server running as root had changed ownership of the server cache to root, preventing the server itself starting as a normal user. Fixed up ownership and tried again, now it's running properly from rc.local

  • Urxvt, xterm, vim, and gnu screen.

    To make this simple: all i want is 256 color support in one terminal, that will give 256 color support in vim, gnu screen, and not screw up shells i ssh into.    If I could get this working in xterm alone consider this solved.
    The more I try to fix my problem it seems the more complicated it gets.  What I want, I thought was simple:
    Now xterm seems to be the most workable solution, I guess I can give up on having clickable links, so that can go on the back burner.  But these are the problems i'm having.
    Here's the problem point by point:
    Urxvt
    $ echo $TERM
    xterm-256color
    Urxvt will run a perl script I have to display 256 colors.  Except is does not show the grayscale ramp shown here:
    VIM in urxvt does NOT show any colors.  It's all white text.
    This is my .vimrc
    $ cat .vimrc
    syntax on
    set ignorecase
    set smartcase
    set incsearch
    set hlsearch
    let g:netrw_http_cmd = "wget -q -O"
    if &t_Co == 256
    colorscheme xoria256
    else
    colorscheme desert
    endif
    in urxvt Gnu Screen
    echo $TERM
    screen-256color-bce
    the perl script does not display 256 colors like it should.
    vim in urxvt in screen again, does not show any colors. all white text.
    Xterm
    echo $TERM
    xterm
    Xterm displays the full 256 colors from the script including the grayscale ramp.
    vim in xterm displays the desert theme (i would prefer it default to the xoria256, no idea why the 256 color script works but vim doesn't see xterm as a 256 capable terminal).
    in xterm, Gnu Screen
    echo $TERM
    screen-256color-bce   ( I do not see in any file where this option is defined)
    Xterm with Gnu Screen displays the full 256 colors from the script including the grayscale ramp.
    Vim in Gnu Screen in Xterm displays 256 colors properly.
    Here is my .screenrc
    #terminfo and termcap for nice 256 color terminal
    # allow bold colors - necessary for some reason
    attrcolor b ".I"
    # tell screen how to set colors. AB = background, AF=foreground
    termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
    # erase background with current bg color
    defbce "on"
    #term xterm-256color
    term screen-256color
    startup_message off
    caption always "%{= KW}%-w%{= gW}%n %t%{-}%+w %-="
    hardstatus alwayslastline "%{= kW} %-= %{= kC}Session:%u%{= kW} %5` | %{= kC}Host:%{= kW} %H | %1` |%{= kC} MEM:%{= kW} %2`MB /%{= kC} SW: %{= kW}%3`MB | %4` %{= kR}Unread %{= kW}| %m/%d %c"
    vbell off
    #Backticks to display information in status bar
    backtick 1 60 60 /home/username/bin/get_uptime
    backtick 2 60 60 /home/username/bin/get_freemem
    backtick 3 60 60 /home/username/bin/get_freeswap
    backtick 4 60 60 /home/username/bin/get_gmail
    backtick 5 60 60 /home/username/bin/get_sessionname
    defscrollback 5000
    screen -t root 0 sudo -s
    screen -t shell 1 bash
    screen -t shell 2 bash
    screen -t shell 3 bash
    screen -t shell 4 bash
    screen -t shell 5 bash
    screen -t shell 6 bash
    screen -t shell 7 bash
    screen -t irc 8 irssi
    screen -t home 9 bash
    select 1
    here is my .Xdefaults
    !XTerm*font: -*-terminal-*-*-*-*-14-*-*-*-*-*-*-
    XTerm*font: xft:DejaVu Sans Mono:size=8
    xterm*faceName: Mono
    xterm*faceSize: 8
    XTerm*background: #191919
    XTerm*foreground: white
    XTerm*pointerColor: white
    XTerm*pointerColorBackground: black
    XTerm*cursorColor: white
    !XTerm*internalBorder: 3
    XTerm*loginShell: true
    XTerm*scrollBar: false
    XTerm*scrollKey: true
    XTerm*saveLines: 1000
    XTerm*multiClickTime: 250
    XTerm*boldColors: false
    xterm*title: xterm
    xterm*geometry: 160x25
    ! Black
    XTerm*color0: #262626
    XTerm*color8: #252525
    ! Red
    XTerm*color1: #C12121
    XTerm*color9: #E50E0E
    ! Green
    XTerm*color2: #597b20
    XTerm*color10: #89b83f
    ! Yellow
    XTerm*color3: #Ded838
    XTerm*color11: #efef60
    ! Blue
    XTerm*color4: #265997
    XTerm*color12: #3F6FD0
    ! Magenta
    XTerm*color5: #706c9a
    XTerm*color13: #826ab1
    ! Cyan
    XTerm*color6: #69a2b0
    XTerm*color14: #a1cdcd
    ! White
    XTerm*color7: #BBBBBB
    XTerm*color15: #EEEEEF
    URxvt*termName: xterm-256color
    URxvt*urlLauncher: /usr/bin/firefox
    URxvt.matcher.pattern.1: \\bwww\\.[\\w-]\\.[\\w./?&@#-]*[\\w/-]
    URxvt.matcher.button: 2
    URxvt.perl-ext-common: default,matcher
    URxvt*saveLines: 4000
    URxvt*background: #191919
    URxvt*secondaryScroll: true
    URxvt*scrollBar: false
    URxvt*geometry: 150x25
    URxvt.font: xft:DejaVu Sans Mono:size=8
    URxvt.xftAntialias: true
    URxvt*foreground: white
    URxvt*pointerColor: white
    URxvt*pointerColorBackground: black
    URxvt*cursorColor: white
    !URxvt*inheritPixmap: True
    !URxvt*shading: 90
    !URxvt*tintColor: #999
    URxvt*keysym.Home: \033[1~
    URxvt*keysym.End: \033[4~
    ! Black
    URxvt*color0: #262626
    URxvt*color8: #252525
    ! Red
    URxvt*color1: #C12121
    URxvt*color9: #E50E0E
    ! Green
    URxvt*color2: #597b20
    URxvt*color10: #89b83f
    ! Yellow
    URxvt*color3: #Ded838
    URxvt*color11: #efef60
    ! Blue
    URxvt*color4: #265997
    URxvt*color12: #3F6FD0
    ! Magenta
    URxvt*color5: #706c9a
    URxvt*color13: #826ab1
    ! Cyan
    URxvt*color6: #69a2b0
    URxvt*color14: #a1cdcd
    ! White
    URxvt*color7: #BBBBBB
    URxvt*color15: #EEEEEF
    To Fix In Xterm
    -Get Vim to display 256 colors without Gnu Screen
    To Fix In Urxvt
    -Get vim to display any color, but preferably 256 colors in urxvt and urxvt with Gnu Screen.  (and yes, it's a 256 capable urxvt)
    -Get shells i SSH into to recognize the reported term variable
    To Fix In Gnu Screen
    -Make it stop reporting the term variable as screen-256color-bce without losing 256 color support as this screws up shells i ssh to.
    any help would be greatly appreciated.  I feel like a dog chasing its tail b/c when I find a fix to one problem, I end up creating 1-2 more.
    Last edited by scv5 (2009-07-31 14:11:31)

    I had similar but different issues regarding this.  Now, i have 256 color support in whatever terminal/ssh/screen session I'm in.
    The relevant config lines:
    .Xdefaults:
    XTerm*termName: xterm-256color
    URxvt*termName: rxvt-256color
    .vimrc
    " 256 colors only if you can handle it
    if $TERM =~ "-256color"
    set t_Co=256
    colorscheme zenburn
    endif
    .screenrc
    # term
    term xterm-256color
    # main options
    altscreen on
    attrcolor b ".I"
    defbce "on"
    # some termcaps
    termcapinfo xterm-256color 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
    termcapinfo rxvt-256color 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
    note: this setup caused an issue where background colors in mutt/htop inside screen did not extend passed the line's text.  i had to solve that via this workaround.
    Last edited by brisbin33 (2009-07-31 21:28:55)

  • Gnu Screen and 10.5

    So, does anyone else have problems with Gnu Screen and OSX 10.5? If I use the box-shipped version, my PATH is completely ignored, and it doesn't understand deflogin or login in my .screenrc file.
    If I use the macports version, I get UTMP problems and unless I manually create /var/run/utmp, eventually /etc/sudoers and passwd gets updated, and UID 501 is no longer in the passwd file!

    That's actually not screen's fault.
    When bash starts, it will read either .profile_bash or .bashrc but not both, depending whether it is a shell process or subprocess.
    On X-window based systems, one of these (I can never remember which) gets read when the root window starts, and then the other gets read when every sub-process starts. On OS X this approach breaks down.
    There is a slightly different bug I have been seeing, and I think it is due to multi-threading. Basically the screen session starts before the $PATH gets entries like /sw/bin or /opt/local/bin set. I never figured out how, but my hackish workaround is simply to start screen and then invoke the process I want, rather than to do it all in one command. (This gets annoying if you are writing shell scripts that invoke screen).

  • I bought the new iphone6 plus at m1 got to "black gap" inside the screen,and apple said cannot be repair  ***,

    I bought the new iphone6 plus at m1 got to "black gap" inside the screen,and apple said cannot be repair  ***,
    ***,,,It's really assembly mistakes......why apple become like that...
    and i chat online with apple support,she said let me call customer service,
    after i call, they said let me went to A.LAB again,,,,they cannot do anything for it ...........
    then A.LAB said they cannot be exchange,need apple to approve...then apple declined this case....
    how......why apple become like that....
    iPhone 6 Plus, iOS 8.1

    Same answer as your other post:
    FelipeV     Nov 5, 2014 9:32 AM 
      Re: new iphone6 plus got to "black gap" inside the screen,and apple said cannot be repair  ***  in response to yidingfromsingapore      
    So what do you want us to do? Apple has already told you and there is nothing anyone here can do about your problem as no one here works for Apple.

  • X crashed, cannot open display in screen session for X apps

    I had X crash and logged back in, and now in my screen session I can't open any apps that use X, ie.,:
    ~/.fluxbox # gedit keys
    cannot open display:
    Run 'gedit --help' to see a full list of available command line options.
    ~/.fluxbox #
    Must I start a new screen to have it work again or can be fixed within current screen? Thanks for any help!

    Looks like your DISPLAY variable isn't set? What does
    $ echo $DISPLAY
    show? If nothing, try the following in your screen session (you may have to do this for each shell within screen that you're running):
    $ export DISPLAY=":0"
    (assuming that it is DISPLAY 0, which is the default)
    Last edited by nogoma (2008-08-12 17:17:54)

  • GNU Screen mouse scrolling shows only empty lines

    Hi,
    I've got a problem with using my mouse wheel to scroll in GNU Screen.
    This is the content of my .screenrc:
    defscrollback 10000
    hardstatus off
    termcapinfo xterm* ti@:te@
    altscreen on
    With this settings, It kinda works: I can scroll up, but instead of showing the previous output, I just shows blank lines.
    I can actually scroll up by entering Screen's copy mode using CTRL-A ESC and then using the Arrow-keys or PageUp.
    Furthermore, if I then scroll with my mouse wheel, I can also scroll the lines that were displayed in copy mode, but if I try to scroll further than I scrolled in copy mode, I still see blank lines.
    Thanks in advance!

    hume's doona wrote:
    Are you configuring for the nvidia card?
    #sudo nvidia-settings
    and set it to twin view in the gui?
    No I think the problem is more basic than that...he's trying to use an ATi card and an Nvidia card simultaneously.  Something that I don't think will work.
    It also dependent on what drivers he is trying to use, as the (new) Nvidia proprietary driver only supports GeForce4 series chips and up...and the OP has an even older card than that.  The legacy Nvidia-96.xx driver does support his chipset, but 96.xx does not work with Xorg1.8 last I knew. see: http://www.archlinux.org/news/502/
    Twinview does not exist in the Nouveau drivers, so one has to use xrandr: http://wiki.archlinux.org/index.php/Nouveau
    Last edited by Skripka (2010-08-14 14:16:25)

  • GNU Screen prints back garbage?

    So. I've noticed an odd thing happening. Eventually, while running GNU Screen, lynx will start spitting out garbage characters at me. It usually starts with lynx, and then spreads to my other programs. http://homepage.mac.com/jamesebailey/screen_garbage.png is a picture of irssi with the garbage. I've only just started using screen, and I don't have the problem when I log in remotely, but only on my local login. I guess I could just SSH into my home computer while sitting in front of it, but that just seems silly, and there's got to be an explanation and solution for this, other than just working around it.
    Maybe not.

    Yeah, I know a couple of ways of getting it to do that, unfortunately, I've done none. Usually, I just switch back to a screen and see garbage. Moments later, all of my screens have garbage. Usually quitting the program and then quitting terminal gets rid of it, I'm just wondering if anyone knows what causes it and how to prevent it.

  • How to clean the dust inside the screen of the iPod Touch?

    Hi everybody,
    lately some dust entered inside the screen of my iPod Touch.
    At first it looked like one or two pixels were gone bad, but it is just some annoying dust.
    The problem is that I cannot figure out any way to remove it.
    I tried a gentle blow from the connector hole but the result was worse.
    Any idea on how to clean the screen inside?
    I hope it is not necessary to go to an Apple Center and pay for the "cleaning service".
    Regards,
    Andrea

    It sounds safe to use
    'Falcon's® "Professional" Dust-Off® "XL" compressed-gas is the perfect product for removing dust from your color transparencies before making scans or copy slides; it's also great for removing dust from cameras, lenses, computers and other electronic equipment. Each 12 oz. disposable can comes with its own trigger value and a 4.75" nozzle extension (a red tube) that allows you to place precise bursts of compressed air just where you want it.'
    Check the directions on the back... also check the contents. Normally anything like that will inform you of contaminants harmful to delicate electrical devices.
    If its just compressed air make sure you keep the can well back from the source.. and unplug the G5 (take it somewhere you don't mind dust.. there no point doing this in situe, just for it to suck it back in again!)
    Also.. as mentioned.. keep the can upright (as the air is decompressed the can gets very cold)
    Stu
    Powermac G5 2.5 Mac OS X (10.4.2) 460gb HD 3gb RAM

  • Using "Window" (Super_L) key as escape in GNU Screen

    I've been trying to map the Windows key (to the left of the space bar) to be the escape key in GNU Screen (as opposed to ^A) with no luck. xev gives me that it generates keycode 133 and its keysym is "Super_L" so its definitely recognized by the system, but I don't know what I can write in my .screenrc to be able to use it as an escape key. I've tried googling how to do it, but the solution another person found didn't work for me (use xmodmap to map keycode 133 to something else - like F13, and then get the literal value in vim by pressing ctrl+v and the key (it generated ^[[3~ or something similar) and then putting that in the .screenrc file).
    Has anyone else solved this?

    I believe you can use the xmodmap method, although it may cause you some problems.  Try this:
    $ xmodmap -e "keycode 133 = F19"
    then put the following line in your .screenrc:
    bindkey -k F9 command
    Note the difference between using 'F19' for xmodmap and using 'F9' in the bindkey command.  This is due to bindkey using the termcap database for specifing keys.  The main problem here, as far as I can tell, is that the termcap database doesn't have any notion of the "Super_L" or "Super_R" keys, thus you have to do this strange xmodmap assignment of keycode 133 to some key that bindkey can recognize.  This will work even if your keyboard doesn't have an F19 key as my example shows.  Of course, you don't have to use function key F19; you can use any key on your keyboard.  The important thing to remember is that the bindkey command in your .screenrc file uses the termcap database (see man termcap) to determine what key to use, and the xmodmap command uses some other mechanism. You have to understand how to specify the keys for each case.
    Other possibilities:
    xmodmap -e "keycode 133 =  F1"  <==>  bindkey -k k1 command
    xmodmap -e "keycode 133 =  F2"  <==>  bindkey -k k2 command
    xmodmap -e "keycode 133 =  F3"  <==>  bindkey -k k3 command
    xmodmap -e "keycode 133 =  F9"  <==>  bindkey -k k9 command
    xmodmap -e "keycode 133 = F10"  <==>  bindkey -k k; command
    xmodmap -e "keycode 133 = F11"  <==>  bindkey -k F1 command
    etc.
    This could cause a problem if some other application you use (like your window manager or desktop environment) uses 'Super_L' for something.  I really don't understand exactly how all this works so I don't know how you could fix a conflict like that.
    Finally, when you remap 'keycode 133' to some other key, then pressing that key will now generate some character. Pressing the windows key when not in screen, at least on my system, caused a '~' to be printed.  I don't know how you would get rid of this.

  • GNU Screen Scroll problem

    Hello everyone, I'm a new member in the Arch community and I'm enjoying myself a lot by using this distribution.
    the problem I'm having is that I can't seem to get the mouse scrollwheel to scroll upwards in GNU Screen running in a Terminator emulator once the terminal is filled.
    I have searched a bit and found that I should put something like this in my ~/.screenrc
    terminfo xterm* ti@:te@
    I have changed the xterm* to terminator* to match my emulator, my full .screenrc is as follows
    bind c screen 1
    bind ^c screen 1
    bind 0 select 10
    screen 1
    term screen-256color
    hardstatus alwayslastline '%{= g}[ %{G}%H %{g}][%= %{= w}%?%-Lw%?%{= R}%n*%f %t%?%{= R}(%u)%?%{= w}%+Lw%?%= %{= g}][%{B}%Y-%m-%d%{g}]'
    startup_message off
    terminfo terminator* ti@:te@
    vbell off
    altscreen on
    defscrollback 5000
    When I first open screen I can scroll up and down using the mouse wheel, but once the terminal gets filled all the way, the mouse wheel starts to show the command history instead of scrolling, which is a pretty odd behavior in my point of view.
    Anyone knows why is that happening?

    geekinthesticks wrote:I think I am missing something obvious and simple, but can't see what it is!
    They're called code tags
    I can't help with the problem directly, but those who can will probably be more inclined to do so if you include file contents of command output in [ code ] ... [ /code ] tags to keep it clean and readable.

  • How do i  remove the air bubble and dust inside the screen?

    i use the shield on my IPAD, and didnot wait 24 hours. so that's why there has a lot air bubble and dust inside the screen when i remove the shield.
    How do i remove these air bubble and dust inside the screen of my IPAD?

    I do not understand what you are seeing. Can you post a screen shot?

  • Hi I bought macbook Pro Retina 1.3 from India on the 29th March 2014 and currently I am in Norway. And suddenly I can see the inside display screen is broken. Nothing from outside and the main top screen. I got by email from the shop in India, Mumbai

    Hi I bought macbook Pro Retina 1.3 from India on the 29th March 2014 and currently I am in Norway. And suddenly I can see the inside display screen is broken. Nothing from outside and the main top screen. I got by email from the shop in India, Mumbai where I purchased it and I have the photos of the screen where do I upload kindly urgently do let me know. It is under warranty till today and I need your urgent details so that I can upload required datas and I shall go back to India on the 5th April 2015 hence I need to get from you how to go about. Thank you. Uday Kumar Ghosh +47 455 48 953

    Thank you. I did contact Apple Norway and they already raised a case no based on which I shall go and hand over my mac pro retina 13inch. As per Apple Norway, as the case has been registered before the expiry of the warranty, Apple India to accept the warranty  as well and get the set repaired under warranty. Thank you.

Maybe you are looking for