On Fri, Nov 14, 2014 at 01:25:30PM +, Gavin Smith wrote:
I think the following fixes it. Could Patrice or Karl confirm?
Indeed, it looks ok. I will check the tests and commit on your behalf
if it is ok with you.
* tp/Texinfo/Convert/Plaintext.pm (_convert) @quotation with
@author:
Hi All,
I couldn't find a reference to this one in the archive, so:
RE: @quotation block
Version: makeinfo 5.2 (built from source on Fedora 20 x86_64)
Bug: Left margin is being indented, but right margin is not.
Documentation says:
“both the left and right margins are closer to the center
On Mon, Nov 03, 2014 at 11:22:26AM +0800, Mahlon wrote:
Hi All,
I couldn't find a reference to this one in the archive, so:
RE: @quotation block
Version: makeinfo 5.2 (built from source on Fedora 20 x86_64)
Bug: Left margin is being indented, but right margin is not.
Documentation
On Mon, Aug 25, 2014 at 08:33:53PM +0800, Mahlon Smith ( 马伦 ) wrote:
Hi Pat,
You are right that @section, @subsection and @subsubsection can be reserved
for the top level only.
However, @heading, @subheading and @subsubheading are explicitly defined in
the documentation as: You may use the
On Thu, Aug 21, 2014 at 10:30:44PM +, Karl Berry wrote:
Also, I am not sure we should add a test for it. If we do, then we
should also add a test for every command-line option and I am not
sure we want that.
Why not?
Anyway, I don't think we're necessarily obliged to test
On Mon, Aug 25, 2014 at 09:42:16AM +0800, Mahlon Smith ( 马伦 ) wrote:
Good Morning,
There is a formatting error for the: @heading, @subheading and
@subsubheading commands.
These commands generate underlining similar to the @section commands, but
can be used
anywhere and don't show up in
Hi Pat,
You are right that @section, @subsection and @subsubsection can be reserved
for the top level only.
However, @heading, @subheading and @subsubheading are explicitly defined in
the documentation as: You may use the '@heading' command anywhere you wish
for a section-style heading that will
Good Morning,
Sorry to be a pest, but better me than someone who has money riding on the
results.
makeinfo v:5.1:
There is a formatting error for the: @heading, @subheading and
@subsubheading commands.
These commands generate underlining similar to the @section commands, but
can be used
On Thu, Aug 21, 2014 at 10:30:45PM +, Karl Berry wrote:
except that I would have placed it a bit later. I'll do it and commit.
1) It seems your patch did not remove my block, so now those four lines
are in two places.
Are you sure it isn't a local non commited modification?
2)
On Wed, Aug 20, 2014 at 11:55:56PM +, Karl Berry wrote:
Hi Mahlon,
The largest of these is that v:5.1 ignores the '--fill-column' option.
Thanks for the report. It seems that the value from the cmdline was not
being propagated to the parsing; the change below appears to fix this.
On Wed, Aug 20, 2014 at 11:55:56PM +, Karl Berry wrote:
The largest of these is that v:5.1 ignores the '--fill-column' option.
Thanks for the report. It seems that the value from the cmdline was not
being propagated to the parsing; the change below appears to fix this.
I can't say
except that I would have placed it a bit later. I'll do it and commit.
1) It seems your patch did not remove my block, so now those four lines
are in two places.
2) In fact, I originally tried putting it later in the fn, which looks
more natural given the existing code. However, I found
Also, I am not sure we should add a test for it. If we do, then we
should also add a test for every command-line option and I am not
sure we want that.
Why not?
Anyway, I don't think we're necessarily obliged to test every single
cmdline option, and it wouldn't even be possible to
Hi Mahlon,
The largest of these is that v:5.1 ignores the '--fill-column' option.
Thanks for the report. It seems that the value from the cmdline was not
being propagated to the parsing; the change below appears to fix this.
I can't say I'm 100% sure this function (converter_initialize in
To TexInfo bug catcher:
I have recently updated my system and among the updates is a move from
makeinfo v:4.13 (x86_32) to makeinfo v:5.1 (x86_64)
I have run 'yum update texinfo' and it reports that I am up-to-date.
However, several things which worked in the previous version, are now out
to
On Tue, Aug 19, 2014 at 7:28 AM, Mahlon Smith ( 马伦 )
esl.tutor@gmail.com wrote:
The largest of these is that v:5.1 ignores the '--fill-column' option.
This means that 50+ pages of documentation, carefully-formatted for
'--fill-column=78' now look really bad.
A smaller matter:
a) There
An update on this one:
When I define the macro through
@macro texnl{}
@end macro
and invoke it through
@texnl
then it eats up all text until the next newline, like @c.
When I define the macro through
@macro texnl
@end macro
and invoke it through
@texnl
then it eats up all spaces
Only @texnl{} appears to work right.
Can this be either fixed or a warning added to the documentation?
As previously stated, it already is in the documentation. What would be
more useful is to have a warning in the code. Patrice?
Thanks,
k
Hi,
I'm using makeinfo-4.13, and define a macro that should take no arguments
and should produce an empty expansion. The texinfo doc says:
If a macro needs no parameters, you can define it either with an empty
list (`...@macro foo {}') or with no braces at all (`...@macro foo').
When I
Bruno Haible br...@clisp.org writes:
When I define the macro as follows:
@macro texnl{}
@end macro
and my input text is:
This is a more low-level API. The word break property is a property defined
in Unicode Standard Annex #29, section ``Word Boundaries'', see
20 matches
Mail list logo
