> Date: Sun, 9 Mar 2008 19:45:45 -0500
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: [EMAIL PROTECTED], bug-gnulib@gnu.org, [EMAIL PROTECTED]
>
> nospam.gnu.org>
>
> Thanks. This seems pretty reasonable (and easy to implement) to me.
> Eli, why do you object to it so
Karl Berry wrote:
> I personally don't feel so strongly about such anti-spamification stuff,
Me neither. Hiding an email address seems doomed to failure. You
can't hide something that other people need to know about to use.
> especially for mailing lists, but I don't see any particular harm in
Karl Berry wrote:
> I don't want to make it an option, that would be the most pain of all.
> Either in or out.
Well, I'm asking for it as an option. If you put it in for everyone, the
fact that makeinfo does not generate "mailto:..."; hrefs will appear as a
deficiency of makeinfo to many people.
Eric Blake wrote:
> | - freadahead keeps its signature but returns the total buffered bytes
> count.
This implements it.
2008-03-09 Bruno Haible <[EMAIL PROTECTED]>
* lib/freadahead.h (freadahead): Document more precisely.
* lib/freadahead.c (freadahead): When an ungetc is i
Thanks. This seems pretty reasonable (and easy to implement) to me.
Eli, why do you object to it so strongly?
I personally don't feel so strongly about such anti-spamification stuff,
especially for mailing lists, but I don't see any particular harm in
Eric Blake wrote:
> | - freadptr is changed to also return the size of the buffer.
> | extern const char * freadptr (FILE *stream, size_t *sizep);
> | When the return value is non-NULL, *sizep is set to the size of the
> | buffer whose address is the return value.
>
> Sounds fine t
Simon Josefsson wrote on Thursday:
> > Maybe this should documented somewhere?
> >
> > Sure (as far as I'm concerned), please add it to the manual somewhere.
>
> The best place I could find was doc/README, is this ok?
>
> /Simon
>
> diff --git a/doc/README b/doc/README
> index 551f539..34f21
> From: Bruno Haible <[EMAIL PROTECTED]>
> Date: Sun, 9 Mar 2008 19:27:18 +0100
> Cc: bug-gnulib@gnu.org, [EMAIL PROTECTED], Karl Berry <[EMAIL PROTECTED]>
>
> The user cannot reply directly when he is reading a manual in
> PDF, Postscript, DVI, or plain text format; he has to copy&paste or retype
> From: Bruno Haible <[EMAIL PROTECTED]>
> Date: Sun, 9 Mar 2008 16:30:38 +0100
> Cc: [EMAIL PROTECTED]
>
> > [EMAIL PROTECTED]}.
> > [EMAIL PROTECTED]@code{}}.
> >
> > Personally, I don't see a reason not to use @email here. That's why it
> > exists.
>
> How can @email be combined with
Eric Blake wrote:
> > On HP-UX 11:
> > When reading from the pipe:
> > c = '#'
> > c = 'i'
> > ungetc result = '@'
> > c =
> > c =
>
> Bug - C99 requires that ALL streams have at least one byte of ungetc space,
> with no limitation on what can go in that buffer. You only invoke
> unspecified
Eric Blake wrote:
> I'm starting to waffle on what POSIX
> requires. Maybe it's worth asking the Austin Group after all?
Yes, thanks for asking the Austin Group.
> Swapped comments.
> ...
> Cygwin listed twice. But be aware that there was a change in cygwin behavior
> from 1.5.25-10 to 1.5.25
Eric Blake wrote:
> But my questions about fflush on seekable input streams after ungetc still
> remain.
There are also two cases to consider:
1) ungetc of the last byte read,
2) ungetc of a different byte value.
Three results are possible:
a. set the file descriptor's position to the strea
Ralf Wildenhues wrote:
> > How can @email be combined with anti-spam devices? The more an email address
> > is mentioned on the web, the more it attracts spam, and the more spam passes
> > the spam filters.
>
> FWIW, I kinda doubt this makes any difference for gnu.org mailing list
> addresses (and
Hello Bruno, Karl,
* Bruno Haible wrote on Sun, Mar 09, 2008 at 04:30:38PM CET:
> Karl Berry wrote to bug-gnulib:
> > [EMAIL PROTECTED]}.
> > [EMAIL PROTECTED]@code{}}.
> >
> > Personally, I don't see a reason not to use @email here. That's why it
> > exists.
>
> How can @email be combi
Karl Berry wrote to bug-gnulib:
> [EMAIL PROTECTED]}.
> [EMAIL PROTECTED]@code{}}.
>
> Personally, I don't see a reason not to use @email here. That's why it
> exists.
How can @email be combined with anti-spam devices? The more an email address
is mentioned on the web, the more it attrac
15 matches
Mail list logo