From: Stefan Monnier <monnier@iro.umontreal.ca>
To: jidanni@jidanni.org
Cc: 5364@debbugs.gnu.org
Subject: bug#5364: 23.1.91; execute-extended-command should do like FFAP
Date: Thu, 14 Jan 2010 10:12:33 -0500 [thread overview]
Message-ID: <jwveils3esk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87my0hgy29.fsf@jidanni.org> (jidanni@jidanni.org's message of "Thu, 14 Jan 2010 11:33:34 +0800")
SM> if you describe the cases where this repeatedly shows up for
SM> you, I can come up with a way to reconcile our difference.
> I sent tons in. And will keep on sending them... however as I am poorly
Single examples of "text at point" don't help me understand why this
happens *repeatedly*. If you could describe where those chunks of text
come from and why you end up using them in M-x, maybe that would help.
> organized, they end up all over the bug system. Anyway, how about: the
> burden is on you to show why it is so bad... what ever it is we were
It's bad to have a default in the prompt which is almost always not the
one you want. People will soon send bug reports about "M-x chooses dumb
defaults".
> just discussing... as right now I discovered C-x i (insert-file)
> doesn't even know that I want to insert e.g., /etc/motd even though my
> cursor is right next to it and I have FFAP turned on. Anyway, that's all
> that I'm still good for these days, alerting you fellows to such
> shortcomings. Yes, I did want to insert a file right next to its name today.
In the pretest code, we've solved this problem by making M-n bring up
the "file at point" if you have ffap loaded (IIUC). This should work
with all file-reading commands, contrary to FFAP itself which only
works for the commands it redefined.
So after C-x i, try M-n.
Stefan
next prev parent reply other threads:[~2010-01-14 15:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 12:52 bug#5364: 23.1.91; execute-extended-command should do like FFAP jidanni
2010-01-12 20:54 ` Juri Linkov
2010-01-12 22:46 ` jidanni
2010-01-13 0:32 ` Juri Linkov
2010-01-13 1:17 ` jidanni
2010-01-13 1:21 ` Stefan Monnier
2010-01-13 2:00 ` jidanni
2010-01-13 4:12 ` Stefan Monnier
2010-01-14 3:33 ` jidanni
2010-01-14 15:12 ` Stefan Monnier [this message]
2010-01-14 21:07 ` Juri Linkov
2010-01-14 22:40 ` Stefan Monnier
2010-01-15 1:12 ` Juri Linkov
2010-01-15 2:20 ` Stefan Monnier
2010-01-15 3:06 ` Chong Yidong
2010-01-15 7:49 ` Stefan Monnier
2010-01-15 9:19 ` Juri Linkov
2010-08-22 23:32 ` Juri Linkov
2010-01-13 7:26 ` Jan D.
2010-01-14 5:29 ` jidanni
2010-01-14 21:01 ` Juri Linkov
2010-01-15 3:04 ` jidanni
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=jwveils3esk.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=5364@debbugs.gnu.org \
--cc=jidanni@jidanni.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).