* On 2020 17 Feb 12:38 -0600, Morten Bo Johansen wrote:
> On 2020-02-17 Nate Bargmann wrote:
>
> > I have used oinfo for a long time.
>
> You meant to say pinfo? ;)
I did, indeed.
Vim highlighted it but I paid no further attention.
Sigh...
- Nate
--
"The optimist proclaims that we live in
On 2020-02-17 Nate Bargmann wrote:
> I have used oinfo for a long time.
You meant to say pinfo? ;)
Morten
--
Ginsburg's Law:
At the precise moment you take off your shoe in a shoe store, your
big toe will pop out of your sock to see what's going on.
* On 2020 17 Feb 07:59 -0600, Mike Bianchi wrote:
> On Sun, Feb 16, 2020 at 07:55:31PM -0800, Larry McVoy wrote:
> > I *hate* info. It has made Linux less available to a lot of people.
>
> BUT info sometimes has information that man(1) lacks.
>
> So _maybe_ an approach would be to make an
On Monday, 17 February 2020 13:32:36 GMT Dave Kemper wrote:
> Considering that groff's own documentation is (perversely? ironically?
> choose your own adverb) written in Texinfo format, a discussion of the
> merits of that format could be considered on topic here (if a bit
> academic, since no one
On Feb 17 08:58:04, mbian...@foveal.com wrote:
> On Sun, Feb 16, 2020 at 07:55:31PM -0800, Larry McVoy wrote:
> > I *hate* info. It has made Linux less available to a lot of people.
>
> BUT info sometimes has information that man(1) lacks.
AFAIK, it is quite usual in GNU to maintain a texinfo
On Mon, Feb 17, 2020 at 08:58:04AM -0500, Mike Bianchi wrote:
> On Sun, Feb 16, 2020 at 07:55:31PM -0800, Larry McVoy wrote:
> > I *hate* info. It has made Linux less available to a lot of people.
>
What about tkinfo?
ulrich lauther
On Sun, Feb 16, 2020 at 07:55:31PM -0800, Larry McVoy wrote:
> I *hate* info. It has made Linux less available to a lot of people.
BUT info sometimes has information that man(1) lacks.
So _maybe_ an approach would be to make an info2(1) command that had access
to the same information with a
On Mon, Feb 17, 2020 at 08:56:25PM +1100, John Gardner wrote:
> That's not what I'm talking about. In Emacs, I'm used to smashing `c-h o`
> to bring up the documentation for the symbol at point. In info(1), I've no
> idea where or what to even begin searching for to find a symbol's
>
> I won't say more on this topic. We are on a groff list.
Considering that groff's own documentation is (perversely? ironically?
choose your own adverb) written in Texinfo format, a discussion of the
merits of that format could be considered on topic here (if a bit
academic, since no one is
gbranden pushed a commit to branch master
in repository groff.
commit d9d52efc87e591508d81f93467759907a8d41ff1
Author: G. Branden Robinson
AuthorDate: Mon Feb 17 23:10:26 2020 +1100
groff_man(7): Update historical information.
* Expand history section to cover the remainder of the
> ??? Have you actually used stand-alone `info` recently? In its
> standard configuration, you only need the arrow keys together with the
> enter key to navigate.
That's not what I'm talking about. In Emacs, I'm used to smashing `c-h o`
to bring up the documentation for the symbol at point. In
>> The info stuff alienates anyone who is not an emacs fan
>
> The standalone info(1) program, though? Please. I'm not going to
> learn a second set of keybindings just to navigate online help.
??? Have you actually used stand-alone `info` recently? In its
standard configuration, you only
12 matches
Mail list logo
