-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all. I use mc quite frequently, but suddenly it has started behaving badly. As i enter 'mc' from the shell i usaly get the same folder opened. (eg. rikjoh@sparhawk:~> mc rikjoh@sparhawk:~>) But since a little while back i get: rikjoh@sparhawk:~> mc 2;rikjoh@sparhawk:~1;sparhawkrikjoh@sparhawk:~> And the "grey keys" doesnt work any more. The only new thing i have done is using NIS for logons. But why should that have anything to do with that? Everything else works as usual... - -- /Rikard - ------------------------------------------------------------------------------------ Rikard Johnels email : rjhn@linux.nu Web : http://www.rikjoh.com Mob : +46 70 464 99 39 - ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78 46 1C EE 56 > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+2SnIWdS2eEYc7lYRAl8ZAKD6PwQriAxRMr6xnoRxR94pBYMwqACcDmEY 8rnuEbjSMk9UBgI32ltfQ4M= =shwC -----END PGP SIGNATURE-----
On Sun, 1 Jun 2003 00:16:35 +0200
Rikard Johnels
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello all.
I use mc quite frequently, but suddenly it has started behaving badly. As i enter 'mc' from the shell i usaly get the same folder opened. (eg. rikjoh@sparhawk:~> mc rikjoh@sparhawk:~>)
But since a little while back i get: rikjoh@sparhawk:~> mc 2;rikjoh@sparhawk:~1;sparhawkrikjoh@sparhawk:~>
And the "grey keys" doesnt work any more.
The only new thing i have done is using NIS for logons. But why should that have anything to do with that? Everything else works as usual...
Maybe your /.mc directory got messed up. If you don't have any special settings in there to save, just delete /.mc and it will get created next time you run it. It sounds odd, never heard of that problem before. Maybe one of the c libs, which mc depends on got changed or corrupted. Can you compile mc yourself? That would make sure your libs match up. -- use Perl; #powerful programmable prestidigitation
zentara wrote:
It sounds odd, never heard of that problem before. Maybe one
I saw the same thing on my Vaio with 8.2. 2;ottaky@vaio:~1;vaioottaky@vaio:~> The problem lies in the environment variables set to define the shell prompts - mine looked like this PS1='\[\e]2;\u@\h:$(ppwd)\007\e]1;\h\007\]\u@\h:\w> ' which displays fine in Bash, but confuses the hell out of mc ;-) Edit /etc/bash.bashrc and search for "_t" or, better, override the default in your ~/.bashrc by adding a line like this .. export PS1='\u@\h:\w> ' HTH sjb
The 03.06.01 at 00:16, Rikard Johnels wrote:
The only new thing i have done is using NIS for logons. But why should that have anything to do with that? Everything else works as usual...
mc behaves different depending on the therminal you use to login, and it can learn keyboard setups. I don't remember how these things are saved, though... -- Cheers, Carlos Robinson
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 01 June 2003 12.58, sjb wrote:
'\u@\h:\w> '
BINGO!!! That solved it!!! Why is the pompt so "confused" in the /etc/bash.bashrc ???? Is there a specific reason to have it that complicated? - -- /Rikard - ------------------------------------------------------------------------------------ Rikard Johnels email : rjhn@linux.nu Web : http://www.rikjoh.com Mob : +46 70 464 99 39 - ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78 46 1C EE 56 > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+27TLWdS2eEYc7lYRAi/JAJ0ZYpGjsgnw8fzih4/AHWK5PWR2vgCfZwgK 2k+C6G+lRF8in2AOmp7gM9I= =lN4q -----END PGP SIGNATURE-----
Rikard Johnels wrote:
BINGO!!! That solved it!!!
Why is the pompt so "confused" in the /etc/bash.bashrc ???? Is there a specific reason to have it that complicated?
It's a funky prompt - it sets your xterm window title to user@host And maybe some other stuff too, it's been years since I messed with it. Try "man bash" and search for PS1 or Google for "bash prompt howto" Cheers, sjb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 02 June 2003 05:34 pm, Rikard Johnels wrote:
On Sunday 01 June 2003 12.58, sjb wrote:
'\u@\h:\w> '
BINGO!!! That solved it!!!
Here's a diff for /etc/bash.bashrc that should give you the best of both worlds: - --- bash.bashrc.old 2003-06-03 11:01:47.000000000 -0300 +++ bash.bashrc 2003-06-03 11:00:24.000000000 -0300 @@ -115,8 +115,11 @@ else _u="\u@\h" _p=">" - - if test \( "$TERM" = "xterm" -o "${TERM#screen}" != "$TERM" \) -a -z "$EMACS" ; then - - _t="\[\e]2;\u@\h:\$(ppwd)\007\e]1;\h\007\]" + /bin/ps -C mc | /bin/grep -q $PPID + if [ $? != 0 ] ; then + if test \( "$TERM" = "xterm" -o "${TERM#screen}" != "$TERM" \) -a -z "$EMACS" ; then + _t="\[\e]2;\u@\h:\$(ppwd)\007\e]1;\h\007\]" + fi fi fi # With full path on prompt - -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+3Kvu+FOexA3koIgRAnTTAKCNCvHstIfMDv3dO/HCgHAqB1YzzwCfScz/ 0NyTCgUBZ+mKC6bTm1FJtO0= =QPsL -----END PGP SIGNATURE-----
participants (5)
-
Carlos E. R. -
James Oakley -
Rikard Johnels -
sjb -
zentara