From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: read-command, read-variable, read-buffer implemented in C
Date: Sat, 13 Dec 2014 05:25:52 +0100 [thread overview]
Message-ID: <877fxw9nvz.fsf@wanadoo.es> (raw)
I guess it is an historical artifact due to performance concerns, but
now it doesn't make much sense anymore, right?
Some extensions need to jump through hoops because of this. For using
Ido (almost) everywhere it would be enough to advise `completing-read',
which is what those functions end using, but as advices are not
effective for functions defined in C when they are called from other C
functions, extensions such as ido-hacks are forced to advise the
functions that call read-*, which is quite a hassle.
Or I'm wrong wrt adivising C functions and overlooking other
considerations?
next reply other threads:[~2014-12-13 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 4:25 Óscar Fuentes [this message]
2014-12-13 5:53 ` read-command, read-variable, read-buffer implemented in C Stefan Monnier
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=877fxw9nvz.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=emacs-devel@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 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).