Brian Inglis wrote:
> On 2024-12-06 19:16, Keith Thompson via Cygwin wrote:
> > The use of "1$", "2$" et al in printf format specifiers is a
> > POSIX-specific feature.
> >
> > On Cygwin (newlib) this is handled correctly in most cases, but one
> > example I tried misbehaves.
> > The output is corr
On 2024-12-06 19:16, Keith Thompson via Cygwin wrote:
The use of "1$", "2$" et al in printf format specifiers is a
POSIX-specific feature.
On Cygwin (newlib) this is handled correctly in most cases, but one
example I tried misbehaves.
The output is correct on other implementations, including gli
On 7 December 2024 02:48:50 UTC, Keith Thompson
wrote:
>It's not really a tmux issue. You can demonstrate it just by invoking
>a shell.
>
>For example, if you "cd /tmp" and then invoke a new shell with
>"bash -l", the code in /etc/profile will cd to your home directory.
>(This doesn't happen on U
It's not really a tmux issue. You can demonstrate it just by invoking
a shell.
For example, if you "cd /tmp" and then invoke a new shell with
"bash -l", the code in /etc/profile will cd to your home directory.
(This doesn't happen on Ubuntu, for example, which has a
different /etc/profile.)
But i
The use of "1$", "2$" et al in printf format specifiers is a
POSIX-specific feature.
On Cygwin (newlib) this is handled correctly in most cases, but one
example I tried misbehaves.
The output is correct on other implementations, including glibc and
musl on Ubuntu.
This C program:
#include
int m
Hello,
was it considered to add a flag to cygpath to output a path in unc format?
For example, the folder
C:\test.
cannot be accessed from many Windows applications (powershell and cmd
included) because of the trailing dot, while cygwin has no issue
creating, accessing and deleting such fil
6 matches
Mail list logo
