Hi Arsen,
On 1/7/23 23:45, Arsen Arsenović wrote:
1) From a first peek, it's not obvious that there's a tree involved.
I've been given the suggestion of including a tree hierarchy on the
left side of the screen, if the screen is wide enough, that annotates
ones position in the info
On Tue, Jan 10, 2023 at 05:57:29PM +0100, Arsen Arsenović wrote:
> Hi Eli,
>
> Eli Zaretskii writes:
>
> > I'd expect downstream distros to do that already. If they don't,
> > maybe Texinfo should (although I'm not sure how to arrange for that in
> > a way that won't make the job of Texinfo
Gavin Smith writes:
> I'm tempted to suggest emphasizing the message with the use of colour.
> A patch is at the end of this mail.
>
> This would be distracting for users who already know how to use Info,
> of course.
>
> You can also make the message blink by adding | BLINK_MASK after
Evening Gavin,
Gavin Smith writes:
> On Tue, Jan 10, 2023 at 02:28:16PM +0100, Arsen Arsenović wrote:
>> Also, I didn't realize this before it was mentioned here, but yes,
>> ``(info)Help'' indeed comes with EMACS. Perhaps we should include a
>> copy in the Texinfo distribution too, or
On Tue, Jan 10, 2023 at 09:39:28PM +0100, Alejandro Colomar wrote:
> I don't have that documentation available. In which package is it?
$ dpkg -S /usr/share/info/libc.info.gz
glibc-doc-reference: /usr/share/info/libc.info.gz
This is on Linux Mint 20.3.
It's also available on the website:
On 1/10/23 21:39, Alejandro Colomar wrote:
Hi Gavin,
On 1/10/23 21:37, Gavin Smith wrote:
On Tue, Jan 10, 2023 at 09:14:35PM +0100, Alejandro Colomar wrote:
I'm curious about how away from man(7) pages that hypothetical GNU OS is.
Would you use info pages for libc functions?
So far, I
Hi Gavin,
On 1/10/23 21:37, Gavin Smith wrote:
On Tue, Jan 10, 2023 at 09:14:35PM +0100, Alejandro Colomar wrote:
I'm curious about how away from man(7) pages that hypothetical GNU OS is.
Would you use info pages for libc functions?
So far, I tried to find printf(3) with info(1), but `info
On Tue, Jan 10, 2023 at 09:14:35PM +0100, Alejandro Colomar wrote:
> I'm curious about how away from man(7) pages that hypothetical GNU OS is.
> Would you use info pages for libc functions?
>
> So far, I tried to find printf(3) with info(1), but `info printf` brings me
> to the documentation for
Hi Gavin,
On 1/10/23 20:45, Gavin Smith wrote:
On Tue, Jan 10, 2023 at 02:46:10PM +0200, Eli Zaretskii wrote:
From: Dave Kemper
Date: Mon, 9 Jan 2023 15:36:44 -0600
Cc: ar...@aarsen.me, alx.manpa...@gmail.com, g.branden.robin...@gmail.com,
help-texinfo@gnu.org
On 1/9/23, Eli
On Tue, Jan 10, 2023 at 02:28:16PM +0100, Arsen Arsenović wrote:
> Also, I didn't realize this before it was mentioned here, but yes,
> ``(info)Help'' indeed comes with EMACS. Perhaps we should include a
> copy in the Texinfo distribution too, or encourage downstreams to
> extract info.info out
On Tue, Jan 10, 2023 at 02:46:10PM +0200, Eli Zaretskii wrote:
> > From: Dave Kemper
> > Date: Mon, 9 Jan 2023 15:36:44 -0600
> > Cc: ar...@aarsen.me, alx.manpa...@gmail.com, g.branden.robin...@gmail.com,
> > help-texinfo@gnu.org
> >
> > On 1/9/23, Eli Zaretskii wrote:
> > > It is not a
On Mon, Jan 09, 2023 at 03:36:44PM -0600, Dave Kemper wrote:
> All I'm saying is, don't confuse YOUR (collective help-texinfo)
> worldview with THE worldview. The main points are: (a) the info
> program can accommodate both types of users; and (b) two small
> additions to the info man page will
On Sat, Jan 07, 2023 at 11:40:29PM +, Gavin Smith wrote:
> > This documentation describes the stand-alone Info reader which you can
> > use to read Info documentation.
> >
> >If you are new to the Info reader, then you can get started by typing
> > 'H' for a list of basic key bindings.
Hi Eli,
Eli Zaretskii writes:
> I'd expect downstream distros to do that already. If they don't,
> maybe Texinfo should (although I'm not sure how to arrange for that in
> a way that won't make the job of Texinfo release too complicated). I
> definitely agree that it would be good to have
> From: Arsen Arsenović
> Cc: Dave Kemper , alx.manpa...@gmail.com,
> g.branden.robin...@gmail.com, help-texinfo@gnu.org
> Date: Tue, 10 Jan 2023 14:28:16 +0100
>
> Also, I didn't realize this before it was mentioned here, but yes,
> ``(info)Help'' indeed comes with EMACS. Perhaps we should
Hi,
Eli Zaretskii writes:
>> From: Dave Kemper
>> Date: Mon, 9 Jan 2023 15:36:44 -0600
>> Cc: ar...@aarsen.me, alx.manpa...@gmail.com, g.branden.robin...@gmail.com,
>> help-texinfo@gnu.org
>>
>> On 1/9/23, Eli Zaretskii wrote:
>> > It is not a coincidence that the GNU project
> From: Dave Kemper
> Date: Mon, 9 Jan 2023 15:36:44 -0600
> Cc: ar...@aarsen.me, alx.manpa...@gmail.com, g.branden.robin...@gmail.com,
> help-texinfo@gnu.org
>
> On 1/9/23, Eli Zaretskii wrote:
> > It is not a coincidence that the GNU project deprecated man pages in
> > favor of Info
On 1/9/23, Eli Zaretskii wrote:
> It is not a coincidence that the GNU project deprecated man pages in
> favor of Info manuals.
A decision that, decades on, still does not garner universal acclaim.
But I'm not here to preach the superiority of one format or another,
merely to advocate offering
On Mon, Jan 09, 2023 at 06:52:44PM +0200, Eli Zaretskii wrote:
> It's an obscure capability that is useful in marginal situations. A
> large manual piped like this will present a humongously long linear
> text, and I doubt that the result will be a convenient read. It's
> again not an incident
> From: Dave Kemper
> Date: Mon, 9 Jan 2023 00:01:33 -0600
> Cc: Alejandro Colomar ,
> "G. Branden Robinson" , help-texinfo@gnu.org
>
> On 1/7/23, Arsen Arsenović wrote:
> > Alejandro Colomar writes:
> >> How about adding the following:
> >>
> >>For readers more familiar with manual
On 1/7/23, Arsen Arsenović wrote:
> Alejandro Colomar writes:
>> How about adding the following:
>>
>> For readers more familiar with manual pages, it might be interesting
>> to pipe info(1) through less(1):
>>
>> info info | less
>
> This suffers from decreased
Hi Arsen,
On 1/7/23 23:45, Arsen Arsenović wrote:
Hi Alex,
Alejandro Colomar writes:
Check out ``info "(info)Help"''.
That brings me to the same as `man info`.
Hmph, that might be an alias on my system. ``h'' should take you there,
though.
No. 'h' takes me to `info info`. It may
On Sat, Jan 07, 2023 at 11:45:32PM +0100, Arsen Arsenović wrote:
> >> That said, that could be
> >> done, if others agree, but I believe a better experience can be created
> >> by making the info format viewers themselves more accessible for people
> >> more used to pagers, or otherwise
Hi Alex,
Alejandro Colomar writes:
>> Check out ``info "(info)Help"''.
>
> That brings me to the same as `man info`.
Hmph, that might be an alias on my system. ``h'' should take you there,
though.
>> This page is also linked through the
>> info viewer welcome message: "Welcome to Info
On Sat, Jan 07, 2023 at 11:37:35PM +0100, Alejandro Colomar wrote:
> Hi Arsen,
>
> On 1/7/23 21:33, Arsen Arsenović wrote:
> > Hi Alex,
> >
> > Alejandro Colomar writes:
> >
> > > Hello,
> > >
> > > As someone with zero knowledge of how info(1) works, but considerable
> > > knowledge
> > >
On Sat, Jan 07, 2023 at 09:33:40PM +0100, Arsen Arsenović wrote:
> Hi Alex,
>
> Alejandro Colomar writes:
>
> > Hello,
> >
> > As someone with zero knowledge of how info(1) works, but considerable
> > knowledge
> > of how to read a manual page (well, there's little to it; less(1) is really
> >
Hi Arsen,
On 1/7/23 21:33, Arsen Arsenović wrote:
Hi Alex,
Alejandro Colomar writes:
Hello,
As someone with zero knowledge of how info(1) works, but considerable knowledge
of how to read a manual page (well, there's little to it; less(1) is really
simple), I'd like to recommend something
Hi Alex,
Alejandro Colomar writes:
> Hello,
>
> As someone with zero knowledge of how info(1) works, but considerable
> knowledge
> of how to read a manual page (well, there's little to it; less(1) is really
> simple), I'd like to recommend something for the info(1) manual page.
Check out
Hello,
As someone with zero knowledge of how info(1) works, but considerable knowledge
of how to read a manual page (well, there's little to it; less(1) is really
simple), I'd like to recommend something for the info(1) manual page.
The info(1) manual page seems to be little more than just a
29 matches
Mail list logo
