From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Rainer M Krug <Rainer-vfylz/Ys1k4@public.gmane.org>
Cc: help-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: Rename Shell buffer with current directory
Date: Mon, 09 Dec 2013 13:22:38 +0100 [thread overview]
Message-ID: <86k3fe43jl.fsf@somewhere.org> (raw)
In-Reply-To: <52A58F09.1010409-vfylz/Ys1k4@public.gmane.org> (Rainer M. Krug's message of "Mon, 09 Dec 2013 10:36:09 +0100")
Hi Rainer,
Rainer M Krug wrote:
>> Michael Heerdegen wrote:
>>>> (defun my-rename-buffer-to-curdir (&optional _string) "Change
>>>> Shell buffer's name to current directory." (message "%s"
>>>> default-directory) (rename-buffer (concat "*shell "
>>>> default-directory "*")))
>>>>
>>>> (add-hook 'shell-mode-hook 'my-rename-buffer-to-curdir)
>>>>
>>>> (add-hook 'comint-output-filter-functions
>>>> 'my-rename-buffer-to-curdir nil t)
>>> ^
>>>> However, that does not change the end result: the name of the
>>>> buffer is unchanged.
>>>
>>> Why do you use a non-nil LOCAL parameter for `add-hook'? Without
>>> it, your code works for me.
>>
>> So does it for me -- thanks for your help!
>>
>> Though, I still don't understand why making the
>> `my-rename-buffer-to-curdir' function buffer-local makes the above
>> fail... Remember that that function gets called (see the message
>> displayed in the echo area), only the function `rename-buffer'
>> fails...
>
> Thanks - I am using your code, and it works very nicely - very useful.
You're welcome.
Though, I just realized it also renames R buffers (as it is bound to comint
mode). I'll have to make some exceptions there.
As well, it does not handle (yet) the problem of two Shell buffers in the same
directory, as the name won't be unique. Not sure what's the most
straightforward approach for this one. Maybe looking at `uniquify' or so.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-12-09 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 8:06 Rename Shell buffer with current directory Sebastien Vauban
2013-12-07 20:58 ` Michael Heerdegen
[not found] ` <mailman.8479.1386449940.10748.help-gnu-emacs@gnu.org>
2013-12-08 20:36 ` Sebastien Vauban
2013-12-08 21:32 ` Michael Heerdegen
[not found] ` <mailman.8618.1386538352.10748.help-gnu-emacs@gnu.org>
2013-12-09 8:36 ` Sebastien Vauban
2013-12-09 9:36 ` Rainer M Krug
[not found] ` <52A58F09.1010409-vfylz/Ys1k4@public.gmane.org>
2013-12-09 12:22 ` Sebastien Vauban [this message]
2013-12-09 12:56 ` Rainer M Krug
2013-12-09 18:16 ` Michael Heerdegen
[not found] ` <mailman.8695.1386613044.10748.help-gnu-emacs@gnu.org>
2013-12-09 18:44 ` Sebastien Vauban
2013-12-09 19:31 ` Michael Heerdegen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86k3fe43jl.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=Rainer-vfylz/Ys1k4@public.gmane.org \
--cc=help-gnu-emacs-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).