public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: "Ondřej Bílka" <neleai@seznam.cz>
Cc: Joseph Myers <joseph@codesourcery.com>,
	Andreas Schwab <schwab@linux-m68k.org>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH v3][BZ #17787] Fix exponents in manual.
Date: Thu, 18 Jun 2015 15:54:00 -0000	[thread overview]
Message-ID: <5582E30E.7090700@redhat.com> (raw)
In-Reply-To: <20150618142917.GA16523@domone>

On 06/18/2015 10:29 AM, Ondřej Bílka wrote:
> On Tue, Jun 16, 2015 at 04:24:52PM -0400, Carlos O'Donell wrote:
>> On 06/16/2015 04:07 PM, Joseph Myers wrote:
>>> On Tue, 16 Jun 2015, Ondřej Bílka wrote:
>>>
>>>> Ping, if you have better idea I would like it.
>>>
>>> I've looked back at the previous discussion.  It seems clear enough that:
>>>
>>> * It's a bad idea to duplicate parts of sentences that don't need 
>>> duplicating.  Conditionals in the main manual should be around lines with 
>>> nothing more than the single word using @math.
>>
>> It's bad, but it's not terrible. I would rather see the manual get updated
>> than nit pick over the exact ways that this can get fixed.
>>
>>> * It should be possible to use a Texinfo macro for this and so avoid any 
>>> conditionals at all in the main manual.  Something like (untested)
>>>
>>> @iftex
>>> @macro twoexp{exp}
>>> 2^{\exp\}
>>> @end macro
>>> @end iftex
>>> @ifnottex
>>> @macro twoexp{exp}
>>> 2^{exp}
>>> @end macro
>>> @end itnottex
>>>
>>> (and then use @twoexp{63} etc.).
>>
>> That's a good suggestion.
>>
>> Cheers,
>> Carlos.
> 
> Thanks that works after fixing two typos. Here I use twoexp.
> 
>         * manual/filesys.texi: Fix exponents.
>         * manual/llio.texi: Likewise.
>         * manual/stdio.texi: Likewise.

Looks good to me.

Cheers,
Carlos.

      parent reply	other threads:[~2015-06-18 15:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 12:11 [PATCH][BZ " Ondřej Bílka
2015-01-05 14:15 ` Andreas Schwab
2015-01-06 11:57   ` Ondřej Bílka
2015-01-06 14:20     ` Andreas Schwab
2015-01-06 18:02       ` Ondřej Bílka
2015-01-06 18:09         ` Andreas Schwab
2015-01-06 21:32           ` Ondřej Bílka
2015-06-16 19:28     ` [PING][PATCH][BZ " Ondřej Bílka
2015-06-16 19:54       ` Carlos O'Donell
2015-06-16 20:24       ` Joseph Myers
2015-06-16 21:42         ` Carlos O'Donell
2015-06-18 15:26           ` [PATCH v3][BZ " Ondřej Bílka
2015-06-18 15:50             ` Joseph Myers
2015-06-18 16:05               ` Carlos O'Donell
2015-06-18 16:20                 ` Joseph Myers
2015-07-12  9:33                   ` [PATCH v4][BZ " Ondřej Bílka
2015-08-12 20:26                     ` [PING][PATCH " Ondřej Bílka
2015-08-19  6:33                       ` [PING^2][PATCH " Ondřej Bílka
2015-08-19 12:57                         ` Joseph Myers
2015-06-18 15:54             ` Carlos O'Donell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5582E30E.7090700@redhat.com \
    --to=carlos@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=neleai@seznam.cz \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).