unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: npostavs@users.sourceforge.net, 24051@debbugs.gnu.org,
	phillip.lord@russet.org.uk
Subject: bug#24051: 24.5; doc of `external-debugging-output'
Date: Tue, 30 Jan 2018 15:29:09 +0200	[thread overview]
Message-ID: <83r2q7h3ve.fsf@gnu.org> (raw)
In-Reply-To: <87k1vzycvg.fsf@gmx.de> (message from Michael Albinus on Tue, 30 Jan 2018 09:22:43 +0100)

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Eli Zaretskii <eliz@gnu.org>,  24051@debbugs.gnu.org,  phillip.lord@russet.org.uk
> Date: Tue, 30 Jan 2018 09:22:43 +0100
> 
> > Ah, so there are.  I see some of them use @group, and some don't.  I
> > can't see any visible effect from @group so I left it out.
> 
> @group prevents page breaks in printed manuals in the following lines.

Right, and for that reason it's a good idea to use @group in this
case, to make sure @print{} doesn't get separated from the preceding
code fragment.

I actually suggest to have the Texinfo manual be loaded in some Info
buffer in your Emacs sessions; that's what I do.  Then you can quickly
consult it whenever the need arises.  That manual is very well
indexed, so finding what you need is usually a snap.

> > Hmm, it's a bit of an awkward fit, but yes, worth a mention (and actual
> > cross-references are only to nodes, not a single function entry, so "the
> > previous section" is already all the cross-reference needed, right?).
> 
> You can also declare an @anchor, and use it as target of a cross reference.

Right.  Also, the 2-argument form of @xref commands can also sometimes
land you on the text that is the second arg (at least with some Info
readers).





  reply	other threads:[~2018-01-30 13:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 16:01 bug#24051: 24.5; doc of `external-debugging-output' Drew Adams
2016-07-24 16:00 ` Phillip Lord
2018-01-28 23:22   ` Noam Postavsky
2018-01-28 23:49     ` Drew Adams
2018-01-29  0:24       ` Noam Postavsky
2018-01-29 14:47         ` Drew Adams
2018-01-30 13:52           ` Eli Zaretskii
2018-01-29 17:26         ` Eli Zaretskii
2018-01-30  0:38           ` Noam Postavsky
2018-01-30  8:22             ` Michael Albinus
2018-01-30 13:29               ` Eli Zaretskii [this message]
2018-01-30 14:00             ` Eli Zaretskii
2018-01-31  3:43               ` Noam Postavsky
     [not found]                 ` <87a7wtkecz.fsf@russet.org.uk>
2018-01-31 19:38                   ` Phillip Lord
     [not found]         ` <<bf7223d4-212a-417f-a39b-8835e2778168@default>
     [not found]           ` <<83k1vzh2rq.fsf@gnu.org>
2018-01-30 15:09             ` Drew Adams
2018-01-29 17:14     ` Eli Zaretskii

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=83r2q7h3ve.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24051@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=npostavs@users.sourceforge.net \
    --cc=phillip.lord@russet.org.uk \
    /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).