Xterm

I made the mistake of adding an xterm invocation to my ".bashrc" file. My intent was to simply execute an xterm upon initial login to the KDE environment on Debian Wheezy (though the distro probably would have made no difference). What happened is that with each invocation of "xterm", the new xterm would again invoke an "xterm" via the ".bashrc" file. Duh, infinite recursion of xterms upon login. Is there a simple way to invoke an xterm at login that doesn't itself lookup the ".bashrc" file? By the time someone answers this, I will probably find and answer somewhere in the bash/xterm man pages, but thought I'd throw it out there. Really felt stupid after having realized my mistake. Had to login to recovery command line mode and replace the ".bashrc" file with "/etc/skel/.bashrc". Cheerio

When I use X I most often run mutt in xterm and I thought it might be nice to send mutt's status_format to the xterm title.

It is set as
Code:

set status_format="Mailbox is %f with %M messages [%v]  You have %n new messages."

in my .muttrc.

Is this possible and if so how to do it? Any help would really be appreciated.

I use bash btw.

Hello,

I installed Mint 17 xfce onto a friend's HP netbook a few months ago. Up until now all has been working pretty perfectly.

From this evening, she tells me that after she types in her password the following message appears:

no exec. line in this session file [her password appears here in plain text!] running the GNOME failsafe session instead

The only option at this point is seemingly to click ok. After that, this message appears:

Could not find the GNOME installation will try running the failsafe xterm session

Again the only option is to click ok, then this appears for a few seconds:

Cannot find xterm start a failsafe session

Then it goes to a black screen (though you can see the mouse cursor) on which it stays indefinitely.

She tells me that she wasn't trying to do anything other than web browsing and email checking before this started happening so there doesn't seem to be any logical reason behind it. Does anybody have any idea what is happening and how to fix it?

I'm running Arch with i3. I'm trying to config xterm and realized that I didn't have a .Xdefaults file in my home directory. I saw in a forum that someone did

Code:

$ cd ~
$ touch ~.Xdefaults

I did that and it made a .Xdefaults file in my home folder but it is empty and I don't know what to do.

The previous Debian versions had root terminal application that I could use with line commands that I could copy/paste. I cannot find that anymore in Debian, only XTerm which I cannot copy/paste text from it. Any idea what I could use?

Chapter 17 of gnuplot pdf manual (Mouse Input) says "The x11, pm, windows, ggi, and wxt terminals allow interaction with the current plot using the mouse." I wonder if my Ubuntu 13.04 has any of those, if not, then perhaps the three terminals (Terminal, UXTerm, Xterm) I can invoke here, maybe they also have the same property? The proper term is: are they mouse capable? Thanks, - A.

Hi,
I am looking for a simple shell script that allows for sftp to be run from the server to another server (Windows). I would like the script to be passed parameters suchas destination server, Id, password, Directory structure/folder name, file name etc...
Need some help to know how to start with and it would be great if someone help me with any sample sftp shell script

Hi

I'm focusing on getting my head around interactive v non-interactive shells, both non-login and login. Basically what scripts are run and how local and global variables behave.

I'm pretty much there except for 'non-interactive login shells'. I understand that 'non-interactive' shells are started when a script is run. However, if I start my script with #!/bin/bash --login, then a 'non-interactive login' shell will be started.

In my mind I would have expected this to be the same as logging in from scratch, albeit without a user\password prompt. In this case I would have thought that any exported variables from the parent shell would be blown away. This doesn't appear to be the case. The 'non-interactive login' shell appears to inherit the environment of its parent 'interactive' shell.

Can anyone explain the purpose of a 'non-interactive login' shell and how they behave in this regard.

Hope this makes sense.

Cheers

Mike

Hi,

This might be odd, but in GNOME Shell 3.10.4 in fedora 20, I used to throw the mouse to the top left of the screen and that would make me feel excited about having all the open windows jam packed and then again selecting one I wanted. It really gave me a thrill.

But, in GNOME Shell 3.14.4, fedora 21 (workstation), I have to "click" on the "activities" on the top-left :-((

Is there any way I can change GNOME Shell 3.14.4 in way to have that feature back?

hi guys,

saw a video where the instructor wanted to login as root

he went...

sudo su -l

i see the -l option is -l, --login
Start the shell as a login shell with an environment similar
to a real login:

but i dont understand the significance of this...why couldnt you just go
su
login