Mintty is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Among its features are Unicode
support and a graphical options dialog. Its terminal emulation is
largely compatible with xterm, but it does not require an X server.
Mintty is based on code from PuTT
n one particular charset, namely that of your editor.
In that case you need to use wchar_t strings instead, for example:
#include
#include
int main(void) {
setlocale(LC_CTYPE, "");
wprintf(L"Øl\n");
}
You also need to ensure that gcc's character set matches th
bytes with
> the 8th-bit set is specifically undefined in the C locale (whether that be
> C.ASCII or C.UTF-8).
I very much disagree with that. C.ASCII and C.UTF-8 are different
locales from plain "C", and the whole point of the explicitly stated
charset is to define the meaning
2009/12/29 Charles Wilson:
> TODO (call for patches):
>
> * Update lpr.cc and mkshortcut.c to use cygwin-1.7 cygwin_conv_path
> instead of deprecated cygwin_conv_to_win32_path.
I'll have a go at mkshortcut.
Andy
--
Problem reports:
ent.
However, since that is a valid assumption on Linux and others, Cygwin
might indeed be better off following their example. There's a
discussion about that on cygwin-developers.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq
to a
singlebyte charset, e.g. by setting 'LANG=en_US.ISO-8859-1'.
Otherwise, the escape prefix is the way to go.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
2010/1/1 Thomas Dickey:
> On Fri, 1 Jan 2010, Andy Koppe wrote:
>
>>> XTerm*vt100.metaSendsEscape: true
>>
>> Actually that's not a hack, but the correct solution. I think this
>> needs to be part of the default config in /etc/X11/app-defaults/XTerm.
&g
symlinks you want that way.
That won't work. The option causes symlinks to be represented by
Windows shortcuts, which do work in Explorer, but not in cmd.exe where
they appear as .lnk files instead. (Lame, eh?)
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ:
server startup:
$ xwin -xkblayout fo
Or the setxkbmap command for a running server:
$ setxkbmap fo
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
ntest advantage over Cygwin-only symlinks
implemented as files with the SYSTEM DOS attribute set."
You could create a Windows symbolic link using the Windows 'mklink'
tool though, and it should work both in cmd.exe and in Cygwin.
Andy
--
Problem reports: http://cygwin.com/pr
de characters (that is, wchar_t
> rather than char).
Good stuff. Thanks!
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
ot;? Simply dropping
the "\\?\" wouldn't work for network paths. I haven't managed to find
a solution on MSDN.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
2010/1/3 Andy Koppe:
> I'm having a spot of trouble changing mkshortcut to use the
> wchar_t-enabled cygwin_create_path instead of the deprecated
> cygwin_conv_to_full_win32_path & co. When converting to a Windows path
> using CCP_POSIX_TO_WIN_W, the result is a path starti
r set of the "C" locale in Cygwin
1.7 is UTF-8 and that the \300 on its own is an invalid UTF-8 byte. To
get well-defined behaviour, you need to invoke setlocale(LC_CTYPE,
...) with the approriate locale.
See the thread at http://cygwin.com/ml/cygwin/2009-12/msg00980.html
for more on this.
at string is undefined behaviour.
Anything can happen. And what likely happened is that the compiler
replaced the third sprintf call with strcpy (which is specified on
strings rather than character strings).
The real discussion to be had here is whether "C" should continue to
mean UTF-8
(LC_CTYPE, "POSIX") also did not work. It happens to
> return "C".
"POSIX" is just a synonym for "C".
> The above behaviour seems to disagree with the man page.
Which man page?
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
wo choices:
- Change your locale to one with a singlebyte character set, e.g.
en_US.ISO-8859-1.
- Use a different terminal: urxvt or xterm if you want to run X, or
mintty if you don't.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
with
the following:
- LANG=en_US.UTF-8
- LANG=en_US.ISO-8859-1
- LANG=C
- LANG=(nothing)
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#un
o work around bugs in those. As Greg
points out, Google results look like 'ibmfilter.sys' is the very
definition of crapware. Try uninstalling it if possible.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
2010/1/6 Fergus:
>>> Something wrong somewhere?
>
>> No.
>
> O .. K .. thanks for that ...
> So how does the same executable differing only in name trigger two entirely
> different installations?
It checks its own name using argv[0] and acts accordingly.
Andy
which uses overlapped IO to create
more reliable interruptible pipes and fifos.
Bottom line: it's a sqlcmd bug. Report it to Microsoft.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
his reason, mintty
replaces U+2010 with a plain ol' ASCII hyphen/minus character (0x2D).
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
se
>
> My mount in /etc/fstab is text, I tried binary, that seems to not help.
>
> any ideas?
Another thing to try might be the locale setting. Windows uses
codepage numbers where Unix uses charset names, so perhaps sqlcmd is
stumbling over those. In particular, try unsetting LANG.
An
2010/1/7 David Arnstein:
> I have finished upgrading from 1.5.x to 1.7.x and I don't intend to
> go back. Now I would like to delete the entries some entries from my
> Windows registry. What are the keys that were used in 1.5.x, but are
> no longer used in 1.7.x?
HKLM\Software\Cygnus Solutions
-
2010/1/7 raytheman:
>
> My cygwin supports all the old SSH protocol, I need to disable them in order
> to meeting the security requirement, please help.
>
> - 1.33
> - 1.5
> - 1.99
> - 2.0
RTFM: man ssh
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin
pened mintty.
And the difference appears to be in the PATH: in the new session it
has an additional /usr/lib/lapack at the end.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
like everything else.
Thanks for the fix.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
set it? I have HOME, HOMEPATH and
> HOMEDRIVE set in my windows environement and I cant' find where they get
> defined. Does anybody know?
Control Panel -> System -> Advanced System Settings -> Environment Variables
Or something like that.
Andy
--
Problem reports:
emacsclient, perhaps it's getting upset about Cygwin's LANG setting.
Try unsetting that.
> If you want everything to work as expected,
> either don't run NTEmacs from Cygwin programs, or use the Cygwin build
> of Emacs.
Yep. And don't expect much help with NTEmacs he
2010/1/12 sbremal
> I am afraid the winsymlinks option is an installation time setting, is it? :
No, but it only affects newly created symlinks.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.
at for some reason, but U+2212 is present in all the fonts
I've tried, except of course in non-Unicode fonts. For example,
Consolas, Courier New, and DejaVu Sans Mono all have it.
Bottom line: use a Unicode font for UTF-8.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ:
t; Files with umlauts are recognized as UTF-8 by the file command.
Please note that 'nano' also doesn't support UTF-8 yet. While entering
characters looks like it works initially, nano will internally think
that you've entered two characters when you enter an umlaut. He
2010/1/13 Cyrille Lefevre:
> give a try to puttycyg which support both ssh, telnet as well cygwin.
The OP is insisting on running the Windows versions of telnet and ftp,
and those won't work in puttycyg either. Same in any other terminal
based on 'pseudo terminal' (pty) devices.
console, it hurt. I fixed that in CVS.
Thanks! And apologies for not testing with CYGWIN=tty at the time.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://c
pologies for sounding irate, it is just that like everyone I was
> in a middle of "something important" and I messed up something which I
> rely on for my bread and butter.
A great time for a major update on your production machine then.
Andy
--
Problem reports: http
Yes. X applications do not depend on XWin (i.e. the xorg-server
package) because they can be used with any X server, including one
running on a different machine.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
able is "C.UTF-8".
I'd still recommend to set it to en_US.UTF-8 though, because that's
least likely to cause issues with any programs that have their own
ideas about locales. (Others of course will want to replace 'en_US'
with their language and country.)
Andy
--
remember when the man output was last formatted correctly. Any
> advise on where to check next?
>
> $ uname -a
> CYGWIN_NT-5.1 phoenix 1.7.0(0.212/5/3) 2009-08-20 10:56 i686 Cygwin
Looks like you could do with an update.
Andy
--
Problem reports: http://cygwin.com/problems.html
rinting a UTF-8 file there?
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
this issue. All a terminal does when
Ctrl+C is pressed is write a ^C character to its pseudo terminal
device (pty), and it's the pty driver that handles it (depending on
the pty's settings): Cygwin processes are sent a SIGINT signal, but
Windows processes such as Java are terminate
default config is broken, looking for gcc in
/usr/local/bin. Hence you need to either edit the global config at
/etc/colorgcc/colorgccrc or copy it to ~/.colorgccrc and change the
paths to /usr/bin. You can also change the colours for various
messages there.)
Andy
--
Problem reports: http://cygw
te
> Wed Jan 20 20:20:44 PST 2010
>
> r...@mycomputer ~
> $ ant
> -bash: ant: command not found
>
> my .bash_profile path looks like:
> PATH=$PATH:/c/Apps/apache-ant-1.8.ORC1/bin
> export PATH
You've got an O ('oh') instead of a 0 ('ze
in the same Cygwin process, but actually a new
Windows process has to be created since Windows doesn't allow a
process to change executable.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.c
ply aliasing CP932 to SJIS is wrong, because they are
quite different character sets. Supporting CP932 as a charset in its
own right might be worth considering though, especially as that's the
standard charset on Japanese Cygwin 1.5.
Andy
--
Problem reports: http://cygwin.com/problems.html
On 23 January 2010 12:02, Christian Franke:
>>> Current setup.exe does not work properly if retry is used.
>>
>> Known regression. Somebody has to fix this.
>
> This is apparently fixed in setup.exe 2.677
Yep, cgf braved the innards of setup.exe and hunted down
Corinna Vinschen:
> I applied a patch which handles the characters 0x5c and 0cfe differently
> if the charset is set to "SJIS"
Something's going seriously wrong with this, and I'd suspect it's to
do with turning backslashes into yen symbols.
C:\Users\Andy>set L
eone really needs standard SJIS
for converting documents or something, they can use iconv.
Therefore I've changed my mind on whether to keep SJIS and CP932
separate: I think we should stick with the .SJIS charset as it
is in 1.7.1, except that nl_langinfo(CODESET) for it should return
rce files. This might be a case of the source being
encoded in ISO-8859-1 while the compiler tries to interpret it as
UTF-8. Try invoking the build with LANG=C.ISO-8859-1. I'm assuming
you're using Cygwin 1.7?
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Mintty is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Among its features are Unicode
support and a graphical options dialog. Its terminal emulation is
largely compatible with xterm, but it does not require an X server.
Mintty is based on code from PuTT
ready. This means that
with LANG=ja_JP, xterm uses eucJP, while filenames and programs
currently use the system's ANSI codepage, i.e. CP932 on Japanese
systems. Result: mojibake. It does work correctly with
LANG=ja_JP.SJIS.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ:
2010/1/27 Kazuhiro Fujieda:
> Andy said `Seems SJIS really isn't suited for Unix command line
> use.' I said there is no problem, no difference with EUC-JP, and
> no need to change the default.
That comment primarily referred to standard SJIS, with its mappings of
the ASCII
ocale, which rxvt does not support.
> Should I be re-setting LANG or otherwise adjusting my environment?
Yep, either use a different terminal or set LANG to something that
rxvt supports, e.g. en_GB.ISO-8859-1.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Kazuhiro Fujieda:
> Andy Koppe:
>> Another example is X11, which has its own locale system independent
>> from Cygwin's. There, "ja_JP" implies eucJP already. This means that
>> with LANG=ja_JP, xterm uses eucJP, while filenames and programs
>> currently
ges afterwards. Most notably the mount point
storage has been moved out of the registry into files. User mount
points are NOT copied into the new user-specific /etc/fstab.d/$USER
file. Rather, every user has to call the /bin/copy-user-registry-fstab
shell script once after the update."
And
opposite order that the corresponding constructors
were invoked and the atexit functions were registered. Since atexit()
may be called from static constructors, there should theoretically be
a single stack for destructors and atexit functions. But if that's not
practical, invoking the atexit stu
you're getting messages from
'bzr'? Please describe the actual steps that produced those warnings.
Also, is bzr connecting to a remote machine? I don't get those
warnings if I just do 'bzr init' locally.
> Setting LC_ALL to C.ISO-8859-1 removed the warning.
Right
Steve Denson:
> Cygwin setup.exe can't find setup.ini in any mirror.
Are using the latest setup.exe from the Cygwin homepage? Any firewalls
or proxies that might be in the way?
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin
of setup-legacy.ini?
What's the mirror you're trying to use? Won't Rockbox work on the
latest Cygwin 1.5 from one of the official mirrors (which should all
have setup-legacy.ini)?
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/f
Mohammad Qayum:
> 'configure' didn't succeed. What could be the
> potential cause of configure failure
Anything. Look at configure's output, it will usually tell you.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cyg
> Also, <http://cygwin.com/mirrors.html> helps you answer this for yourself
> anytime.
An oddity in that list: Japan appears as a continent with Asia as a country.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
D
e
frequently, but I guess hacking away at the keyboard while output is
going on just isn't something one would normally do.
Anyway, as long as there isn't a fix, is there anything I could do in
mintty to work around this? Would it help to move the writing of
keyboard input to the pty device into its own thread?
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
appear on the bach command line as c ( š and ž don't appear at all).
>
> Any idea what is wrong?
A mismatch of Cygwin's charset and mintty's charset, probably. What
versions of Cygwin and mintty are you using? What are the values of
LC_ALL, LC_CTYPE and LANG? Is anything s
t; case. But in the latter case, if there're whitespaces in the
> myscript's pathname, the batch will fail to run.
Hmm, perhaps the argument mangling at program startup is using the
ANSI codepage (i.e. GBK in this case) when it should be using UTF-8?
Andy
--
Problem reports: h
usr/bin/bash:
> "F:/zhaohs/Desktop/鏂版煡鏂囩尞/RestoreName4Elsevier.sh": No such
> file or directory
That's easily explained: batch files are assumed (by Windows) to be
encoded in the OEM codepage, which on your system will be the same as
the ANSI codepage, i.e. GBK (aka CP936).
string as GBK.
>> Seems sys_mbstowcs and WriteFileW are needed there.
>
> There's no such thing as a WriteFileW function.
D'oh, of course. I confused it with WriteConsole, which does have a
Unicode version.
Andy
--
Problem reports: http://cygwin.com/problems.htm
muttrc send_charset is unset, so allegedly defaults to
> charset, but that doesn't seem to be the case here for some reason.
I don't use mutt, so I can't really help here, but a mintty user
reported that he had to rebuild mutt against ncursesw (which is now
part of the
by that, because the standards and formats setting
shouldn't have any effect on LANG, at least as far as mintty and
Cygwin are concerned. Any idea how it might have got set to "SL"?
In any case, the easy way to set locale and charset in mintty is via
the Text options. This will also se
means something else set it to
"SL". Is there any other Unixish software on your machine that might
be doing that? MS's "Services for Unix" perhaps? Emacs?
I understand you're no longer interested in this since you've solved
your problem, but it would nevertheless be
(for instance Unicode and the UTF-8 encoding). The
corresponding wide-character ncursesw libraries are source-compatible
with the normal applications. That is, applications must be compiled
and linked against the ncursesw library."
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ:
you put the '-cd ' before the -e it won't work as
you expect because the default /etc/profile contains a 'cd $HOME'
command. Instead of using -cd, though, you could set HOME in your
batch script:
set HOME=C:\blu\newest
Or you could change your home directory in /etc/passw
ut
backslash quoting, because "\\?\C:\tmp" loses a vital backslash during
quote removal.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
ut
>> backslash quoting, because "\\?\C:\tmp" loses a vital backslash during
>> quote removal.
>
> Thanks for the report. Should be fixed in CVS.
Confirmed.
Thanks,
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.
sein, z.B. mit einem separaten
Paket?
Ein Fehler mit dem Kontextmenü: eine Datei names "New Text
Document.txt" wird als "New" geöffnet.
Schönen Gruß,
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documen
ns
> -> xterm is killed
When a console is closed, Windows kills all processes attached to it.
> Also, mintty can be protected from being killed by spawning it with
> (mintty&)
> while xterm, spawned this way from a cygwin console, still gets killed.
Yep, doing that doesn&#
Mintty is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Among its features are Unicode
support and a graphical options dialog. Its terminal emulation is
largely compatible with xterm, but it does not require an X server.
Mintty is based on code from PuTT
In cygwin 1.7.1, when I use "bash promt here" at a directory which's
name contains unicode charactor, there's wrong. But it's right under
cygwin 1.5.x.
Below is my example.
C:\Users\andy>C:\cygwin\bin\bash -c "/bin/xhere /bin/bash.exe 'd:\我的工作'"
cy
; wide-character) functions
> [...]
I'd go with that, because that way you can support not only UTF-8, but
all the charsets supported by the OS.
> (provided you want characters as Unicode words,
> not UTF-8 sequences in your program).
In that case, one can just ignore the
vt.color4:#007fff
Blue (i.e. color 4) on black background is just a bad idea, full stop.
Brightening it up by default would impair its usability as a
background colour. (Try 'mc' with your setting.)
And mintty's default for colour 12 is #4040ff, which is much the
; (or
'xterm-256color') as part of the conditional code.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Thomas Wolff:
> Andy Koppe:
>> Mintty has default handling for SIGHUP, i.e. it exits.
>
> Actually (another topic but related) mintty has a great feature here: it
> passed the SIGHUP to its client application and if that application catches
> and handles the SIGHUP, mintt
Xterm ignores the
DECCOLM sequence by default and provides a separate control sequence
for allowing DECCOLM. I'll implement that for mintty 0.6.
Thanks for the report.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
data. Yet
unlike with xterm, a misbehaving application won't stop the user from
closing the terminal, because guess who'd be blamed for that.
> Should I propose a patch?
Not much point, because the difficult bit here is design not implementation.
Andy
--
Problem reports: http://
tical terms it means that xterm would need to call
FreeConsole() to detach from the console it's started from. If you're
interested in the details, there's always MSDN.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Andy Koppe:
> Thomas Wolff wrote:
>> In general, a GUI application started in the background, like a terminal,
>> should detach itself from its parent process so that it survives if the
>> parent is terminated.
>
> Says who? You can always invoke it with setsid or some s
e implementation of DECSCUSR could be done using
SetConsoleCursorInfo).
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
current highest one. This means, however, that if opening
and closing of terminal sessions is interleaved in certain ways,
Cygwin might eventually run out of terminal IDs, even if only few of
them are actually used. High numbers in the TTY column of the 'ps'
output would point to that.
enabled by default, i.e. the "X"/SIGHUP button often
is the only way to close it. Xterm's child process normally is a shell
that does handle SIGHUP correctly, so I guess my concern about an
unclosable terminal isn't really relevant in practice. So sod it, I'll
change mintty t
Hallo Thomas,
Ich habe den Close==SIGHUP Wunsch auf trunk implementiert. Wär toll,
wenn Du das einem Härtetest unterziehen könntest, auch in Verbindung
mit --hold=always und --hold=error.
Gruss,
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http
l wrong? Doesn't backslash in the double
> quote (") acts as an escape character. i.e \s = s, \c = c etc.
http://www.gnu.org/software/bash/manual/bashref.html#Double-Quotes:
The backslash retains its special meaning only when followed by one of
the following characters: ‘$’, ‘`’, ‘
David Byron:
> mkshortcut is returning 8 when I expect it to return 0.
Yep, known issue.
> I'd love a hand getting mkshortcut to return 0 in this case.
Index: src/mkshortcut/mkshortcut.c
===
RCS file: /cvs/cygwin-apps/cygutils/src/m
we should take this to the mintty issue tracker, since the
beta isn't shipped with Cygwin.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
And if that doesn't help:
rxvt -e /bin/bash -l
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
t PATH
(And lose the '-c "exec /bin/bash"' at the end of the rxvt shortcut,
unless you've got a particular reason for double-invoking bash like
that.)
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
reinstall the 'base-files' package at this
point. If you created an /etc/profile just now, delete it first
(because a customised profile won't be overwritten).
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
"od -c" I see
> Then for kicks I tried:
>
> $ touch "\x18"; echo $?
> 0
Have a look in your root directory. There should be a file called x18 there.
> Can someone give me a hand coming up with a command line where I can build
> up filenames t
quot;
mkdir -p "$DEVDIR" || result=1
I haven't stared at the sed magic long enough to work out exactly what
it does or why, but it looks suspiciously like it assumes that Cygwin
is installed on the C drive.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ:
--quoting style option.
> $ ls
> ^X
>
> which seems inconsistent.
Yep, but that's a bash vs ls issue rather than a Cygwin one. You'd get
the same on Linux. But if you use control characters in filenames, you
better know what you're doing anyway. Some argue that it shouldn't b
eady, i.e. they still use Windows
>> "ANSI" APIs.
>
> Guess it's time to roll up my sleeves and write a patch.
That'd be great. Here's a starting point:
http://cygwin.com/ml/cygwin-apps/2010-01/msg1.html
Andy
--
Problem reports: http://cygwin.
; have another case (like "utilities") by any chance?
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
he named file does not exist. Or, a
> directory component in pathname does not exist or is a dangling
> symbolic link.
The way I understand this, the open() call shouldn't fail with ENOENT
given those arguments, because O_CREAT is set and there is no
directory compone
201 - 300 of 1242 matches
Mail list logo
