From: Amos Bird <amosbird@gmail.com>
To: Bob Proulx <bob@proulx.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: how can I get back to the dired buffer after closing the file buffer opened by dired?
Date: Tue, 31 Oct 2017 09:51:33 +0800 [thread overview]
Message-ID: <877evcoziy.fsf@gmail.com> (raw)
In-Reply-To: <20171030184232927408169@bob.proulx.com>
Hi Bob,
Thanks! It is due to some package that overrides
`kill-this-buffer'.
regards,
Bob Proulx <bob@proulx.com> writes:
> Amos Bird wrote:
>> I tried opening my files via `a` which runs
>> dired-find-alternate-file.
>
> Unfortunately 'a' probably was confused with 'f' as they do
> related by
> opposite things. Probably the suggestion was intended to
> suggest 'f'
> instead. Using 'a' replaces the dired buffer with the new file.
> That
> is the opposite of what you want.
>
> However 'f' does exactly the same as RET bound to
> dired-find-file and
> so will work the same.
>
> For me both RET and 'f' are bound to dired-find-file and both of
> those
> stack a new buffer. When I kill the buffer of the file I am
> returned
> to the previous buffer, including the dired buffer. What you
> are
> asking for is the behavior I have always seen and currently see.
>
> What version of emacs are you running? Please test the behavior
> using
> 'emacs -q' and 'emacs -Q' and see if the problem persists.
> Those
> avoid loading your own or any initialization. Quite often
> problems
> are due to customization. That will test if the problem is in
> the
> project or in the customization.
>
> Bob
--
Amos Bird
amosbird@gmail.com
next prev parent reply other threads:[~2017-10-31 1:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 16:09 how can I get back to the dired buffer after closing the file buffer opened by dired? Amos Bird
2017-10-29 21:37 ` Anast Gramm
2017-10-30 1:41 ` Amos Bird
2017-10-31 0:49 ` Bob Proulx
2017-10-31 1:51 ` Amos Bird [this message]
[not found] <mailman.2400.1509206973.27995.help-gnu-emacs@gnu.org>
2017-10-28 16:24 ` notbob
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877evcoziy.fsf@gmail.com \
--to=amosbird@gmail.com \
--cc=bob@proulx.com \
--cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.