From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>,
"'Juanma Barranquero'" <lekktu@gmail.com>
Cc: 'Eli Zaretskii' <eliz@gnu.org>,
monnier@iro.umontreal.ca, mark.lillibridge@hp.com,
emacs-devel@gnu.org
Subject: RE: Emacs's handling of line numbers [from bug#5042]
Date: Sun, 18 Apr 2010 06:44:17 -0700 [thread overview]
Message-ID: <C43F5679F50E4C4E809E5BE55CFB067B@us.oracle.com> (raw)
In-Reply-To: <87aat1b2sr.fsf@mail.jurta.org>
> > For the same reason that the narrowing stack that Drew
> > proposes could be useful: if I'm reading an Info node, my
> > narrowing/widening shouldn't interfere with the use of narrowing
> > by Info-mode, because that's just an artifact of its
> > implementation. Being able to do M-x widen in an Info node
> > and seeing the whole buffer is IMO a "bug"
> > because it destroys the abstraction.
>
> I agree that user commands (with the prefix map `C-x n') should not
> widen or narrow the Info buffer outside of the current Info node.
> Only some low-level functions should be allowed to do this.
That's going too far, IMO. As Eli will perhaps point out (see bug #5839), there
are reasons that some users will want to widen Info buffers.
More generally, we should not remove `widen' as a command, even if in only some
contexts. Likewise, `narrow'. What we should do is provide more user control
(not less), possibly by creating a `widen-one-level' command as I suggested
earlier.
As I suggested in the thread for bug #5839, one way to at least not encourage
user narrowing when that might get users (especially newbies) into trouble,
would be to inhibit the activation of the `Narrow' lighter in the mode line (the
lighter would still be shown but would not act as a widening button).
next prev parent reply other threads:[~2010-04-18 13:44 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 [this message]
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
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=C43F5679F50E4C4E809E5BE55CFB067B@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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.