From: "Omar Antolín Camarena" <omar@matem.unam.mx>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45686@debbugs.gnu.org
Subject: bug#45686: 28.0.50; Could minibuf-eldef-setup-minibuffer inhibit modifications hooks, please?
Date: Sun, 10 Jan 2021 08:57:23 -0600 [thread overview]
Message-ID: <87r1msyh4c.fsf@matem.unam.mx> (raw)
In-Reply-To: <87czycsvhu.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 10 Jan 2021 15:43:25 +0100")
> Well, I could see others wanting to trigger something on these
> modifications, too, so I'm not sure inhibiting these specific
> modifications from running the hooks would be a good general solution.
I cannot imagine anyone wanting to trigger something when eldef shortens
the prompt! But that could easily be a lack of imagination on my part. :)
I think my problem is that I'm wrong about what after-change-functions
is for. I thought it was supposed to trigger when the buffer changes due
to direct user actions, but the documentation says "after every change",
not "after user-initiated changes" or something like that. Maybe I just
need to re-adjust my expectations of when that hook runs.
> That looks like the correct solution for your use case?
Seems so.
> Anybody else got an opinion here?
I'd be interested to read other opinions, particularly if someone has a
useful example of triggering something to happen when eldef shortens the
prompt (since a single example would increase my powers of imagination!).
--
Omar
next prev parent reply other threads:[~2021-01-10 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 0:25 bug#45686: 28.0.50; Could minibuf-eldef-setup-minibuffer inhibit modifications hooks, please? Omar Antolín Camarena
2021-01-10 14:43 ` Lars Ingebrigtsen
2021-01-10 14:57 ` Omar Antolín Camarena [this message]
2021-06-04 10:26 ` Lars Ingebrigtsen
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=87r1msyh4c.fsf@matem.unam.mx \
--to=omar@matem.unam.mx \
--cc=45686@debbugs.gnu.org \
--cc=larsi@gnus.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).