Re: Go to my CWD!

[Andreas Röhler]

Kevin Rodgers wrote:
> Andrea Crotti wrote:
>> Whenever I have a shell or another interpreter of course they keep
>> they're own current directory, which is given from the first time I've
>> launched them.
>>
>> But if I for example call
>> M-x shell again it means that I want the shell in the directory of
>> the current
>> buffer, not that old forgotten position.
>
> `C-u M-x shell RET' will give you a new shell buffer named *shell*<2>
> whose default directory is the same as the buffer from which you called
> it.  
Storing it as a keyboard-macro, naming the macro, binding it to a key,
probably is better solution than having a separate function for it.

Andreas


> Subsequent shells will be named *shell*<3>, *shell*<4>, *shell*<5>
> etc.
>
>> That's also true for python interpreter or any other interpreter, is
>> there a way to solve this problem automatically?
>
> No, each interpreter starts comint in its own way.
>
>> Maybe a second call should kill and restart instead of visiting the
>> already open?
>
> Happy hacking,
>