From: Juri Linkov <juri@jurta.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
mark.lillibridge@hp.com, monnier@iro.umontreal.ca,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: Emacs's handling of line numbers [from bug#5042]
Date: Mon, 19 Apr 2010 00:29:21 +0300 [thread overview]
Message-ID: <87wrw4o3p2.fsf@mail.jurta.org> (raw)
In-Reply-To: <y2gf7ccd24b1004181003y74003accta3aad7f18277a575@mail.gmail.com> (Juanma Barranquero's message of "Sun, 18 Apr 2010 19:03:43 +0200")
>> IMO Juri did, by saying that user narrowing and widening commands
>> should not go beyond the current Info node.
>
> Again, user commands in the C-x n prefix map. And I would agree with
> that. Even if it is sometimes (how often?) useful to be able to widen
> the restriction in an Info buffer, that restriction is a programming
> convenience for Info-mode (that it uses narrowing is an implementation
> detail), so Info-mode should offer the way to deactivate it.
Yes, this is what I meant. The primitive function `widen' should
remove narrowing from the whole buffer completely as it currently does.
But a new user command `widen-command' bound to `C-x n w' should not
remove narrowing that was created programmatically, not by a user command
like `C-x n n'.
When authors of some mode decide that users should be able to remove
narrowing from the whole buffer completely then this mode should provide
a special command to do that.
And indeed, Info mode already has such a command. It is `g * RET'
that is documented in (info "(info) Go to node") as:
The node name `*' specifies the whole file. So you can look at all
of the current file by typing `g*<RET>' or all of any other file with
`g(FILENAME)*<RET>'.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2010-04-18 21:29 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 18:47 Emacs's handling of line numbers [from bug#5042] Mark Lillibridge
[not found] ` <jwvd4068dsr.fsf-monnier+emacs@gnu.org>
2010-04-11 22:22 ` Mark Lillibridge
2010-04-12 2:27 ` Stefan Monnier
2010-04-17 1:57 ` Mark Lillibridge
2010-04-17 7:29 ` Eli Zaretskii
2010-04-17 14:45 ` Stefan Monnier
2010-04-17 15:57 ` Eli Zaretskii
2010-04-17 19:51 ` Mark Lillibridge
2010-04-17 21:04 ` Eli Zaretskii
2010-04-17 21:17 ` Juanma Barranquero
2010-04-17 21:31 ` Drew Adams
2010-04-18 18:15 ` widen-one-level [was: Emacs's handling of line numbers] Drew Adams
2010-04-18 21:31 ` Juri Linkov
2010-04-19 0:25 ` Drew Adams
2010-04-18 23:30 ` Davis Herring
2010-04-19 19:57 ` Richard Stallman
2010-04-19 20:22 ` Drew Adams
2010-04-19 22:52 ` Juri Linkov
2010-04-19 1:56 ` Leo
2010-04-19 2:04 ` Drew Adams
2010-04-19 11:34 ` Leo
2010-04-19 16:31 ` Drew Adams
2010-04-19 17:57 ` Leo
2010-04-19 22:56 ` Drew Adams
2010-04-22 9:59 ` Leo
2010-04-18 3:12 ` Emacs's handling of line numbers [from bug#5042] Eli Zaretskii
2010-04-18 3:49 ` Juanma Barranquero
2010-04-18 8:05 ` Juri Linkov
2010-04-18 13:44 ` Drew Adams
2010-04-18 13:50 ` Lennart Borgman
2010-04-18 16:40 ` Drew Adams
2010-04-18 14:03 ` Juanma Barranquero
2010-04-18 14:14 ` David Kastrup
2010-04-18 16:41 ` Drew Adams
2010-04-18 17:03 ` Juanma Barranquero
2010-04-18 21:29 ` Juri Linkov [this message]
2010-04-18 13:45 ` Drew Adams
2010-04-18 17:29 ` Eli Zaretskii
2010-04-18 17:52 ` Juanma Barranquero
2010-04-18 17:56 ` Eli Zaretskii
2010-04-18 17:00 ` Mark Lillibridge
2010-04-18 17:38 ` Eli Zaretskii
2010-04-18 18:11 ` Lennart Borgman
2010-04-22 2:17 ` Mark Lillibridge
2010-04-22 8:06 ` David Kastrup
2010-04-22 8:38 ` Juri Linkov
2010-04-22 8:45 ` Juanma Barranquero
2010-06-06 18:18 ` Mark Lillibridge
2010-06-07 1:30 ` Stefan Monnier
2010-06-07 1:41 ` Lennart Borgman
2010-06-07 13:45 ` Stefan Monnier
2010-06-09 2:20 ` Mark Lillibridge
2010-06-09 3:44 ` Miles Bader
2010-06-09 2:19 ` Mark Lillibridge
2010-06-09 6:37 ` Glenn Morris
2010-06-24 2:24 ` Mark Lillibridge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wrw4o3p2.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=mark.lillibridge@hp.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.