Andrey Repin wrote:
Greetings, Csaba Raduly!
...
The API can handle / as the path separator, but cmd.exe can't.
You're seriously wrong...
How? (Which part is wrong?)
The Start menu's Run... command accepts forward slashes, and cmd.exe
parses unquoted forward slashes as parameter
Larry Hall (Cygwin) wrote:
On 10/5/2010 10:12 AM, Daniel Barclay wrote:
Larry Hall (Cygwin) wrote:
On 10/4/2010 12:19 PM, Daniel Barclay wrote:
...
Can anyone confirm (or anti-confirm) this behavior?:
...
When bash is started using the Cygwin shortcut (which runs cygwin.bat,
which executes
Larry Hall (Cygwin) wrote:
On 10/4/2010 12:19 PM, Daniel Barclay wrote:
I wrote:
The behavior of bash --login -i seems to vary depending on whether
it is a root invocation or a nested invocation of bash. This is
inconsistent with the description man bash, and seems to be a bug.
Can anyone
Afflictedd2 wrote:
Ok. nm...
it has to be this way:
cygpath -u C:\Users\Viper\Tmp
Using single quotes would be more general. Consider the difference if
the pathname includes a substring like \r. (Backslash is inert in
(bash/sh/etc.) single-quoted strings, but sometimes escapes the
I wrote:
The behavior of bash --login -i seems to vary depending on whether
it is a root invocation or a nested invocation of bash. This is
inconsistent with the description man bash, and seems to be a bug.
Can anyone confirm (or anti-confirm) this behavior?:
Details:
When bash is started
The behavior of bash --login -i seems to vary depending on whether
it is a root invocation or a nested invocation of bash. This is
inconsistent with the description man bash, and seems to be a bug.
Details:
When bash is started using the Cygwin shortcut (which runs cygwin.bat,
which executes
Eric Blake wrote:
On 09/22/2010 03:02 PM, Daniel Barclay wrote:
...
Again, why does Cygwin's (virtual) file system _not_ include those
devices (when listing /dev)? (Why doesn't it do it more like Linux's
/proc, etc., which gives a consistent view and which tells you what's
available without
Buchbinder, Barry (NIH/NIAID) [E] wrote:
...
To go there directly:
http://www.cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-posixdevices
Regarding where that page says:
These devices cannot be seen with the command ls /dev/ ...
I've wondered about that--why aren't those
Larry Hall (Cygwin) wrote:
On 9/22/2010 1:29 PM, Daniel Barclay wrote:
Buchbinder, Barry (NIH/NIAID) [E] wrote:
...
To go there directly:
http://www.cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-posixdevices
Regarding where that page says:
These devices cannot be seen
Does anyone recall a mention of what in CygWin (or possibly Emacs) creates
files with a simple name of NUL?
Thanks,
Daniel
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
Corinna Vinschen wrote:
...
Note: Don't use DOS device names in Cygwin!
Wrong:
$ echo foo NUL
$ echo foo nul
$ echo foo nul:
Right:
$ echo foo /dev/null
Yes, I know. I'm not using NUL (or nul or nul:, etc.), but something
is.
(Now I'm thinking that it's an
Larry Hall (Cygwin) wrote:
On 9/8/2010 1:24 PM, Andy Koppe wrote:
On 8 September 2010 17:35, Larry Hall (Cygwin) wrote:
Isn't the whole reason for Cygwin actually to enable doing Unixy things
in Windows (that is, providing Windows/Unix interoperablity?
No, that's not a key goal. From the
Christopher Faylor wrote:
On Thu, Sep 02, 2010 at 12:13:12PM -0600, Eric Blake wrote:
On 09/02/2010 11:45 AM, Daniel Barclay wrote:
I don't quite understand this behavior:
$ ls C:\\tools\\emacs-23.2\\bin\\runemacs.exe
C:\tools\emacs-23.2\bin\runemacs.exe
$ C:\\tools\\emacs-23.2\\bin
I don't quite understand this behavior:
$ ls C:\\tools\\emacs-23.2\\bin\\runemacs.exe
C:\tools\emacs-23.2\bin\runemacs.exe
$ C:\\tools\\emacs-23.2\\bin\\runemacs.exe
bash: C:\tools\emacs-23.2\bin\runemacs.exe: command not found
In particular, why is it that bash does not understand that Windows
Where is the documentation of the igncr (ignore-CR) option for Cygwin 1.7's
bash?
(There does not appear to be any reference to it in
- the current Cygwin User's Guide (http://cygwin.com/cygwin-ug-net/),
- the current CygWin FAQ (http://cygwin.com/faq.html), or
- in bash man page from CygWin.
Eric Blake wrote:
On 09/01/2010 12:12 PM, Daniel Barclay wrote:
Where is the documentation of the igncr (ignore-CR) option for Cygwin
1.7's
bash?
(There does not appear to be any reference to it in
- the current Cygwin User's Guide (http://cygwin.com/cygwin-ug-net/),
- the current CygWin FAQ
Yep - that email (most recently here[1]), along with
/usr/share/doc/Cygwin/bash.README, are the definitive sources of all
documentation to cygwin-specific patches to bash (of which igncr is one).
[1] http://cygwin.com/ml/cygwin-announce/2010-08/msg00015.html
That read-me file says:
4c. To
Charles Wilson wrote:
Daniel Barclay wrote:
However, I suggest rather than blindly re-installing/un-installing
packages at random
Hey, I wasn't randomly installing and uninstalling packages. My setup was
seemingly working fine until I installed some unrelated package (Ruby) and then
rxvt
Dave Korn wrote:
Daniel Barclay wrote on 12 May 2008 17:39:
What causes rxvt to switch to displaying characters with lots of space in
between them?
Did you overlook Chuck Wilson's reply in our thread last week?
No, I didn't. That post didn't address why things were changing seemingly
What causes rxvt to switch to displaying characters with lots of space in
between
them?
I heard that there's some interaction between X11-mode rxvt setup and
plain-window
rxvt setup. I don't think I've installed any X11 libraries, servers, or even
fonts since rxvt was working right, but now
René Berber wrote:
Daniel Barclay wrote:
What causes rxvt to switch to displaying characters with lots of space
in between them?
The font it's using.
I heard that there's some interaction between X11-mode rxvt setup and
plain-window
rxvt setup. I don't think I've installed any X11
René Berber wrote:
Daniel Barclay wrote:
What causes rxvt to switch to displaying characters with lots of space
in between them?
The font it's using.
But why exactly would it display characters with lots of space between them?
Surely the font isn't designed that way.
What is actually
Charles Wilson wrote:
However, with regards to rxvt in native mode, the widely spaced
characters you are seeing happens when rxvt can't find, or doesn't
understand, the font you specified.
Well, I didn't specify anything. I haven't touched any of
/etc/X11/app-defaults/Rxvt, ~/.Xdefaults
I wrote:
I am using whatever the CygWin packages and installer installed on my
machine, which evidently changes in non-intuitive ways when I re-run it
to modify the combinations of packages I have installed even though I'm
not (consciously) touching any X11 or font-related packages).
Just
cygwin@cygwin.com:
Sorry, your message has been denied due to keywords found in your
subject. This is probably due to an off-topic post.
...
--- Enclosed are the original headers of the message.
... Subject: widely-spaced characters in rxvt (non-X11 mode)
What the heck is off-topic about
Dave Korn wrote:
Daniel Barclay wrote on 09 May 2008 17:22:
cygwin@cygwin.com:
Sorry, your message has been denied due to keywords found in your
subject. This is probably due to an off-topic post. ...
--- Enclosed are the original headers of the message.
... Subject: widely-spaced
Elfyn McBratney wrote:
I don't think harvesters have frame-enabled browser's :-) :-) :-)
Why not? It's just as easy to handle frame SRC='someurl'
as it is to handle a href='someurl'.
Daniel
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
Igor Pechtchanski wrote:
On Thu, 3 Jul 2003, Daniel Barclay wrote:
Can bash inherit the working directory setting from the process that
invoked bash instead of always setting its initial working directory
(to the user's home directory)? ...
Normally, you should be able to just not pass
Can bash inherit the working directory setting from the process that
invoked bash instead of always setting its initial working directory
(to the user's home directory)?
On Unix, Emacs' shell command gets me a shell whose working directory
is set based on what I was editing.
However, when I use
Max Bowsher wrote:
Charles D. Russell wrote:
...
1) setup.exe is really designed to work best for direct installation
from the web, so do that first on some computer with an internet
connection. 2) when you install from the web, copies of all the
downloaded files - including setup.exe - are
30 matches
Mail list logo
