Slackware :: XTerm*reverseVideo: True Doesn't Work In KDE?
May 18, 2011
I have the following line in my .Xresources, and it only works when I'm not running KDE:
Code:
XTerm*reverseVideo: true When I start up XTerm in Xfce, TWM, or any other window manager, I get the expected black background. When I launch XTerm in KDE, I get a white background, meaning that the reverseVideo setting is not taking effect. When I'm in KDE, launching XTerm with -rv does give me an XTerm with a black background. Obviously, having to add this switch every time I launch an XTerm in KDE is suboptimal, no matter how you try to automate it. Manually running xrdb -merge ~/.Xresources and then launching XTerm immediately afterwards does not make a difference.
If you're wondering why this is a concern, it's because all 256-color vim color schemes (xoria256, desert256, inkpot) require reverseVideo to be set so that XTerm launches with a black background. You get a black-on-black cursor otherwise.
When running MC in xterm or gnome-terminal, it doesn't seem to allow the use of Ctrl-enter and Ctr-shift-enter to copy marked files to the command line.
Does anyone know of another way to cause this to happen or a way to enable it under xterm/gnome-term?
Start xpdf or gv. Click an xterm to be active and slide it over xpdf/gv. Vertical lines from xpdf/gv under the xterm stick to the xterm window above and make it unreadable.
The problem does NOT show with KDE default settings with display effects on but does show in fvwm, xfce etc, and in KDE without effects.
On a system with a Sandy Bridge integrated graphics (i5-2400) the problem went away by downgrading to xf86-video-intel-2.13.0. But it was not enough for another system with 945G which needed downgrading to xf86-video-intel-2.12.0.
So when I upgraded to Slack64 13.1 on my asus MB homebrewed desktop and Slack 13.1 on my compaq presario a900 laptop, I started having issues with the xterm title (in Terminal--not Konsole) being too dynamic. By "too dynamic" I mean that I can't actually change the title. The dynamic title (from my .bashrc) is basically just pwd. Whenever I try to set the title (via terminal->set title (menu)), I changes it for a split second, and then reverts back to the dynamic title.
This is merely a petty annoyance, so to get around it, I added an xtitle function that I grabed somewhere online (just echos "�33]0;$*�07"). So for nano-ing some file, I'd type:xtitle some_file.txt; nano some_file.txt
That works just fine (kind of annoying to type though). running xtitle alone won't actually change the name either though (I'm pretty sure it's the same command as what terminal does anyway). That is, running: xtitle some_file.txt
changes the title for a split second, and the reverts back to my old pwd.What I really want is to have it dynamically name it "some_file.txt" whenever I use nano, but that appears to be a functionality of zsh (with the preexec() fxn).I'm wondering if anyone else has had this problem, and if you have a fix for it.
I have a user A that need to log into a linux box, change to user B, and then fire up a GUI.
I've tried this:
Code:
[userA@server ~]$ sudo su - userB -c "xterm" X connection to localhost:10.0 broken (explicit kill or server shutdown).
Running "echo $DISPLAY" shows the same value for user A as for user B when I first run "sudo su - userB". I thought that if the $DISPLAY variable is set correctly this would work, but apparently it doesn't. Does anyone else here know how to get this working?
EDIT: I forgot to mention that I'm SSH-ing into the server, and have x-forwading enabled.
Recently I installed a Linux distro (Pardus) which boots using initramfs. I am completely novice here. In the former configuration I used lilo to boot OpenBSD, Debian and W2k (it is easy for me to configure lilo to boot OpenBSD). But initramfs is a something completely new for me. As I understand it is a virtual file system with a standard directory tree and the information stored on that system is used (to boot the kernel?) to mount the true (physical) root device. The first question is how to properly describe a system (kernel image) booted with initramfs in the lilo.conf.
I had been running Slackware64 13 almost since it came out and recently upgraded to Slackware64 13.1.Every thing looked to be working well until I tried to burn a DVD with k3B. It starts the burn process but then dies and says that "cdrecord has no permission to open the device".I was able to put in a DVD+RW and erase it without a problem, but when trying to burn to a DVD-R it stops and gives me the error.I checked cdrecord and it is owned by root in the root group.
The sc spreadsheet app doesn't really work in 64bits. It launches but you're unable to do anything with it, it's not possible to enter any values in the cells or do anything else. It works fine in 32bit though.
To make it work properly in 64bits, you can use this patch, borrowed from debian: http://salix.enialis.net/x86_64/13.1...changes-7.16-3
And there is also this patch to make DESTDIR work properly with the Makefile: http://salix.enialis.net/x86_64/13.1...-destdir.patch
I maintain my slackware by using slackpkg-current. When I upgraded to the new OpenSSH 5.4, I noticed that my key method (passwordless) doesn't work anymore. I checked and checked the conf files but everything looks fine.I tried debug but can't get it to work, here is the debug:
Mar 15 21:52:15 vmslackware2 sshd[2663]: debug1: rexec start in 5 out 5 newsock Mar 15 21:52:15 vmslackware2 sshd[2622]: debug1: Forked child 2663. Mar 15 21:52:15 vmslackware2 sshd[2663]: debug1: inetd sockets after dupping: 3,
The FreeCAD slackbuild doesn't work. All the Slackbuilds for the dependencies worked.
Code: checking for boost system library... yes checking for X... libraries , headers checking for host... linux-gnu
[Code]....
I don't know what to do. That's the configure file in /tmp/SBo. Even if I alter it then when I run the slackbuild script again it wipes the old configure file and loads in a fresh one from the .tgz package.
I think the problem has something to do with bash4 parsing differently than bash3 or something? I don't know.
I really like the way the ledger CLI accounting software works, but I cannot seem to get it to function correctly. I set my LEDGER_FILE environment variable to my text file. Whenever I use ledger the output is always formatted incorrectly. Heres an example: I can do ledger bal
results (replace $MONEY with actual numbers): $MONEY ESC[34mAssets:CheckingESC[0m ESC[31m$-MONEYESC[0m ESC[34mEquity:Opening BalanceESC[0m
That is the result I get. I am not sure whats wrong. There is also no man page for ledger or any kind of help with the -h flag.
I have slackware 13.37-64 bit with xfce. I have a "microsoft wired keyboard 600" keyboard and want to remap it to use the right win key as ctrl. With xev i see that the keycode for the specific win key is 134.
Then i run:
Code:
But nothing changes. Even if i manually configure the .Xmodmap file in my /home i see no change at all.
Okay, when I load epsxe it loads just fine and I got it playing playstation games BUT the audio doesn't work. I have this issue with Basilisk II and it never got solved. When I load the epsxe executable I get
I've been using Slackware for awhile now on my laptop without a single issue (well except that I can't get the screen brightness to change, but that's a separate issue).
I logged in today and went to the terminal and when I type the letter 'e' it is not shown or recognized. It works when I 'su -' and enter my root password which contains the letter 'e' twice, but otherwise is not recognized.
I have no idea where to even start with this problem. I've logged out and back in. I've restarted twice now, but the problem is not going away. Obviously, my keyboard is working properly as I am typing this message with the letter 'e', but in the Terminal it is not recognized.
I have a fairly fresh Slack install. When I start or shutdown X, the sounds that are supposed to play do. Also, sometimes everything else that is supposed to play sounds does.
However, sometimes the sound doesn't work for flash content or pidgin. I have never had a similar problem and I don't know where to start in resolving this issue.
I have RAR archive including some files using Russian file names and I?m unable to display them properly in xterm window in my Slackware 13.1. Instead of the Cyrillic letters I see questions marks, for example ??.txt?.I tried four methods:
(This assumes you didn't already have a ~/ffbug directory, and you have firefox 3.5.6 installed -- the prior firefox id not have this problem) What you will probably see is firefox trying to display a listing of the ~/ffbug directory, but instead showing an error message: XML Parsing Error: not well-formed. I posted this in the mozillazine forum, where it got read 20 times, but no response.
when i load lilo, everything is greenish and weird, i tried to change the picture with Lilo.conf, fallowing the exact instruction given by linux forum, dosnt work. the linux logo got verry strange colors has well,verry ugly.
at first i tried to install my ati driver, but my x1800 is not supported anymore, so i decided to run xconfsetup to use the default ati driver. After that i have been in the xorg.conf generated by the setup and it seem they got the right driver, it say radeon in the device section. another problem i experience is that everytime i lod KDE my default resolution suck, and when i open the control panel and click on display, everything goes right.
the last problem is more serious, when i order my computer to shutdown either by command line or with the logout button, the screen goes black and nothing happen at all. Its sad beccause so far everything else seem to work fine, i installed my network card and my sound card properly.
xterm is scanning lines one by one.It takes time.I did jumpScroll: true ,but it results same. But rxvt is better comparing this. Where would i get the global configuration file for rxvt and xterm?
Just can't resize xterm or any windows such as firefox. In xterm it seems using the button in the up-right corner could resize the window's width, not height.
I'm trying to turn on the system bell (pc speaker) in xterm. I have the bell working in console (text mode, not under X), and with X running, even firefox can use the pc speaker (it beeps, when I enter a search term which is not found). Only xterm doesn't seem to work.
Here is my xterm config, and the xset command I'm trying to use to turn the bell on: -------###-------- xterm*renderFont: true xterm*faceName: Terminus xterm*faceSize: 12
xterm*background: black xterm*foreground: white !xterm*highlightColor: red xterm*charClass: 46-47:48
xterm*visualBell: false -------###-------- xset b on xset bell 100 1000 1000 -------###--------
If I run xterm with the +vb option, it doesn't help either (I'm testing it with printf "a"). What am I missing? How can I make xterm use my pc speaker as bell?
Just upgrading to 13.0, and one thing I had in KDE 3.5 was a larger (normal) sized xterm, and a smaller sized one. The small sized ones are handy for CL scripts and don't chew up as much screen-estate.
I know I can change defaults in .xinitrc, but I don't know how to make a widget for the small xterm.
I'm having a problem with vim and xterm. When I open a file and press any key, the colour scheme changes slightly. This doesn't happen if I run a 256-colour xterm (export TERM='xterm-256color') but if TERM is set to 'xterm' (the default) I see the colour change. Setting TERM='xterm-256color' in my ~/.bashrc is a "solution", but I'd rather not have to do that since it's never been necessary in the past (e.g., on 13.1) and I don't use any 256-color schemes for vim (usually just the default or possibly "delek"). It doesn't happen with rxvt or with Xfce's terminal. I've tried compiling some other versions of xterm but they either exhibit the same behaviour or don't build. I have tried running without any ~/.vimrc file just to be sure it wasn't one of my settings and I've also tried the sample file at /usr/share/vim/vimrc; the effect is the same.
I've read about this. Everyone says to use ~/.Xresources or ~/.Xdefaults, and it doesn't work for me. It doesn't do anything at all, in fact. I'm trying to use this:
Code:
XTerm*background: black XTerm*foreground: white
In the ~/.X* files, it won't work. I read that another way of doing it is using
Code:
xrdb -merge .x_settings_file
This will work for me. It's the only thing I can get to work. But when I restart, it will have to be done again. I'm using Slackware 12.2.
I am playing with SalixOS which is supposed to be entirely compatible with Slack. I've never put Slack proper on this laptop. It's run Ubuntu and Mandriva both and the volume wheel always works. It does not seem to be recognized in Salix. I figure the fix will be the same in Salix as Slackware so I'm asking here. The laptop is an A205 Toshiba Satellite.
I use VNC, open an xterm, and for example when I press "NumPad7", it completes "Home" command. Also "NumPad1" is mapped to "End". In fact there is a code for .cshrc that does the work required. But unfortunately I can't translate it into a bash code. Please help me to translate. Here is the code:
if ($?TERM) then # fix the home, end, ins and del keys if ($TERM == "xterm" || $TERM == "vt100" || $TERM == "vt102" || $TERM !~ "con*") then
