Hi,
On Mon, Jun 27, 2005 at 05:38:06PM +0100, Giles Anderson wrote:
> On 27/06/05, Stepan Kasal <[EMAIL PROTECTED]> wrote:
>
> > The simple *.test files used by Automake test suite seems to be much
> > simpler.
>
> I hadn't come across this Automake facility. Could you provide some
> details Ste
Hello,
On Mon, Jun 27, 2005 at 02:08:07PM +0200, Stepan Kasal wrote:
> On Thu, Jun 23, 2005 at 10:20:33PM +0200, Patrice Dumas wrote:
> > > gnulib is an existing centralised repository, with implementations
> > > under various licenses, but mostly they are GPL or LGPL.
> >
> > Maybe there could b
+In case you want to use already existing files, you can have a look at
[EMAIL PROTECTED]://www.gnu.org/software/gnulib/, Gnulib}, a centralized
The English seems fine to me, but since Gnulib has a Texinfo manual, it
seems like it might make sense to use a multi-argument xref instead of
@u
> Hello,
gnulib is an existing centralised repository, with implementations
under various licenses, but mostly they are GPL or LGPL.
>>>
>>> Maybe there could be a note about that in the autoconf manual ?
>>
>> standards.texi, which is distributed with Autoconf, mentiones it.
>>
>> But
Hello!
Probably you want: --devicers=AxB
Yes AxB is Ok for this too. But that means that I must define any possible
resolution in configure.ac, right?
No.
You can just parse the value using a script. Then you put your XRES
and YRES in environment vars. Then you use AC_DEFINE.
And the
Hello,
On Tue, Jun 28, 2005 at 09:12:32AM -0400, Karl Berry wrote:
> The English seems fine to me, but since Gnulib has a Texinfo manual, it
> seems like it might make sense to use a multi-argument xref instead of
> @uref (with rewording), as in:
> @xref{Top,,,gnulib,Gnulib},
OTOH, is seems mo
