2009/12/1 Ken Brown:
> On 12/1/2009 5:44 AM, John Morrison wrote:
>> Unsetting them in the skel .bashrc files shouldn't be a problem to do, but
>> on my system...
>>
>> $ echo $TMP
>> /cygdrive/c/DOCUME~1/morrijr/LOCALS~1/Temp
>>
>> Tue Dec 01 10:40 AM
>> $ unset TMP
>>
>> Tue Dec 01 10:40 AM
>> $
2009/12/1 Reinier Post:
>> If you want to see the Windows PATH setting unmolested by Cygwin, you
>> will either need to strip out the additions set by /etc/profile or avoid
>> running under an environment modified by /etc/profile.
>
> It doesn't add, actually - it replaces it.
You're wrong. The Cy
2009/12/1 David Antliff:
> I need a way to
> translate "/tmp" to the Cygwin installation directory. I.e. it's not a
> simple case of replacing "/tmp" with "c:/tmp" but rather
> "$CYGWIN_INSTALL_DIR/tmp" and I'm not sure CYGWIN_INSTALL_DIR or
> anything similar exists.
Have a look at the cygpath ut
2009/12/2 jeffunit:
> My program ran fine under cygwin 1.5 as well as many versions of linux
> including
> mandriva 2009, mandriva 2009.1 and mandriva 2010.0
>
> When compiled with
> gcc cal.c -o cal
> and run with
> cal 2009
> I get a segmentation fault.
> When I uncomment line 62, the program run
2009/12/2 Dave Korn:
> Andy Koppe wrote:
>> 2009/12/2 jeffunit:
>>> My program ran fine under cygwin 1.5 as well as many versions of linux
>>> including
>>> mandriva 2009, mandriva 2009.1 and mandriva 2010.0
>>>
>>> When compiled with
>>
2009/12/2 Angelo Graziosi:
> Corinna Vinschen wrote:
>>
>> And I'd like to ask you to add two one-liner files to your package:
>> http://cygwin.com/ml/cygwin-developers/2009-12/msg00026.html
>
> In my system (XPSP3), some Windows application defined LANG=it_IT.UTF-8 at
> Windows level (all users),
2009/12/3 Linda Walsh:
> In bash I start a copy of gvim.exe (64-bit windows version) in background.
> I disown the job in bash so bash no longer manages the job -- it should be
> a free and clear process (unaffected by bash exiting).
>
> Yet when I exit the bash window (bash running in a console wi
2009/12/4 Andy Koppe:
> 2009/12/3 Linda Walsh:
>> In bash I start a copy of gvim.exe (64-bit windows version) in background.
>> I disown the job in bash so bash no longer manages the job -- it should be
>> a free and clear process (unaffected by bash exiting).
>>
>>
2009/12/4 Christopher Faylor:
>>Hang on, if I do this:
>>
>>$ setsid gvim -display :0 &
>>
>>in a bash console and then close the console, gvim continues to work,
>>so either setsid or gvim itself does detach from the console.
>
> That makes sense. Cygwin sends explicit SIGHUPs to other members of
2009/12/8 Cliff Hones:
> Is UTF-8 character output fully supported in the standard Cygwin
> console ($TERM=cygwin) under Cygwin 1.7?
Yes (except it's limited to the Basic Multilingual Plane). You need to
select a Unicode-capable font in the console properties though.
Basically, anything but the de
2009/12/8 Chip Panarchy:
> I'm unable to install MinGW and GCC libraries.
>
> What other information do you need in order to troubleshoot further?
Erm, describing how you tried to install them and how it went wrong
would be a start.
Also: http://cygwin.com/problems.html
Andy
--
Problem reports:
2009/12/8 Cliff Hones:
> Perhaps setup.exe should offer to generate a shortcut (as well as .bat
> and .ico) with, say, the Lucida font selected?
Or just do so without asking? We've had a number of questions on this
already, and there are likely to be many more. People can always
choose the raster
2009/12/9 Cliff Hones
> I think you missed attaching your fix - or else it has got lost.
Oops. Here's another attempt.
> I would guess the change is to file cygwin/fhandler_console.cc, and
> is simply to remove line 1616 [ cursor_rel (1, 0); ] (after case NULL:)
Yep, except that the patch remove
2009/12/9 Angelo Graziosi:
> It seems that some recent updates in cygwin-1.7 has broken Pine from MinTTY.
> Now, trying to start from MinTTY:
>
> $ pine
> Terminal type "xterm", is unknown.
I can reproduce that by uninstalling the termcap package, so install
that and hopefully you'll be fine. Look
2009/12/8 Chip Panarchy:
> As I'm still having compilation problems, could someone else please
> create a SendMail package for Cygwin?
While waiting for that to happen, have a look at exim, or – in case
all you actually need is forwarding to a remote server – ssmtp.
Andy
--
Problem reports:
tianlijian:
> It is a bug of cygwin. It is nothing to do with what terminal i am
> using OR what LANG i have set.
You'll need to provide more than unsubstantiated assertions to get
help with your issue.
What output are you getting from 'cygpath -D' and what do you expect
instead? Do Chinese char
2009/12/9 Corinna Vinschen:
> On Dec 9 06:21, Andy Koppe wrote:
>> 2009/12/9 Angelo Graziosi:
>> > It seems that some recent updates in cygwin-1.7 has broken Pine from
>> > MinTTY.
>> > Now, trying to start from MinTTY:
>> >
>> > $ pi
2009/12/9 Angelo Graziosi:
>> I can reproduce that by uninstalling the termcap package
>
> This workaround
>
> $ TERM=cygwin pine
>
> seems to work too.
That may cause other problems though, because the keycodes and control
sequences of xterm and cygwin differ in a number of places. Setting
TERM s
2009/12/9 Thomas Wolff:
> So the #define IGN should go as well...
Yep.
> Actually, I don't really understand this code part:
> * What is the purpose of the lookup table for the switch rather than just
> switching on a few special control characters?
Good question.
> * What is the idea of (rando
2009/12/12 Kenneth Wolcott:
> I update frequently.
>
> I always get everything from the standard cygwin mirrors.
>
> I have not seen /usr/share/dict/words or /usr/dict/words for quite
> some time now.
>
> I really like this package and it is not installed on any of our
> proprietary systems at
cp and mv behave differently when trying to overwrite an in-use executable:
$ cp mintty.exe /bin
cp: cannot create regular file `/bin/mintty.exe': Device or resource busy
$ mv mintty.exe /bin
[works fine]
That's on 1.7. On 1.5, both cp and mv fail.
Is that as expected?
Andy
--
Problem reports
2009/12/13 Marc Girod:
> I run a proprietary application, IBM Rational cleartool.exe from cygwin.
> In some usage scenarios which I am now interested in, it prompts the user
> for an interactive decision.
> I do not get this prompt under cygwin (either X --emacs shell or xterm-- or
> the Cygwin ter
2009/12/13 Eric Blake:
>> Same when trying to 'rm' an in-use executable: Works on 1.7, fails with
>> 'Permission denied' on 1.5. Cygwin 1.7 works like Linux here. I don't
>> know whether POSIX requires this behavior.
>
> POSIX allows both behaviors, but the cygwin 1.7 behavior is more like
> Linux
2009/12/13 Dave Korn:
>> I'm currently working on a little utility for this sort of situation.
>> It's called 'conin'
>
> Conin The Barbarian?
Yeah, I guess with all the goodness of Cygwin available, using native
console programs is rather a savage thing to do. ;)
> Heh. This looks pretty inte
2009/12/13 Christian Franke:
> 'cp' does not unlink() before overwriting an existing file, it tries to
> overwrite the data in place. This also fails on *nix, typically with "Text
> file busy".
> 'mv' only modifies the link between file name in directory and file data.
> The OS can keep the old dat
2009/12/13 Marc Girod:
>> Surprised it doesn't work in the Cygwin console, unless you've got
>> CYGWIN=tty set?
>>
> I have. Dave Korn told me to take it away.
> Anyway, no result one way or the other.
Did you restart your Cygwin session? I think that setting only gets
read once at the start of th
2009/12/13 René Berber:
> And there's the old 'ttyfier' which almost worked:
>
> http://sources.redhat.com/ml/cygwin/2006-03/msg00164.html
>
> I say almost because it assumes a fixed terminal size and it fails if
> the output exceeds that size, and there where other problems but the OP
> might find
2009/12/14 LiuYan 刘研:
>
> The only unexpected thing is the empty output of GBK-encoded chinese
> characters when LANG is .UTF-8.
>
> I mean it should display something visible(malformed characters, squares or
> whatever visible characters) regardless the LANG setting.
>
> echo -e "Chinese chara
2009/12/15 Eliot Moss:
> Following the guidelines related to cygwin 1.7, I have
> generally been using LANG=en_US.UTF-8. But I found that
> if I do "man " to get a man page, and then
> search (I have man's "more" program set to "less") for
> a string having a dash in it, say to search for -a in the
2009/12/15 Leo Lagos:
>>> Hi... I've got the following problem, that I'll describe with the
>>> steps, so You can reproduce it...
>>>
>>> 1. open cygwin (normal black command prompt window)
>>> 2. run "rxvt -e bash &" from there
>>> 3. on the rxvt terminal, execute an ssh to any host
>>>
>>> Now, w
2009/12/16 chaos215bar2:
>
> I'm attempting to use rsync to backup from Linux to Windows. This is mostly
> working, except that paths with characters that are not legal in NTFS (< > :
> " / \ | ? *) are not copied because rsync fails to create files and
> directories with names containing these cha
2009/12/16 chaos215bar2:
> I knew Cygwin 1.7 supported unicode, but I didn't realize it also converted
> illegal characters in filenames. I have been using rsync from DeltaCopy, but
> I switched to cwRsync, since it uses Cygwin 1.7. Everything is working great
> now.
Good. But why don't you use Cy
The gcc4-g++ contains about 4000 Java-related headers under
/usr/lib/gcc/i686-pc-cygwin/4.3.4/include/c++. Is that as intended?
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscri
2009/12/18 Marc Girod:
>> the problem is that cleartool is written for Windows
>> thus uses /dev/conout
>>
> I can see /dev/conout, but what can I do with it?
It won't literally be using /dev/conout, because that's a Cygwin
wrapper round a Windows concept.
Cleartool is doing either of two things:
2009/12/20 Rogelio:
> I installed mintty (put the js file in the /bin folder, created a
> short cut, started the shell from that short cut)
You don't need to put the js file in the /bin folder. Its only purpose
is to create a mintty shortcut for you.
However, the easiest way to install mintty is
2009/12/22 Lee D. Rothstein:
> '--icon=c:\_0\hippo_xp.ico' option now breaks mintty.
Works for me, with the icon placed in the same location. This is on
XP, and I tried it both in Cygwin 1.5 and 1.7.
What system are you on? How does it break? Can you run mintty with
that option from an existing
2009/12/22 Lee D. Rothstein:
>>> '--icon=c:\_0\hippo_xp.ico' option now breaks mintty.
>
>> Works for me, with the icon placed in the same location. This is on
>> XP, and I tried it both in Cygwin 1.5 and 1.7.
>
> NB: c:\_0 is my root.
>
> I just looked at the ownership/mode of hippo_xp.ico and it
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
2009/12/23 Lee Rothstein:
> Chris,
>
> Thanks for the reference. As I mentioned, it wasn't retrievable via Google.
> Strange.
>
> As you had stated earlier, the key to solving the problem is to reference:
>
> --icon=c:\_0\cygicons-hippo-vista-0.dll,10 in the shortcut
Hippo hippo hurray!
> Note
2009/12/23 Lee D. Rothstein:
> Just installed 1.7.1. Bravo, again.
>
> Everything seems to be working okay, but every time I start up a Mintty/Bash
> window I get the following
> error message.
>
> -bash: regtool: command not found
>
> Shortcut is:
>
> C:\_0\bin\mintty.exe --icon=c:\_0\cygicons-hi
2009/12/23 Christopher Faylor:
> On Wed, Dec 23, 2009 at 12:37:31PM +0100, Corinna Vinschen wrote:
>>Hi,
>>
>>I just found an unfortunate side-effect of the move of the Cygwin 1.7
>>release area. If you use the new setup.exe for Cygwin 1.7 on a mirror
>>which hasn't catched up with the update yet,
2009/12/23 Andy Koppe:
> 2009/12/23 Christopher Faylor:
>> On Wed, Dec 23, 2009 at 12:37:31PM +0100, Corinna Vinschen wrote:
>>>Hi,
>>>
>>>I just found an unfortunate side-effect of the move of the Cygwin 1.7
>>>release area. If you use the new setup.e
2009/12/24 Fergus:
> Thanks for great new version.
>
> 1.7 uses setup.ini, draws from release/, uses setup.exe v.2.673.
> 1.5 uses setup-legacy.ini, draws from release-legacy/, uses setup.exe
> v.2.673 (i.e. the same version as 1.7).
No, 1.5 you uses http://www.cygwin.com/setup-legacy.exe
Andy
-
2009/12/24 Paul McFerrin:
> I did the upgrade to 1.7.1-1 without any problems. During the remainder of
> the day, I accidentally blew away my installation of 1.7.1-1. I restored my
> installation from a backup several days old (1.7.0-65). Now I'm trying to
> upgrade again.
>
> Now the questions
2009/12/24 Gregg Levine:
> My other problems are the typically idiotic Windows problems
> concerning removing a directory (or a directory of directories). The
> system refuses to believe that I have the rights to remove that
> directory.
Use 'rm -rf' from your new Cygwin install. Much faster than
2009/12/24 Ken Brown:
> In the latest mintty (0.5.5-1), RightAlt plus f (or b) doesn't move the
> cursor one word forward (or backward) when editing the command line. The
> LeftAlt key still works as expected.
Confirmed. As a workaround, switch on the Ctrl+LeftAlt is AltGr option
on the Keyboard p
2009/12/24 Linda Walsh:
> It appears several files are missing.
> I have no mkpasswd or group, no mount. Don't know what else is missing.
> I do have 'sed', but it might have been there from before (I didn't
> reinstall
> it).
>
> I've done a cygcheck -c to see if any packages had missing f
2009/12/24 Andy Koppe:
> 2009/12/24 Ken Brown:
>> In the latest mintty (0.5.5-1), RightAlt plus f (or b) doesn't move the
>> cursor one word forward (or backward) when editing the command line. The
>> LeftAlt key still works as expected.
>
> Confirmed. As a workar
2009/12/25 Mark Geisert:
> Josh writes:
> [...a bunch of detailed stuff...]
>
> If this were really a Cygwin program you likely wouldn't be #include-ing
> winsock.h. Is this a native Windows program you're just trying to build with
> gcc? If so, you likely don't want Cygwin, you want MinGW, a sep
2009/12/25 Ric Anderson:
> For a variety of reasons, I need a way to switch the character sent by the
> Console Window Backspace key from ASCII \177 to ASCII \008 (that is, make
> the backspace key send the ASCII backspace character like it did in older
> cygwin versions).
Can't be done at the mo
2009/12/26 Wes S :
> Below is excerpt from man file on touch. Highlighted text is showing
> strange characters when I use putty to ssh in. It was working fine
> before the 1.7 upgrade.
>
> How do I fix this?
>
> Thanks,
>
> Wes
>
>
> âd, ââdate=STRING
> parse STRING and use it
2009/12/25 Andy Koppe:
> 2009/12/25 Ric Anderson:
>> For a variety of reasons, I need a way to switch the character sent by the
>> Console Window Backspace key from ASCII \177 to ASCII \008 (that is, make
>> the backspace key send the ASCII backspace character like it d
2009/12/26 Charles Wilson:
> There's one remaining problem with your scenario: when the Xserver is
> not available, and the option is used:
>
>
>
>
>
> -e /bin/bash
>
>
>
> mintty *IS* launched: it shows up in the process list, but the window is
> not visible. I'm not sure
2009/12/27 Jerry DeLisle:
> I have been using the 1.7 beta without any issues up until the official
> release. I try to run 1.7.1 setup and nothing happens, it just exits
> without even opening a window.
>
> Trying to run the previous version of setup works until it encounters
> setup.ini which no
2009/12/27 Jerry DeLisle:
> I am going to try a completely fresh install. I have nothing to lose.
No point in that. I'm afraid you'll need to wait for a setup.exe fix.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
2009/12/27 Bernd Bartmann:
>> What does:
>>
>> c:\cygwin\bin\cygcheck c:\cygwin\bin\bash.exe
>>
>> show? It will probably show that you're missing some basic dlls
>> which, for some reason, will need to be (re)installed.
>>
>> You can find the packages which hold the missing dlls by going to
>> ht
> On 2009/12/27 7:56 PM, Adam Rosi-Kessel wrote:
>> But when I
>> view them from the linux box, they have scrambled accents -- either just
>> ?'s if I use ls (must be a terminal issue)
You probably haven't got a charset configured on the Linux box. In
that case, ASCII is assumed, and 'ls' prints a
2009/12/28 Rodrigo Medina:
> Hi,
> I am moving from cygwin-1.5 and gcc3.4 to cygwin1.7 and gcc4.
> Some simple programs of mine fail.
>
> I am using LC_ALL=es_VE.ISO-8859-15.
>
> I have reduced the problem to this example
>
> --
> #include
> main()
> {
> static char* line1 =
> " This l
2009/12/28 Andy Koppe:
> 2009/12/28 Rodrigo Medina:
>> Hi,
>> I am moving from cygwin-1.5 and gcc3.4 to cygwin1.7 and gcc4.
>> Some simple programs of mine fail.
>>
>> I am using LC_ALL=es_VE.ISO-8859-15.
>>
>> I have reduced the problem to this exam
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
2009/12/29 Rodrigo Medina:
>>Ah, the problem actually is that your program is missing a call to
>>setlocale(LC_CTYPE, "") to switch to the locale and character set
>>specified in the environment...
>
> That worked!, but what that means is that if one wants to
> use any locale other than C.UTF-8, on
2009/12/29 Eric Blake:
>> I couldn't find specific text about invalid bytes in the POSIX printf
>> spec,
>
> http://www.opengroup.org/onlinepubs/9699919799/functions/fprintf.html
>
> "all forms of fprintf() shall fail if:
>
> [EILSEQ]
> [CX] A wide-character code that does not correspond to a va
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: http://cygwin.com/proble
> Some comments:
> 1- I think that printf(string_constant) and printf(char_array) should give
> the same
> output in any circumstance.
> 2- In absence of a call to setlocale printf((string_constant) writes
> according to
> the locale of the environment, but printf(char_array) does not, even
> tho
2009/12/30 Gary Carvell:
X issues including xterm ones should go to the cygwin-xfree list. I'm
sending this to both lists, but please respond on cygwin-xfree only.
> With the upgrade to Cygwin 1.7, I found that the Alt key is no longer
> recognized as a Meta key in xterm. This means the Alt based
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
2009/12/30 Larry Hall (Cygwin):
>> I've been using gcc and other tools in older versions of cygwin with
>> 32-bit Windows XP and Vista from windows command prompt (cmd.exe)
>> without problems. But now I'm using 64-bit Windows 7, and some command
>> line tools like gcc.exe do not work anymore (from
2010/1/1 Gunnar Vestergaard:
> I prefer that Emacs accepts input from my Faroese keyboard, or at least
> Danish if need be. Whatever I do, the US keyboard mapping is in effect
> always. How do I change that? I mean, for every X11 application?
X questions should go to the cygwin-xfree list.
The X
Lee Rothstein:
>> Will Windows junctions (for the path; plus the file name) work, here?
Don't think so, afaik junction points (introduced in Win2000, and
different from Vista/7 symlinks) work correctly for directories only.
Hard links, however, should work just fine for the problem at hand.
tul
2010/1/2 Charles Wilson:
> ncurses is a package that provides character and terminal handling
> libraries, including 'gui-like' panels and menus. It is often used
> instead of termcap. ncursesw provides a version of this library and
> related tools compiled to support wide characters (that is, wch
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 starting with "\\?\",
e.g. "\\?\C:\cygwin\bash.exe".
Yet un
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
2010/1/4 Joseph Quinsey
> In Cygwin 1,7.1, sprintf() with the format string having an 8th bit set
> appears to be broken. Sample code (where I've indicated the backslashes in
> the comments, in case they are stripped out by the mailer):
>
> #include
>
> int main (void)
> {
> unsigned char foo[3
2010/1/4 Thomas Wolff:
> My assumption has been that *printf should be byte-transparent unless where
> it uses explicit wide character arguments.
What's that assumption based on?
> After all, legacy applications that do not care about locales at all may
> legitimately assume this since a C char
2010/1/4 Joseph Quinsey:
> 1) In my bad test, I already had my LOCALE set to C.ASCII:
>
> env | grep LC
> LC_ALL=C.ASCII
To use the locale set in the environment you need to invoke
setlocale(LC_CTYPE, ""), i.e. with an empty string as the second
parameter. Without a setlocale call, your progra
2010/1/4 tim richardson:
> I've setup rxvt, and take the default term settings.
> This is the latest cygwin as of today, Vista host.
>
> when I do man x, I get odd characters: mis-interpreted control characters.
> The default cygwin terminal works fine.
>
> for example, if I do
> man man
>
> I get
2010/1/5 Vadim Zeitlin:
> Exactly the same thing happens here with 1.7.1 under 64-bit Windows 7.
> However my Cygwin is not a new install but an upgrade of a previous 1.5
> installation -- in which Git worked just fine.
Does the locale setting make a difference? For example, try it with
the follo
2010/1/5 Paul Keusemann:
>> I have previously used Cygwin 1.5 successfully, but thought I should
>> report a possible issue with the newer 1.7.1 version.
>>
>> My XP workstation blue screens reliably when doing the final steps of the
>> Cygwin 1.7.1 installation somewhere in the /etc/postinstall/*.
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
--
Problem reports: http://cy
2010/1/6 RH:
> KJ writes:
>> within a cygwin shell I used to pipe some data into a windows program
>> (sqlcmd.exe) which used to work pretty well. Since upgrading to version
>> 1.7 I get the following error:
>> $ echo "select @@version" | sqlcmd
>> Sqlcmd: Error: Internal error at ReadTextLine (Rea
2010/1/6 Wes Barris:
> I just installed Cygwin 1.7.1 and Puttycyg 20091228. When I viewed
> a man page I saw the letter 'a' with two dots above it instead of
> '-' characters. So, knowing that Cygwin 1.7 now used UTF-8, I changed
> my character translation set in Puttycyg to UTF-8 for my Cygwin
>
2010/1/6 RH:
> echo "select * from mytable" | unix2dos | sqlcmd -S server -U sa -P mypassword
> -d myDatabase
>
> As you can see I'm trying to force the data hitting sqlcmd to be in dos mode
> but
> somehow I suspect it is getting put into linux-mode line endings before
> hitting
> sqlcmd. The e
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
2010/1/8 Thomas Wolff:
> Andrew Schulman wrote:
>>
>> A new version of orpie, 1.5.1-2, is now available in the Cygwin
>> distribution.
>>
>> This release is a Cygwin-only update. The package has been rebuilt for
>> Cygwin
>> 1.7, removing dependence on some obsolete packages. I recommend that all
2010/1/8 Andrew Schulman:
> * In order for lapack to work, you have to have /usr/lib/lapack in your
> $PATH. IMO that's a bug
I agree, and I shudder to think what the path would look like if every
library did that. I don't see why the lapack DLLs can't go into
/usr/bin like everything else.
Than
> Hi,
> I discovered that the HOME variable is set in windows. I therefore get the
> cygwin HOME path set to this window path instead of the path set in passwd
> as I would like it. I tried to delete the windows HOME path, but I can't
> find it. Where is it set or what does set it? I have HOME, HOM
2010/1/11 aputerguy
>
> Here is the situation:
>
> Running from a cygwin 1.7 bash terminal:
> $ emacs -nw
>
>
> $emacsclient -nw
> *ERROR*: Not using an ASCII terminal now; cannot make a new ASCII frame
>
> $echo $TERM
> cygwin
>
> Running from within screen within cygwin:
> $ emacs -nw
> emacs: s
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.com/
2010/1/12 Nellis, Kenneth:
> Thank you, Jeremy. BTW, I deal with legacy machines that don't
> know from SSH. :-(
>
> Well this gets more interesting, at least to me...
> With LANG=UTF-8, man uses the Unicode HYPHEN character (U+2010)
> to break long words at the right margin, and uses the Unicode
>
2010/1/12 Niklaus Kuehnis:
> I've upgraded to Cygwin 1.7 (release version, clean install) and now am
> unable to print text files with non-ascii characters (i.e. German umlauts)
> from commandline.
>
> On Cygwin 1.5 printing used to work with a2ps but now all umlauts are
> replaced by strange ch
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.
Andy
--
Problem
2010/1/13 Corinna Vinschen:
> That only occurs in CYGWIN=tty mode. The problem was that in tty mode a
> piece of code reset all termios settings of the console to 0. That was
> no problem so far, but now that the VERASE key from the termios settings
> is used to delete chars in the console, it hu
2010/1/14 Manish Agarwal:
> These are the packages/commands/features which I have been using with
> cygwin. I am unable to install them through a "fresh" setup.Reason for
> not being able to install: they no longer exist in the package select
> window.
>
> xdvi (I _have_ installed and using tetex,
2010/1/14 Fergus:
> I installed portable Cygwin to a low-capacity USB stick by "picking" Base
> and then extras from the selection menu. Amongst other things I picked up
> xterm, Lyx, TeX. (I've done this item-by-item selection a few times in the
> past but not recently; and never with 1.7.)
> Some
Corinna Vinschen:
> aputerguy:
>> Is it best to leave it that way or would it be better to set it to something
>> like LANG=en-US.UTF-8 (or even C)
>
> Not necessary. As described in the User's Guide, the default locale
> in the absence of a LC_ALL/LC_CTYPE/LANG variable is "C.UTF-8".
I'd still r
2010/1/14 Jason Pyeron :
> When doing man grep it blurted out many <##> hex codes. If I unset LANG,
> LANGVAR I get extended ascii. I am using teraterm to connect via ssh.
What's 'extended ascii'?
You need to ensure that your terminal is set to the same character set
as Cygwin. The second of you
2010/1/15 Niklaus Kuehnis:
>> If you want to
>> be sure to use UTF-8, then say so: export LANG=de_CH.UTF-8.
>
> I set this variable (and also LC_CTYPE and LC_ALL), and printing with
> umlauts with bare a2ps works fine now. Thanks!
I can't confirm that. Sure you were printing a UTF-8 file there?
Sven Köhler:
> David Smiley:
>> I have been fed-up with the default GUI shell on Cygwin, being used to the
>> great Terminal that comes with Mac OS X. Some googling around uncovered
>> that I should try "rxvt". My experience with rxvt is pretty good, after
>> reading online some basic configurati
2010/1/20 indrek:
> I'm using make/gcc for compiling applications. It generates a lot of output.
> I need to highlight some keywords (show red text), in example "error".
> Is it possible with Cygwin.
Have a look at the colorgcc package as well.
(Unfortunately its default config is broken, looking
1 - 100 of 1001 matches
Mail list logo
