unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Emanuel Berg via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 49964@debbugs.gnu.org
Subject: bug#49964: 28.0.50; ERC button to docu, again
Date: Wed, 11 Aug 2021 19:18:33 +0200	[thread overview]
Message-ID: <871r6zc32u.fsf@zoho.eu> (raw)
In-Reply-To: <87fsviczd5.fsf@zoho.eu>

Lars Ingebrigtsen wrote:

>> I just wrote about this on
>> gmane.emacs.help/gmane.emacs.erc.general so I'll just reuse
>> that, I think it is clear what I mean :) Keep it up...
>>
>> 2. What is `this-convention' and ‘this‘? I always used
>>    `this-one' - I don't know/remember why, probably I saw
>>    someone else do it - but it seems in the on-line (*) help
>>    ‘this‘ is what happens, indeed even if you use
>>    `the-other-one' [see this example [1]]
>
> What do you mean by `this-convention'? I can't find that
> string in the Emacs tree.

Do

  $ emacs -Q test.el

and type `kill-emacs' and see what happens.

It gets buttonized to the help if used in ERC, I think that's
cool and helpful as well, for example in #emacs.

In the Emacs help tho it gets buttonized/hyperlinked as well
but converted to (respelled as) ‘kill-emacs‘, even if put as
`kill-emacs' in a docstring.

That notation, i.e. ‘kill-emacs‘, however does not get
highlighted/buttonized/hyperlinked in ERC, I don't know if
that is by intent.

Again take a look at the screenshot to see what happens:

  https://dataswamp.org/~incal/figures/emacs/erc-docu-button-again.png

-- 
underground experts united
https://dataswamp.org/~incal






  reply	other threads:[~2021-08-11 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 17:16 bug#49964: 28.0.50; ERC button to docu, again Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-10 14:47 ` Lars Ingebrigtsen
2021-08-11 17:18   ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-08-11 17:25     ` Lars Ingebrigtsen
2021-08-11 17:44       ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-25 15:24         ` Stefan Kangas

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=871r6zc32u.fsf@zoho.eu \
    --to=bug-gnu-emacs@gnu.org \
    --cc=49964@debbugs.gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).