Package: lesspipe Severity: minor Tags: patch l10n Version: 643-1 Dear less maintainer, the manpage-l10n project maintains a large number of translations of man pages both from a large variety of sources (including less) as well for a large variety of target languages.
During their work translators notice different possible issues in the
original (english) man pages. Sometimes this is a straightforward
typo, sometimes a hard to read sentence, sometimes this is a
convention not held up and sometimes we simply do not understand the
original.
We use several distributions as sources and update regularly (at
least every 2 month). This means we are fairly recent (some
distributions like archlinux also update frequently) but might miss
the latest upstream version once in a while, so the error might be
already fixed. We apologize and ask you to close the issue immediately
if this should be the case, but given the huge volume of projects and
the very limited number of volunteers we are not able to double check
each and every issue.
Secondly we translators see the manpages in the neutral po format,
i.e. converted and harmonized, but not the original source (be it man,
groff, xml or other). So we cannot provide a true patch (where
possible), but only an approximation which you need to convert into
your source format.
Finally the issues I'm reporting have accumulated over time and are
not always discovered by me, so sometimes my description of the
problem my be a bit limited - do not hesitate to ask so we can clarify
them.
I'm now reporting the errors for your project. If future reports
should use another channel, please let me know.
First of all, is there a common upstream for lesspipe(1)? The upstream
authors of less disclaim any source, but I see that many distributions
ship lesspipe(1), hence reporting it to the true upstream instead of
here might be more sensible.
Man page: lesspipe.1
Issue 1: less → B<less>(1)
Issue 2: ~/.bashrc → I<~/.bashrc>
Issue 3: ~/.bash_profile → I<~/.bash_profile>
"Sometimes, less does not display the contents file you want to view but "
"output that is produced by your login scripts (~/.bashrc or ~/."
"bash_profile). This happens because less uses your current shell to run the "
"lesspipe filter. Bash first looks for the variable $BASH_ENV in the "
"environment expands its value and uses the expanded value as the name of a "
"file to read and execute. If this file produces any output less will display "
"this. A way to solve this problem is to put the following lines on the top "
"of your login script that produces output:"
--
ssue 1: I<less> → B<less>(1)
Issue 2: less → B<less>(1)
"I<lesspipe> will toss the contents/info on STDOUT and I<less> will read them "
"as they come across. This means that you do not have to wait for the "
"decoding to finish before less shows you the file. This also means that you "
"will get a 'byte N' instead of an N% as your file position. You can seek to "
"the end and back to get the N% but that means you have to wait for the pipe "
"to finish."
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
