[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: (g)mc-4.5.38-2 still broken



On Thu, 16 Sep 1999 19:54:11 +0200 (CEST), Piotr Roszatycki wrote:

>No no, it isn't mc script but only function in your ~/.bash_profile or
>global /etc/profile.
>
>I'm afraid many people have some kind of function or aliases related
>to _real_ mc binary and current mc wrapper can broke it.
>
>BTW, 
>/usr/bin/mcedit is a symlink to /etc/bin/mc which is an only wrapper.
>This is the reason that mcedit doesn't work already.

Quite.

And this has nothing to do with how much resources a bash takes up.
When the bash exits, control is returned to the original directory; no
matter what the bash script did.

And, the idea of editing /etc/profile or whatever is to my mind really
bad.

The upstream source for mc has sample scripts which users can call from
their own .bash_profile, .profile, etc, both for Bourne and C shells. 
They should be made available (they are also listed on the man page for
mc)

ps: the reason for not doing

 cd `mc -P "$@"`

is given in the man page.  Something to do with control-Z to suspend
doesn't work unless you use the temporary file method.

On Thu, 16 Sep 1999 19:54:11 +0200 (CEST), Piotr Roszatycki wrote:

>On 16 Sep 1999, Philip Hands wrote:
>
>> Wait a second.
>> 
>> So this mc script is an attempt to leave you in the directory you were
>> in when you left mc ?
>> 
>> Well that won't work will it?
>> 
>> Try running this:
>> 
>>   cd /tmp; ( cd /etc; pwd );  pwd
>
>No no, it isn't mc script but only function in your ~/.bash_profile or
>global /etc/profile.
>
>I'm afraid many people have some kind of function or aliases related
>to _real_ mc binary and current mc wrapper can broke it.
>
>BTW, 
>/usr/bin/mcedit is a symlink to /etc/bin/mc which is an only wrapper.
>This is the reason that mcedit doesn't work already.
>
>-- 
>
>Piotr "Dexter" Roszatycki
>mailto:dexter@fnet.pl
>
>
>-- 
>To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
>with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>



Reply to: