From: Eli Zaretskii <eliz@gnu.org>
To: Sivaram Neelakantan <nsivaram.net@gmail.com>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Insufficient documentation on *how* to change SPC behaviour in minibuffer
Date: Sat, 07 Jul 2007 12:46:07 +0300 [thread overview]
Message-ID: <uy7hsbl7k.fsf@gnu.org> (raw)
In-Reply-To: <uk5td8l63.fsf@gmail.com> (message from Sivaram Neelakantan on Fri, 06 Jul 2007 23:33:00 +0530)
> From: Sivaram Neelakantan <nsivaram.net@gmail.com>
> Date: Fri, 06 Jul 2007 23:33:00 +0530
> User-Mail-Address: nsivaram.net@gmail.com
>
> As for the documentation, well yes that would make sense. But would
> it be also useful to put it under Emacs-Minibuffer-Completion Commands
> section in the info manual?
>
> Similar to the way, how Emacs recognises sentences (2 spaces vs
> 1aftera period) and how the manual explains how to switch from one to
> the other, I think, there should be a similar explanation in the main
> info manual.
I don't think these two situations are similar. One space after a
period that ends a sentence is a widely used convention that has its
roots in cultural differences that are outside Emacs's domain. By
contrast, the key bindings in the minibuffer prompts for file names is
(a) purely an Emacs issue, and (b) we firmly believe that most people
will be happy with the new bindings (or else we wouldn't be making
them the default).
prev parent reply other threads:[~2007-07-07 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 18:23 Insufficient documentation on *how* to change SPC behaviour in minibuffer Sivaram Neelakantan
2007-07-06 16:16 ` Eli Zaretskii
2007-07-06 18:03 ` Sivaram Neelakantan
2007-07-06 18:26 ` Insufficient documentation on *how* to change SPC behaviour inminibuffer Drew Adams
2007-07-07 9:48 ` Eli Zaretskii
2007-07-07 12:37 ` Insufficient documentation on *how* to change SPC behaviourinminibuffer Drew Adams
2007-07-07 20:47 ` Insufficient documentation on *how* to change SPC behaviour inminibuffer Richard Stallman
2007-07-07 9:46 ` Eli Zaretskii [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=uy7hsbl7k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=nsivaram.net@gmail.com \
/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).