unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Stefan Guath <stefan@automata.se>
Cc: 17685@debbugs.gnu.org
Subject: bug#17685: 24.3.91.1; help-C-file-name failes to create temp buffer " *DOC*"
Date: Wed, 04 Jun 2014 09:15:41 -0400	[thread overview]
Message-ID: <jwvsinkhlfe.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <DAF05340-A751-46D1-BD50-25E853987F73@automata.se> (Stefan Guath's message of "Wed, 4 Jun 2014 10:47:44 +0200")

> emacs -Q
> (find-lisp-object-file-name 'visible-bell 'defvar) ;visible-bell is just an
> example and can be replaced with any variable.

> RESULT:
> C-source

> EXPECTED RESULT:
> "src/dispnew.c"

Here's the reason for the behavior:
the DOC file is moderately large, so we don't want to load it into
memory just because the user did C-h v visible-bell RET.

So we only populate the *DOC* buffer when the user actually clicks on
the "C-source" link to jump to the source code.  And once the buffer is
populated, then there's no reason not to use it, so if *DOC* exists then
we do use it.

We could probably change it so that we always populate the *DOC* buffer
in the case where the C sources are available (so the behavior would
stay unchanged for users running pre-compiled Emacs, while it would
work better for those users who compile it themselves and keep the
source in place).  But I'm not sure it'd really be an improvement.


        Stefan





  reply	other threads:[~2014-06-04 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  8:47 bug#17685: 24.3.91.1; help-C-file-name failes to create temp buffer " *DOC*" Stefan Guath
2014-06-04 13:15 ` Stefan Monnier [this message]
2014-06-04 14:08   ` Drew Adams
2014-06-04 14:21     ` Stefan Monnier
2014-06-05  6:46   ` Stefan Guath
2014-06-05  7:48     ` martin rudalics
2014-06-05  8:35       ` Stefan Guath
2014-06-05  8:45         ` martin rudalics
2014-06-05  9:00           ` Stefan Guath
2014-06-05 13:51         ` Stefan Monnier
2022-02-08 10:11       ` Lars Ingebrigtsen

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=jwvsinkhlfe.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=17685@debbugs.gnu.org \
    --cc=stefan@automata.se \
    /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).