From: Douglas Lewan <d.lewan2000@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Return values of (find-file-noselect), etc.
Date: Tue, 8 Jan 2019 14:12:27 -0500 [thread overview]
Message-ID: <c128f966-577a-afba-cd94-40193b4c1bce@gmail.com> (raw)
In-Reply-To: <jwvo98rm3du.fsf-monnier+gmane.emacs.help@gnu.org>
Ok. I'll look into it. Don't expect this immediately though. (One
problem I see right away is that associating an entry contents buffer
correctly might require a different mechanism.
On 01/08/2019 01:07 PM, Stefan Monnier wrote:
>>>> Either way, that's not what I'm seeing. Should this be recorded as a bug?
>>> I think it's a bug for a major mode function to change the current
>>> buffer, so what you're seeing is likely the result of find-file-noselect
>>> not protecting itself against such misbehaving major modes ;-)
>> Hmmm. I suppose I could make (cpio-mode) a function instead of a mode,
> I think using buffer-swap-text, you should be able to fairly easily make
> it so that cpio-mode is a proper major mode (e.g. doesn't change
> current-buffer) and yet moves the current buffer's contents to some
> auxiliary buffer and puts the dired-style interface in the current buffer.
> (and setup a change-major-mode-hook to reverse this if the user decides
> to change the major mode to something else like fundamental-mode).
>
>
> Stefan
>
>
--
,Doug
Douglas Lewan
+1 (908) 720-7908
Give me "assloads of config" over "some other person thought they could decide what I like" any day. - Szmo, on reddit, 2017 Sep 05
prev parent reply other threads:[~2019-01-08 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 19:06 Return values of (find-file-noselect), etc Douglas Lewan
2019-01-06 22:13 ` Stefan Monnier
2019-01-07 0:49 ` Douglas Lewan
2019-01-07 3:06 ` Stefan Monnier
2019-01-07 7:36 ` Douglas Lewan
2019-01-08 18:07 ` Stefan Monnier
2019-01-08 19:12 ` Douglas Lewan [this message]
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=c128f966-577a-afba-cd94-40193b4c1bce@gmail.com \
--to=d.lewan2000@gmail.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.
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).