From: Drew Adams <drew.adams@oracle.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: RE: Ordering of command completions
Date: Sun, 7 Dec 2014 13:26:36 -0800 (PST) [thread overview]
Message-ID: <05dfd1ec-0530-4c76-8079-1a4d2ed8be80@default> (raw)
In-Reply-To: <87iohntbk2.fsf@wanadoo.es>
> > Sounds good to me, I guess. Is there a way for a user to advise
> > such a command to change or remove the declaration? Is `declare'
> > amenable to advising?
>
> Dunno. What scenario do you have on mind?
A user ... not wanting a particular command to be excluded ...
for whatever usery reason. How to override the exclusion?
> As a last resort, the user could define a new interactive function,
> without associated restrictions, that simply calls the "hidden" one.
Sure, people can always rewrite the code we provide. That's not
what is generally meant by user control over commands, in Emacs.
> Besides, the filtering would be optional, of course.
Optionally completely on or completely off is not what I'm
getting at, either.
We are talking about providing declarations at the individual
command level (and possibly at the file/package/mode level).
Users should be able to change that behavior for an individual
command, just as you can declare it for an individual command.
That's what advice is for: tweaking an individual function.
Users should not need to redefine commands, if we can give them
a better way.
next prev parent reply other threads:[~2014-12-07 21:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 16:14 Ordering of command completions Tom
2014-12-07 16:28 ` Lars Magne Ingebrigtsen
2014-12-07 17:36 ` Andreas Schwab
2014-12-07 17:42 ` Lars Magne Ingebrigtsen
2014-12-07 21:20 ` Lars Magne Ingebrigtsen
2014-12-07 21:33 ` Lars Magne Ingebrigtsen
2014-12-07 21:47 ` Lars Magne Ingebrigtsen
2014-12-07 22:00 ` Autoload cookies (was: Ordering of command completions) Lars Magne Ingebrigtsen
2014-12-07 22:03 ` Autoload cookies Daniel Colascione
2014-12-07 22:08 ` Lars Magne Ingebrigtsen
2014-12-07 22:06 ` Andreas Schwab
2014-12-08 0:14 ` Autoload cookies (was: Ordering of command completions) Artur Malabarba
2014-12-07 22:05 ` Ordering of command completions Óscar Fuentes
2014-12-07 22:13 ` Lars Magne Ingebrigtsen
2014-12-08 0:53 ` Artur Malabarba
2014-12-08 0:56 ` Artur Malabarba
2014-12-07 18:33 ` Óscar Fuentes
2014-12-07 18:42 ` Drew Adams
2014-12-07 19:37 ` Óscar Fuentes
2014-12-07 20:10 ` Drew Adams
2014-12-07 20:24 ` Óscar Fuentes
2014-12-07 20:42 ` Drew Adams
2014-12-07 21:06 ` Óscar Fuentes
2014-12-07 21:26 ` Drew Adams [this message]
2014-12-07 18:45 ` Lars Magne Ingebrigtsen
2014-12-07 18:59 ` Óscar Fuentes
2014-12-07 20:34 ` Lars Magne Ingebrigtsen
2014-12-07 20:47 ` Drew Adams
2014-12-07 21:20 ` Stefan Monnier
2014-12-07 21:25 ` Lars Magne Ingebrigtsen
2014-12-08 9:51 ` define "out-of-tree"? Stephen Leake
2014-12-08 18:04 ` Lars Magne Ingebrigtsen
2014-12-09 11:00 ` Richard Stallman
2014-12-09 20:00 ` Karl Fogel
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=05dfd1ec-0530-4c76-8079-1a4d2ed8be80@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).