unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: emacs-devel@gnu.org
Subject: Re: Suggestion: Let the help command load autoloaded functions etc
Date: Sat, 22 Dec 2007 11:36:05 +0100	[thread overview]
Message-ID: <87zlw3qane.fsf@ambire.localdomain> (raw)
In-Reply-To: <E1J5xsF-0001pH-Jh@fencepost.gnu.org> (Richard Stallman's message of "Sat, 22 Dec 2007 01:30:15 -0500")

() Richard Stallman <rms@gnu.org>
() Sat, 22 Dec 2007 01:30:15 -0500

   That would be an ok feature, since it
   would not do anything automatically.

i don't think it would be always ok.  for example, consider a set
of interdependent libraries misbehaving when components are loaded
in the wrong order.  the result is curiosity- but not necessarily
user-induced bug reports.  i would hate to have this conversation:

 user      : i clicked on "foo link" and emacs barfed: FOO-ERROR.
 programmer: well don't do that.
          u: well, why is that link displayed?
          p: because we don't handle "improper load sequence".
          u: what is the "proper load sequence"?
          p: advertized entry point is M-x bar RET.
          u: what does that have to do w/ foo?
          p: nothing.
          u: ???

in other words, i personally am disinclined to support this kind
of fuzziness (entering the subroutine from the side).

thi

  reply	other threads:[~2007-12-22 10:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 18:26 Suggestion: Let the help command load autoloaded functions etc Lennart Borgman (gmail)
2007-12-21  3:05 ` Richard Stallman
2007-12-21  8:39   ` Lennart Borgman (gmail)
2007-12-21 10:44     ` Jason Rumney
2007-12-21 16:20       ` Lennart Borgman (gmail)
2007-12-21 16:43         ` Jason Rumney
2007-12-21 17:35           ` Lennart Borgman (gmail)
2007-12-21 17:40             ` Leo
2007-12-21 18:46               ` Lennart Borgman (gmail)
2007-12-22  9:57                 ` Eli Zaretskii
2007-12-22  6:30         ` Richard Stallman
2007-12-22 10:36           ` Thien-Thi Nguyen [this message]
2007-12-22 10:42             ` Lennart Borgman (gmail)
2007-12-22 10:45               ` Lennart Borgman (gmail)
2007-12-22 11:23               ` Robert J. Chassell
2007-12-22 11:44               ` Thien-Thi Nguyen
2007-12-22 21:08             ` Richard Stallman
2008-07-16 10:28           ` Lennart Borgman (gmail)
2008-07-16 10:54             ` David Kastrup
2008-07-16 11:01               ` Lennart Borgman (gmail)
2008-07-16 11:08                 ` David Kastrup
2008-07-16 11:55                   ` Lennart Borgman
2008-07-16 19:02                     ` Stephen J. Turnbull
2008-07-16 19:55                       ` David Kastrup
2008-07-16 21:11                         ` Lennart Borgman (gmail)
2008-07-16 22:40                         ` Stephen J. Turnbull
2008-07-17  6:36                           ` David Kastrup
2008-07-17  8:49                             ` Stephen J. Turnbull
2008-07-17  9:56                               ` David Kastrup
2008-07-17 10:41                                 ` Lennart Borgman (gmail)
2008-07-17 22:54                         ` Richard M Stallman
2007-12-22  6:29     ` Richard Stallman

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=87zlw3qane.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=emacs-devel@gnu.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).