bug#57936: closed (29.0.50; Make info treat "\n" in node names as "\s")

[GNU bug Tracking System]

Your message dated Thu, 13 Oct 2022 16:03:48 +0200
with message-id 
<CADwFkmks_yMP-0Fe2Z=zN9Pav5Leb5us75wbvu+RRTTccQB97w@mail.gmail.com>
and subject line Re: bug#57936: 29.0.50; Make info treat "\n" in node names as 
"\s"
has caused the debbugs.gnu.org bug report #57936,
regarding 29.0.50; Make info treat "\n" in node names as "\s"
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
57936: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57936
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: 29.0.50; Make info treat "\n" in node names as "\s" Date: Mon, 19 Sep 2022 12:12:38 -0400

Severity: wishlist
Tags: patch

I often find myself writing an email, and I paste something like:

(info "(elisp) Interactive Examples")

But it sometimes ends up wrapped over two lines and I need to manually
adjust it back from something like:

(info "(elisp) Interactive
Examples")

And then I have to fiddle around with the formatting, which is just a
bit boring.

So I think it would be nice if `info' would just treat the node name
"(elisp) Interactive\nExamples" as "(elisp) Interactive Examples".  See
the attached patch.

Thoughts?

0001-Make-info-treat-n-in-node-names-as-s.patch
Description: Text Data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#57936: 29.0.50; Make info treat "\n" in node names as "\s"
>
>
>
>
> Date: 
>
> Thu, 13 Oct 2022 16:03:48 +0200
>
>
>
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > Stefan Kangas <stefankangas@gmail.com> writes:
> >
> >> So I think it would be nice if `info' would just treat the node name
> >> "(elisp) Interactive\nExamples" as "(elisp) Interactive Examples".  See
> >> the attached patch.
> >>
> >> Thoughts?
> >
> > Makes sense to me, but:
> >
> >> +  (setq file-or-node
> >> +        (replace-regexp-in-string "\n" " " file-or-node))
> >
> > `string-replace', I think.
>
> Thanks, pushed with that change.
>
>
> --- End Message ---