[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [screen-devel] Problems in screen.1
From: |
Amadeusz Sławiński |
Subject: |
Re: [screen-devel] Problems in screen.1 |
Date: |
Wed, 13 Jun 2018 00:16:26 +0200 |
On Tue, 12 Jun 2018 17:53:16 -0400
"Eric S. Raymond" <address@hidden> wrote:
> Amadeusz Sławiński <address@hidden>:
> > On Tue, 12 Jun 2018 15:16:13 -0400 (EDT)
> > address@hidden wrote:
> >
> > > -This is version 4.3.1. Its roots are a merge of a custom version
> > > +This is version 4.3.0. Its roots are a merge of a custom version
> >
> > Hi,
> >
> > seems interesting, but it seems to've been run against old version of
> > screen?
>
> Probably. I run my tests against package-installed versions of man
> pages because trying to fetch repo versions of every page in my
> distribution's nan directories would be impossibly complicated.
>
> > Current release is 4.6.2 and git branches have some more fixes to manpages.
> > Any chance it can be run against git (screen-v4 and master branch) or
> > can you tell me how to run it?
>
> See below...
>
> > It would be useful if "automated" bugreport system included version of
> > package, it was run against as well as some reproduction instructions.
>
> Not practical, alas. There's no uniform way to get the version, and at
> over 500 patches it's too big to do by hand.
If you install from package manager I'm pretty sure there should be a way
to ask to which package file belongs and then somehow get version.
For example on Gentoo I can do something like:
# equery b /usr/share/man/man1/screen.1.bz2
* Searching for /usr/share/man/man1/screen.1.bz2 ...
app-misc/screen-9999 (/usr/share/man/man1/screen.1.bz2)
9999 being git version in this case
# equery b /usr/share/man/man1/zsh.1.bz2
* Searching for /usr/share/man/man1/zsh.1.bz2 ...
app-shells/zsh-5.5.1-r1 (/usr/share/man/man1/zsh.1.bz2)
5.5.1 being version and r1 being distribution patchset release
anyway knowing distribution and package version should be enough in most cases.
> > (Tried looking at manlifter and doclifter documentation, and I'm unsure
> > how to run it to get a patch)
> >
> > $ manlifter -m ...../screen/src/doc/screen.1
> > Trying ...../screen/src/doc/screen.1
> > "./foobar.man", line 8: error - uninterpreted 'schar' command
> > "./foobar.man", line 4835: there were 1 errors during translation
> > doclifter error status: 1
>
> I see how you got confused. I'm afraid manlifter isn't very useful
> outside my specialized test setup. It's really intended to be used for
> test-translating an entirte man tree.
>
> It looks like your page uses the groff .schar extension to define a glyph.
>
> If you email me a current copy I'll try to fix it up for you.
Ah ok, it's not me being tired then ;)
You can find plain text versions here (they should be mostly similar,
but there are some differences):
https://git.savannah.gnu.org/cgit/screen.git/plain/src/doc/screen.1?h=screen-v4
https://git.savannah.gnu.org/cgit/screen.git/plain/src/doc/screen.1
Cheers,
Amadeusz
- [screen-devel] Problems in screen.1, esr, 2018/06/12
- Re: [screen-devel] Problems in screen.1, Amadeusz Sławiński, 2018/06/12
- Re: [screen-devel] Problems in screen.1, Eric S. Raymond, 2018/06/12
- Re: [screen-devel] Problems in screen.1,
Amadeusz Sławiński <=
- Re: [screen-devel] Problems in screen.1, Eric S. Raymond, 2018/06/12
- Re: [screen-devel] Problems in screen.1, Amadeusz Sławiński, 2018/06/13
- Re: [screen-devel] Problems in screen.1, Eric S. Raymond, 2018/06/13
- Re: [screen-devel] Problems in screen.1, Amadeusz Sławiński, 2018/06/13
- Re: [screen-devel] Problems in screen.1, Marcin Cieslak, 2018/06/13
- Re: [screen-devel] Problems in screen.1, Eric S. Raymond, 2018/06/13
- Re: [screen-devel] Problems in screen.1, Amadeusz Sławiński, 2018/06/21
Re: [screen-devel] Problems in screen.1, Axel Beckert, 2018/06/12