* bug#40900: Add face for function params in info
@ 2020-04-27 12:46 ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-27 15:06 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2020-04-27 12:46 UTC (permalink / raw)
To: 40900
The Elisp info manual could be easier to read if parameters which are capitalized
could have a face too:
If the minibuffer prompt string PROMPT does not end in ‘:’ ...
Though I don't know if it's possible to add language specific faces to info,
because a capitalized word could mean something else in an other language.
Maybe a face like Info-elisp-param-face which is added only if the current
info is about elisp?
Or simply generalizing it? Info-capitalized-word-face?
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#40900: Add face for function params in info
2020-04-27 12:46 bug#40900: Add face for function params in info ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2020-04-27 15:06 ` Eli Zaretskii
2020-09-09 13:22 ` Stefan Kangas
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2020-04-27 15:06 UTC (permalink / raw)
To: ndame; +Cc: 40900
> Date: Mon, 27 Apr 2020 12:46:02 +0000
> From: ndame via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> The Elisp info manual could be easier to read if parameters which are capitalized
> could have a face too:
>
> If the minibuffer prompt string PROMPT does not end in ‘:’ ...
>
>
> Though I don't know if it's possible to add language specific faces to info,
> because a capitalized word could mean something else in an other language.
>
> Maybe a face like Info-elisp-param-face which is added only if the current
> info is about elisp?
I think the challenge is to reliably identify the strings that are
function parameters. Info files lack the markup that identifies
various symbols in the Texinfo sources, and the code which finds
function arguments must not err too much, or users will complain.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#40900: Add face for function params in info
2020-04-27 15:06 ` Eli Zaretskii
@ 2020-09-09 13:22 ` Stefan Kangas
2020-09-09 15:03 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Stefan Kangas @ 2020-09-09 13:22 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 40900, ndame
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Mon, 27 Apr 2020 12:46:02 +0000
>> From: ndame via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> The Elisp info manual could be easier to read if parameters which are capitalized
>> could have a face too:
>>
>> If the minibuffer prompt string PROMPT does not end in ‘:’ ...
>>
>>
>> Though I don't know if it's possible to add language specific faces to info,
>> because a capitalized word could mean something else in an other language.
>>
>> Maybe a face like Info-elisp-param-face which is added only if the current
>> info is about elisp?
>
> I think the challenge is to reliably identify the strings that are
> function parameters. Info files lack the markup that identifies
> various symbols in the Texinfo sources, and the code which finds
> function arguments must not err too much, or users will complain.
Isn't this therefore a limitation in Texinfo? We could of course hack
around it, but it sounds like it would risk being error-prone and hard
to maintain.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#40900: Add face for function params in info
2020-09-09 13:22 ` Stefan Kangas
@ 2020-09-09 15:03 ` Eli Zaretskii
2020-09-09 15:18 ` Stefan Kangas
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2020-09-09 15:03 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 40900, ndame
> From: Stefan Kangas <stefan@marxist.se>
> Date: Wed, 9 Sep 2020 06:22:25 -0700
> Cc: ndame <ndame@protonmail.com>, 40900@debbugs.gnu.org
>
> > I think the challenge is to reliably identify the strings that are
> > function parameters. Info files lack the markup that identifies
> > various symbols in the Texinfo sources, and the code which finds
> > function arguments must not err too much, or users will complain.
>
> Isn't this therefore a limitation in Texinfo? We could of course hack
> around it, but it sounds like it would risk being error-prone and hard
> to maintain.
It is a limitation of the Info format produced from Texinfo sources.
For example, HTML format produced from Texinfo still has markup, which
could be used for such features.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#40900: Add face for function params in info
2020-09-09 15:03 ` Eli Zaretskii
@ 2020-09-09 15:18 ` Stefan Kangas
0 siblings, 0 replies; 5+ messages in thread
From: Stefan Kangas @ 2020-09-09 15:18 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 40900, ndame
tags 40900 + notabug
close 40900
thanks
Eli Zaretskii <eliz@gnu.org> writes:
> It is a limitation of the Info format produced from Texinfo sources.
> For example, HTML format produced from Texinfo still has markup, which
> could be used for such features.
So this limitation should be reported to the Texinfo maintainers. Once
the Info format has support for this, we could work on supporting it in
Emacs. I'm therefore closing this bug report.
If this conclusion is incorrect, please reply to this email (use "Reply
to all" in your email client) and we can reopen the bug report.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-09-09 15:18 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-27 12:46 bug#40900: Add face for function params in info ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-27 15:06 ` Eli Zaretskii
2020-09-09 13:22 ` Stefan Kangas
2020-09-09 15:03 ` Eli Zaretskii
2020-09-09 15:18 ` Stefan Kangas
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).