Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> Hello Jim, all,
>
> * Jim Meyering wrote on Fri, Sep 07, 2007 at 09:35:14PM CEST:
>>
>> I prefer ..h, too. Does anyone object?
>
> Two reasons against it: it looks too much like a typo gone mad.
> And if you ever happen to use portable make inference ru
Hello Jim, all,
* Jim Meyering wrote on Fri, Sep 07, 2007 at 09:35:14PM CEST:
>
> I prefer ..h, too. Does anyone object?
Two reasons against it: it looks too much like a typo gone mad.
And if you ever happen to use portable make inference rules,
then ..h (or any suffix with more than one dot) w
I prefer ..h, too. Does anyone object?
I don't object myself, but since this whole thread started (as I
understand it) because rms complained, you might want to ask him too.
k
Paul Eggert <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> I admit that .eh seems a little odd, and would
>> require everyone to teach their editor about the new suffix.
>
> True; that's a pain.
>
>> How about the "..h" suffix, e.g., stdlib..h? Do we care enough
>> abou
Jim Meyering <[EMAIL PROTECTED]> writes:
> I admit that .eh seems a little odd, and would
> require everyone to teach their editor about the new suffix.
True; that's a pain.
> How about the "..h" suffix, e.g., stdlib..h? Do we care enough
> about 8.3 limitations to worry about that?
I don't th
[EMAIL PROTECTED] (Karl Berry) wrote:
> I see it's not specifically mentioned in standards.info.
> Maybe someone will add it, there.
>
> "someone" = mail bug-standards, preferably with a patch, and I will
> raise it with rms. That is, if we really want it.
Thanks.
> At least those pa
I see it's not specifically mentioned in standards.info.
Maybe someone will add it, there.
"someone" = mail bug-standards, preferably with a patch, and I will
raise it with rms. That is, if we really want it.
At least those particular cases don't bother me as much as say,
foo_bar
Eric Blake wrote:
> But editors (at least good ones, including vi, emacs, and kate) can be
> taught about new suffixes, and once taught, will treat .eh like .h.
Solving a problem for yourself is one thing; solving it for all the people
who look at the gnulib sources from outside is another.
I did
I installed the patch.
/Simon
Simon Josefsson <[EMAIL PROTECTED]> writes:
> How about this patch? I'm not sure where a good place to add this is,
> or whether it should use a @subsection or something. But the important
> thing is to say something similar somewhere.
>
> /Simon
>
> --- stdint.te
