Update of bug #43126 (project texinfo):
Open/Closed:Open = Closed
Status:None = Invalid
___
Reply to this item at:
On Sun, Oct 19, 2014 at 04:45:41PM -0600, Karl Berry wrote:
Patrice,
That is, remove all CR before NL and replace all other CR with NL, not
worrying about whether a given file is consistent or not. I have seen
plenty of input files with inconsistent EOL conventions, due to
different people
Thaat could work on input, but it means that on output we must readd end
of lines everywhere.
I believe that it is fine to always output \n, period.
I am pretty sure that I used chomp in a attempt to be more portable...
Yes, the Perl manual leads one down that path. It increases
On Tue, Sep 02, 2014 at 09:17:56AM +0200, Vincent Belaïche wrote:
Just as a few side comments:
* it is probably worth checking whether @rmacro has the same issue
It has, it is almost the same as @macro.
* probably the perl script uses some hard-coded \n, rather than
some `endofline'
Patrice,
As I tried to write before ... I think by far the best approach would
be to s/\r?\n/\n/ on input files when they are read, and then have good
NL-only source to deal with henceforth. Oh, and I guess s/\r/\n/ too,
in case the input had CR without NL.
That is, remove all CR before NL and
Gavin Smith a écrit :
On Mon, Sep 1, 2014 at 7:15 PM, Vincent Belaïche
invalid.nore...@gnu.org wrote:
I have attached an example. There are two macros with identical definition
(only naming changed in order to avoid erroneous duplication of macro
definition).
One of the macro is defined in
Vincent Belaïche a écrit :
Gavin Smith a écrit :
On Mon, Sep 1, 2014 at 7:15 PM, Vincent Belaïche
[...]
Dear Gavin et alii,
I think that you have put the finger on it: it does not have to do
with @include but with line endings. I did the following experiment:
* both bug_texinfo.texi
* it would be good if it is not mandatory that all files used for a
single document have the same format,
I agree in principle.
The only rule should be that *within a same file* you have to
be consistent.
Maybe not even that. I regularly see files with mixed line endings.
URL:
http://savannah.gnu.org/bugs/?43126
Summary: Macros defined through @include make a spurious
space before @end macro
Project: texinfo - GNU documentation system
Submitted by: vincentb1
Submitted on: lun. 01 sept. 2014 18:15:31 GMT
On Mon, Sep 1, 2014 at 7:15 PM, Vincent Belaïche
invalid.nore...@gnu.org wrote:
I have attached an example. There are two macros with identical definition
(only naming changed in order to avoid erroneous duplication of macro
definition).
One of the macro is defined in the main file, while the
10 matches
Mail list logo
