Ralph,
> > 'so /usr/lib/tmac/tmac.m
> > This probably wouldn’t be the preferred way of doing things anymore
>
> I see no reason to demote it. :-)
I was getting more at using “.mso”, but for the example above, the file
well might not be on the macro path. I think it’s better to use “'”
than a s
Hi Ingo,
> even though close(2) is the most typical example of a system call
> where checking the return value / checking for failure is almost never
> useful, and simply ignoring both the return value and errno is what
> you should do in most cases.
There's ENOSPC indicating a previous write(2)
Hello Colin, Ingo and Ralph,
thank you for your elaborate and clarifying answers.
Sorry again for the off-topic noise.
Regards,
Carsten
Hi Colin,
> Writing "== -1" implies a reading that any other value would indicate
> success;
Or it implies it's being coded to the spec.
> writing "!= 0" implies a reading that any other value would indicate
> an error; writing "< 0" implies a reading that it depends on the sign
> of the hypothe
Hi Carsten,
> Many system calls (e.g. close(2),
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/close.html)
> return 0 on success and -1 on error and set errno.
Well done for referring to POSIX. Your Unix system might make their man
pages available alongside its own, e.g. I've close(
Hi,
Carsten Kunze wrote on Sun, Aug 19, 2018 at 02:32:49PM +0200:
> Many system calls (e.g. close(2),
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/close.html)
> return 0 on success and -1 on error and set errno.
>
> My understanding is that errno is only reliably set when the syst
On Sun, Aug 19, 2018 at 02:32:49PM +0200, Carsten Kunze wrote:
> Many system calls (e.g. close(2),
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/close.html)
> return 0 on success and -1 on error and set errno.
>
> My understanding is that errno is only reliably set when the system
>
On Sun, Aug 19, 2018 at 02:15:07PM +0200, Heinz-Jürgen Oertel wrote:
> using for the first time now OpenSuse Thumbleweed. Installed all tools (I
> hope)
> ./configure runs without problems. Had to do:
> sudo ln -sf /usr/bin/aclocal /usr/bin/aclocal-1.13
As well as what other people have said, ran
> using for the first time now OpenSuse Thumbleweed. Installed all tools (I
> hope)
> ./configure runs without problems. Had to do:
> sudo ln -sf /usr/bin/aclocal /usr/bin/aclocal-1.13
If you install from git, please read `INSTALL.REPO'. The first step
is to call
./bootstrap
which should
Hello,
sorry for misusing the list for something completely off-topic (while it still
refers to the documentation of the UNIX system), but since there are many UNIX
experts on the list maybe someone has a definite answer.
Many system calls (e.g. close(2),
http://pubs.opengroup.org/onlinepubs/9
Hi Heinz-Jürgen,
> sh: build-aux/git-version-gen: Datei oder Verzeichnis nicht gefunden
Try running that directly and investigating what it's doing?
http://git.savannah.gnu.org/cgit/groff.git/tree/configure.ac#n21
suggests it's run with
build-aux/git-version-gen --prefix "" .tarball-version
hi,
using for the first time now OpenSuse Thumbleweed. Installed all tools (I
hope)
./configure runs without problems. Had to do:
sudo ln -sf /usr/bin/aclocal /usr/bin/aclocal-1.13
but anyway, calling make
groff-git> make
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /home/oe/src/groff-git/buil
Hi Jeff,
> A traditional idiom for doing this was calling ‘so’ with the no-break
> control character, e.g.,
>
> 'so /usr/lib/tmac/tmac.m
>
> This probably wouldn’t be the preferred way of doing things anymore
I see no reason to demote it. :-)
soelim(1) from heirloom-doctools says
Note that
Hi Tadziu,
> Here's a patch to fix the problem, but I'm not entirely happy with it
> since it feels like it is usurping ms's chain of command. On the
> other hand, I'm not sure a clean solution exists short of rewriting a
> large part of ms's internals.
Agreed. /usr/heirloom/lib/doctools/tmac/s
14 matches
Mail list logo
