From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Implement texinfo @ref dwim
Date: Tue, 05 Feb 2019 18:31:28 +0200 [thread overview]
Message-ID: <83lg2utcwv.fsf@gnu.org> (raw)
In-Reply-To: <m2muna8mhs.fsf@gmail.com> (message from Robert Pluim on Tue, 05 Feb 2019 13:10:07 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Date: Tue, 05 Feb 2019 13:10:07 +0100
>
> This has been sitting around in my patch queue for a while, and Iʼd
> like to get it in so I can also get the manual update into the texinfo
> project. I think Iʼve addressed all the comments from the last time
> around.
Thanks, I think this command will be useful.
> * etc/NEWS: Describe new texinfo dwim reference functionality.
I understand that the corresponding update to the Texinfo manual will
be submitted to the Texinfo maintainers? If so, the NEWS entry should
be marked with "+++", I think.
> +(define-skeleton texinfo-insert-dwim-@ref
> + "Insert appropriate `@pxref{...}', `@xref{}', or `@ref{}' command.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Is Emacs smart enough not to highlight these as links?
> + ;; parenthesis
> + ((eq (char-before) ?\()
> + "@pxref{")
@pxref is also good inside parentheses, not just after the opening
paren. Can this command be smarter and support also cases like
(bla-bla yak-yak @pxref{foo})
?
> + ;; beginning of sentence
> + ((looking-back (sentence-end) (point-at-bol 0))
> + "@xref{")
What about BOB? Can we produce @xref there as well?
next prev parent reply other threads:[~2019-02-05 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 12:10 [PATCH] Implement texinfo @ref dwim Robert Pluim
2019-02-05 16:31 ` Eli Zaretskii [this message]
2019-02-05 19:42 ` Robert Pluim
2019-02-06 16:09 ` Eli Zaretskii
2019-02-06 18:05 ` Robert Pluim
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=83lg2utcwv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
/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.