unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman'" <lennart.borgman@gmail.com>
Cc: 'Juanma Barranquero' <lekktu@gmail.com>,
	mark.lillibridge@hp.com, emacs-devel@gnu.org,
	'Juri Linkov' <juri@jurta.org>,
	monnier@iro.umontreal.ca, 'Eli Zaretskii' <eliz@gnu.org>
Subject: RE: Emacs's handling of line numbers [from bug#5042]
Date: Sun, 18 Apr 2010 09:40:54 -0700	[thread overview]
Message-ID: <CA353C9277814CFDAE622D2A0D3CE071@us.oracle.com> (raw)
In-Reply-To: <w2we01d8a51004180650r55afdc7dg206c6f6b3d46418@mail.gmail.com>

> >> > 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.
> 
> I think Juri sugggested that there should not be an interactive
> command for doing that. Would not low level elisp functions be enough
> for the purpose of widening Info buffers?

(All commands are interactive.) Yes, I understood that that was Juri's
suggestion.

I disagree - `widen' should be a user command. And it should be available (but
not especially encouraged) in Info - see the reasons that Eli gave in the bug
#5839 thread as one example.

The proper way to tame widening is not to eliminate `widen' as a user command or
to restrict its use in a coarse, black-and-white way. The proper way is to:

1. Remove the button on the `Narrow' lighter in modes such as Info where we
don't want newbies to narrow without knowing what they're doing. (And perhaps
(_perhaps_), in such contexts, also ask for confirmation if the user invokes
`widen' in such a context. We already disable the command by default.)

2. Provide another command, `widen-one-level', which gives users more control
over the scope of widening. It would give them the same degree of control they
have now for narrowing. (No, this wouldn't prevent a user from widening to the
top level in Info, but it would give users more control generally.)





  reply	other threads:[~2010-04-18 16:40 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 [this message]
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

  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=CA353C9277814CFDAE622D2A0D3CE071@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=lennart.borgman@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 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).