Re: New Mintty Beta via setup

Lee Rothstein wrote: >> On my sys, uninstalled the old one, and installed nada, zilch, niemands, >> zip, bupkis, nothing, the null set. For some reason, when the test version is selected in setup.exe, the checkbox in the 'Bin?' (as in "Binary", rather than a British waste container) column gets cl

[ANNOUNCEMENT] Testing: mintty-0.7-beta3-1

mintty 0.7-beta3-1 is on its way to the Cygwin mirrors. This is a test release. To install using setup.exe, find mintty on the package selection screen and click on the cycle symbol in the 'New' column until the required version appears. Make sure the checkbox in the 'Bin?' column is ticked. Also

Re: Cygwin Performance and stat()

On 4 June 2010 19:50, Eliot Moss wrote: > I don't think there's an objection here to > patching *rsync* specially in the cygwin > environment -- that would be between you > and the rsync port maintainer. The issue > is whether or not to make a more general > change to cygwin itself, and cgf is just

Re: Listing a non-existent network file

On 2 June 2010 15:53, Corinna Vinschen wrote: > On Jun  2 15:56, Corinna Vinschen wrote: >> On Jun  2 13:55, Christian Franke wrote: >> > Andy Koppe wrote: >> > > On Cygwin 1.7: >> > > $ ls -l //foo/bar >> > > -rw-r--r-- 1 andy Administrat

Listing a non-existent network file

On Cygwin 1.5: $ ls //foo/bar ls: cannot access //foo/bar: No such file or directory On Cygwin 1.7: $ ls -l //foo/bar -rw-r--r-- 1 andy Administrators 0 Dec 1 2006 //foo/bar Server 'foo' doesn't exist, and on both the reply comes after about 10 seconds, presumably a server lookup timeout. I thi

Re: default terminal (was: Re: "can't create master tty" errors)

Lowell Anderson wrote: > May I express my sincere appreciation and a big THANK YOU to Andy and > everyone else involved for your hard work and dedication in providing > mintty. Thanks, my pleasure. Bit embarrassed, because I'm getting more than my fair share of positive feedback here due to mintty

Re: default terminal (was: Re: "can't create master tty" errors)

On 31 May 2010 22:40, L Anderson wrote: > I really like mintty.  However, even though it has the option to 'copy on > select' it requires a right click and paste to insert selected text into the > window. Middle-click pastes by default, and you can change the right-click action to paste on the Mou

default terminal (was: Re: "can't create master tty" errors)

On 31 May 2010 17:47, Christopher Faylor wrote: > I don't remember responding to the original message so, if I didn't, I > apologize. No worries. > Thanks, as always, for your amazing support of mintty.  I wonder if it's > time to just make it the default for the cygwin terminal, knowing that > s

Re: "can't create master tty" errors

On 9 March 2010 21:50, Andy Koppe wrote: > Cesar Crusius: >> I am using Cygwin and SSH to do automated remote builds using Visual >> C++. It works for a few days, but invariably things start failing with >> messages like these (this one from a build log): >> >> Ma

Re: base-files: LOGNAME

On 31 May 2010 09:18, Corinna Vinschen wrote: > On May 30 10:02, Andy Koppe wrote: >> On Sunday, May 30, 2010, Yaakov wrote: >> > POSIX.1[1] describes a LOGNAME environment variable which represents the >> > user's login name.  Adding the following lines to /etc/p

Re: "command not found"-For All Commands

On 30 May 2010 18:48, physicist25 wrote: > I am initiating two ways, 1- using the desktop icon I created and 2-using the > one at start that says mintty. > Their startups screens are "bash-3.2#" and "-sh-3.2$". Does this answer your > question? The result in case 1 is to be expected unless your de

Re: "command not found"-For All Commands

physicist25 wrote: > > Hello, I have recently downloaded cygwin with the hope of learning c++ for > school.the download completed with no problems at all. I installed some > packages such as gcc4, util-linux, ncurses devel, pcre devel, openssl devel, > zlib devel, mintty etc. > > Some Info: > -

Re: base-files: LOGNAME

On Sunday, May 30, 2010, Yaakov wrote: > POSIX.1[1] describes a LOGNAME environment variable which represents the > user's login name.  Adding the following lines to /etc/profile should do the > trick: > > LOGNAME="`logname`" > export LOGNAME > > Where logname(1) is a program supplied by coreutil

Re: 1.7.5 cannot bg mintty

Paul wrote: > I sometimes forget to append a & when opening a new mintty from an existing > mintty. With rxvt this was never a problem, just ^Z and bg in the parent > terminal (my shell is bash  3.2.49-23). This doesn't seem to work for mintty > (0.6.2-1) though - although it seems that the job has

Re: cygpath behaviour when input is not a path

On 29 May 2010 16:20, Gary wrote: > I wrote: >> How should cygcheck > > cygpath, not cygcheck > > /me smacks head > >> behave when given a "PATH list" (e.g., >> '/bin:/usr/bin'), *without* the -p option? >> >> For example: >> $ cygpath -a -p -C ANSI -w /bin:/usr/bin >> C:\cygwin\bin;C:\cygwin\bin >

Re: LANG=ja_JP.Shift_JIS

On 22 May 2010 14:27, rushojp wrote: >> So why do you need to set it to ja_JP.Shift_JIS if ja_JP.CP932 and >> ja_JP.SJIS do the same thing? > > There is no serious reason. > I think IANA name is more famous. Fair enough, but I think it would be misleading to use the official IANA name for what's a

Re: LANG=ja_JP.Shift_JIS

On Friday, May 21, 2010, rushojp: > 2010/5/21 Thomas Wolff: >> As a workaround, you could add the entry >> ja_JP.Shift_JIS·ja_JP.SJIS >> to the file >> /usr/share/locale/locale.alias >> > It works! Thank you! So why do you need to set it to ja_JP.Shift_JIS if ja_JP.CP932 and ja_JP.SJIS do the same

Re: sed doesn't like LANG= anymore

On Thursday, May 20, 2010, Thomas Wolff: > With LANG=anything-unknown, the charmap is set to ASCII, so it works (as > there is at least no multibyte character then). Anything above 0x7F is invalid with charset ASCII though (since 1.7.2). But perhaps sed skips the multibyte conversion functions wh

Re: LANG=ja_JP.Shift_JIS

On Thursday, May 20, 2010, rushojp wrote: > "LANG=ja_JP.Shift_JIS" does not work. > Only SJIS or CP932 support? Yep, and they're both Microsoft's slightly modified variant of standard Shift_JIS. The latter isn't suitable for Windows and Unix command line use because it maps the ASCII backslash cod

Re: sed doesn't like LANG= anymore

On Thursday, May 20, 2010, Jurriaan wrote: > A very long sed script that's been working for ages (back from the 1.5 > age) here has stopped working. > > It turned out sed doesn't like some strings anymore when environment > variable LANG is empty. With LANG=ASCII, there are no problems. > > The act

Re: 1.7.5 cannot bg mintty

On 18/05/2010, cy.20.superconductor wrote: > I sometimes forget to append a & when opening a new mintty from an > existing mintty. With rxvt this was never a problem, just ^Z and bg in > the parent terminal (my shell is bash 3.2.49-23). This doesn't seem to > work for mintty (0.6.2-1) though - alt

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-23.2-1

On Friday, May 14, 2010, Ken Brown wrote: > I tried Ctrl+Alt+Shift+5 in emacs under X11, and it seems to work fine, i.e., > it is recognized as C-M-%.  I also tried it in an xterm window ('emacs -nw'), > and it fails there but in a different way than in mintty: emacs sees it as > C-%. I don't k

Re: V1.7 can not use cursor or backspace within a shell

Matthias Meyer wrote: > cygwin 1.7.5 need, at least, the /usr/share/terminfo/63/cygwin file. > > cygwin 1.7.2, used by the actual copssh distribution, didn't need this file. Third-party Cygwin distributions like copssh aren't supported here. /usr/share/terminfo isn't used by the Cygwin DLL, so th

Re: rxvt : 1.5 vs. 1.7

Oleksandr Gavenko wrote: > On 2010.05.06 8:04, Andy Koppe wrote: >> >> Always on the lookout for ways to improve mintty: what mintty >> shortcomings or rxvt features make you prefer rxvt? >> > My preferred ~/.Xdefaults ? That would mean linking against Xlib or reimpl

Re: V1.7 can not use cursor or backspace within a shell

Matthias Meyer: >> I'm stumped. I think 'cygcheck -svr' output is needed to >> get any further. Please attach, not include it, and make sure you >> delete any sensitive info from it first. > > see attachment :-) You've got Cygwin installed under 'C:/Program Files', which I suspect is likely to cau

Re: rxvt : 1.5 vs. 1.7

Fergus wrote: > Constantly stalling when exiting rxvt in [1.7] (as previously reported; > and still don't understand why, or why this list isn't full of > "Me too"s). This never happens in 1.5. I really prefer rxvt over all > other shells incl mintty. Always on the lookout for ways to improve mint

Re: V1.7 and endless loops triggerd by junction points

Matthias Meyer: > Andy Koppe wrote: >> Matthias Meyer wrote: >>> I've installed cygwin 1.7 in Vista and have two problems, not known prior >>> with cygwin 1.5.25: >>> >>> 1) If I login in a shell (e.g. sh --login -i) I can not use cursor or >

Re: V1.7 and endless loops triggerd by junction points

Matthias Meyer wrote: > I've installed cygwin 1.7 in Vista and have two problems, not known prior > with cygwin 1.5.25: > > 1) If I login in a shell (e.g. sh --login -i) I can not use cursor or > backspace keys. It seems that the cursor can't go into the left direction. > Cursor up will resolve in

Re: Resizing a terminal window

J. David Boyd wrote: > I don't think it is a Cygwin issue at all.  And, I'm certain it is a > remote server problem, as it works on many boxes. > > I was just looking for some help and ideas, and the Cygwin list seemed a > good place to start since I use Cygwin. Right. This list is all about the m

Re: Resizing a terminal window

Thomas Wolff wrote: > LINES and COLUMNS are legacy mechanisms which may serve as a workaround if > the system doesn't otherwise handle screen size changes properly. They > should not be needed on modern systems where the tty driver maintains the > information. Yep. > (You may note that mintty has

Re: Resizing a terminal window

J. David Boyd wrote: > I'm using Cygwin to provide my own X server, and using Xterms locally, > and to connect to remote servers. > > Locally, I can use the mouse to resize a window, and the $COLUMNS and > $LINES variables are automatically filled in. > > On many remote xterm sessions, they aren't.

Re: $PS1 doesn't appear to work the same after version 1.7

lynn wrote: > I use the following to setup my $PS1 bash prompt: > > PS1="\[\033]0;\w\007\033[32m\...@\h\[\033[36m \W\033[0m\]> " > > This attempts to emit the usern...@hostname current_folder>  (in color) You've got the \W and the space before it inside \[...\] which tells readline not to count it

Re: Using nano in mintty : missing cursor

fergus wrote: > Try editing a text document using nano in a mintty terminal. > Press to replace text. > The typed search string at the bottom of the page lacks a visible cursor > (though it is there, as evidenced by use of and and > inserting text) which is a small inconvenience. Fixed on svn t

Re: Is 256 colors possible with cmd.exe?

Alex Leigh: > So my question is, is it possible to get 256 colors > with Cygwin running on top of cmd.exe? As Corinna already said: nope. Windows represents console colours with only four bits: red, green, blue, bright: http://msdn.microsoft.com/en-us/library/ms682013%28v=VS.85%29.aspx Only thing

Re: Using nano in mintty : missing cursor

fergus wrote: > Try editing a text document using nano in a mintty terminal. > Press to replace text. > The typed search string at the bottom of the page lacks a visible cursor > (though it is there, as evidenced by use of and and > inserting text) which is a small inconvenience. Thanks for the

[ANNOUNCEMENT] mintty-0.6.2-1

mintty 0.6.2-1 is on its way to the Cygwin mirrors. This is a maintenance release with a few small fixes and improvements. DESCRIPTION === Mintty is a terminal emulator for Cygwin with a native Windows user interface and minimalist design. Among its features are Unicode support and a graph

Re: Cygwin 1.7.5-1: backspace does not work correctly when using "set -o vi" in pdksh in the console window

RISINGP1: > The ability to modify the character value generated by the Backspace key > is a logical solution rather than forcing people to accept a change to the > 0x7f value. >From the cygwin-1.7.5 release announcement: - Support DEC Backarrow Key Mode escape sequences (ESC [ ? 67 h, ESC [ ? 67

Re: [ANNOUNCEMENT] Updated: groff-1.20.1-1

Christopher Faylor: > I've made a new version of groff available for installation.  This is an > overdue refresh from ftp.gnu.org.  It is reputed to fix the problem > mentioned here: > > http://cygwin.com/ml/cygwin/2010-04/msg00745.html It does indeed. No more funny quotes either. Thanks very much

Re: bash/readline spinout in vi command mode

Jeremy Bopp: >> When you say spin out, do you mean it's fully loading a core? That >> would obviously be a bug, but I don't see that. For me, both with >> ESC-; and Shift-F12 it's just sitting there waiting for more input, >> which to me looks like normal operation because I do know that the >> esc

Re: bash loop using mintty

Jeremy Bopp wrote: > On 4/17/2010 3:31 PM, ERIC HO wrote: >> I  just tested it under xterm and bash loops as well with shift F12. > > I just reproduced this problem with a simpler test case.  Enter vi > editing mode under bash and then type ESC-;.  That is, press the escape > key and then hit the s

Re: bash loop using mintty

ERIC HO wrote: > I reported a couple of times of the bash loop problem before. But it seems > the problem could bot be duplicated > by others. > I use "mintty -" to start up a terminal session. > Today, I found out the problem. The loop is caused by set -o vi in my > .bashrc. After I removed that

Re: 64 bit applications

Andrew P. wrote: > Mingw64 is for compiling x64 Windows applications. > As there no possibilities to run Linux_x86_64 applications under Windows, so > far as I'll try to compile they for Windows x64 What x86-64-specific applications are you talking about? The vast majority of applications compile

Re: mintty: Doesn't know about CTRL key

Corinna Vinschen wrote: > Consider you have more than one mintty window open.  A typical use case > for me is to have one shell open under UAC and the other one with admin > rights to test to test something.  Then I want to close both ttys and > test again with another Cygwin DLL. > > So I press Ct

Re: Cygwin does not have unicode support however FileZilla displays unicode

me scribbled: > Eric wrote: >>> What exactly is coming out as rectangles, i.e. which letters do you >>> expect instead? Are any particular programs affected? >> >> Instead of Chinese characters I get the rectangle box that looks like [] but >> without the gaps. >> >> Programs affected so far are t

Re: Cygwin does not have unicode support however FileZilla displays unicode

Eric wrote: >> What exactly is coming out as rectangles, i.e. which letters do you >> expect instead? Are any particular programs affected? > > Instead of Chinese characters I get the rectangle box that looks like [] but > without the gaps. > > Programs affected so far are the command prompt and f

Re: mintty: Doesn't know about CTRL key

> Corinna Vinschen: >> I'm more and more using mintty for everything (shell, admin shell, >> heating my food, you name it). > > Food as well? It was only meant to make mint tea. Thanks for the endorsement. > :) > > >> Consider you have more than one mintty window open.  A typical use case >> for m

Re: mintty: Doesn't know about CTRL key

Corinna Vinschen: > I'm more and more using mintty for everything (shell, admin shell, > heating my food, you name it). Food as well? It was only meant to make mint tea. Thanks for the endorsement. :) > Consider you have more than one mintty window open.  A typical use case > for me is to have o

Re: Cygwin does not have unicode support however FileZilla displays unicode

Eric wrote: >> Bash does support Unicode, but when running it in a console window you >> need to select an appropriate font in the console window defaults to >> be able to display codepoints outside your language's codepage. Lucida >> Console or Consolas, for example. > > In cygwin's console window

Re: Cygwin does not have unicode support however FileZilla displays unicode

Eric wrote: > Hi I have been confused about a matter between cygwin and the (open)ssh > server package. I think your confusion stems from the fact that Cygwin 1.7, released at the end of last year, does in fact support Unicode (i.e. UTF-8). It's the default. > I believe everything works when  Fi

Re: UTF-8 breaks 'ascii'

Charles Wilson wrote: > Kenneth wrote: >> Maybe it shouldn't attempt to display code points 128..255 >> since they aren't really ascii. > > You're probably right.  Originally, ascii didn't display those code > points; I added it back when a big concern was getting the "correct" > fonts for rxvt-win

Re: 1.7.3: Backspace key not working in GNU screen.

Andrew Schulman wrote: > It sounds as though no change is required in screen for this. Correct. > screen is an ancient program from the dim mists of early terminal days, so I'm > not surprised that it has some problems of this kind. Don't worry, screen isn't doing anything wrong here. Setting th

Re: 1.7.3: Backspace key not working in GNU screen.

Corinna Vinschen: > I think I see what you mean now.  The c_cc[VERASE] value is the one > which is expected for the VERASE functionality (unless it's set to > 0 == _POSIX_VDISABLE), but it has nothing to do with the actual setting > of the backspace key in the terminal.  So, actually the key value

Re: 1.7.3: Backspace key not working in GNU screen.

Christopher Faylor wrote: > I'm not 100% sure that this is the right fix but the new snapshot at > least works around the problem. Thanks. > The problem is that screen explicitly sets VERASE to 0.  I believe that > it does that to mean "there is really no erase character since I'm > handling that

Re: 1.7.3: Backspace key not working in GNU screen.

Christopher Faylor: >>Workarounds: Add 'set CYGWIN=tty' to Cygwin.bat (or wherever you're >>starting your session from), or use one of the other terminals. > > If setting CYGWIN=tty affects the setting of the backspace key for ptys > then that's a bug in Cygwin.  You really should *not* be setting

Re: man pages showing special characters

On 8 April 2010 21:56, Paul Bibbings: >> What font are you using, and what do you get instead of the '-'? > > Well, certainly the font affects the problem.  I had this set to > `Courier'.  However, changing this to `Courier New' solves this for me > and everything renders as I would expect.  For th

Re: 1.7.3: Backspace key not working in GNU screen.

Al G.: > using GNU screen (4.00.03) and trying to backspace by > hitting the backspace key results in nothing happening. The cursor > doesn't move, the character isn't erased and the command remains the > same (if you hit Enter whatever your typo was gets the usual error). Uh oh, this is most like

Re: man pages showing special characters

Paul Bibbings: > FWIW, I am experiencing exactly the same problems as the OP.  I have > mintty set up to use (under Options): > >   Locale       : en_GB >   Character set: UTF-8 > > which matches... > >   19:59:13 Paul bibbi...@jijou >   ~ $env | grep LANG >   LANG=en_GB.UTF-8 > >   19:59:25 Paul b

Re: man pages showing special characters

TheCajun: >> What character set is selected on the Text page of mintty's options? >> Where are you setting LANG and LC_ALL? > > mintty is set to en_US.UTF-8 > > I only exported LANG=c in .bash_profile.  All my other tests were on > commandline. >> >> I'd recommend setting the locale and character s

Re: man pages showing special characters

Durwin De La Rue: > I have searched the archive on this with complicated results. > > First, I am using latest version of cygwin.  I normally use rxvt.  But after > having this issue with it, and finding information that mintty does not have > the issue, I started using mintty.  My first attempt to

Re: UTF-8 in ftp client.

> Oleksandr Gavenko wrote: >>> ...which is good advice.  The other clients MAY support UTF-8 or some >>> other explicit i18n/NLS, but the inetutils bare-bones ftp client >>> doesn't, and won't. >>> >> Won't because religion don't allow? That's a ridiculous question. The GNUs may be rather religiou

Re: Problem with Shift+Left or Right arrow in Cygwin locally (Ctrl isn't noticed) and through SSH (escape code isn't interpreted correctly)

> If I'm in Bash on my Ubuntu system I can use Ctrl+Left Arrow or Right > Arrow to navigate one word at a time to the left and right. When I use > Cygwin it doesn't react to the Ctrl, responding as if I only had > pressed the Left or Right Arrow. Is there a way to fix this? The standard Bash short

Re: mintty - changing colours when logging in to remote host

Gary wrote: >> For example, to set the background >> colour to dark red: >> >> echo $'\e]12;64,0,0\a' > > Err. Well that set my block cursor to dark red, but anyway, yeah, I > get the idea. Oops. 12 indeed is the cursor. 11 is background, 10 is foreground. And the OSC 4 sequence lets you change a

Re: MySQL client, prompt, redux

Jeremy Bopp: > Tim McDaniel wrote: >>  From Google searches and some experience, it appears that it's a >> long-standing situation that, if you run the mysql.exe client program >> under mintty or rxvt from Cygwin, then mysql figures that it's not on >> an interactive terminal and therefore does not

Re: [ANNOUNCEMENT] Updated: cygwin-1.7.3-1

Rurik Christiansen: >> So, did anyone actually read my response here about how this wouldn't >> work for Cygwin?  If so, you'd have to think that these responses were >> pretty off-topic. > > Actually I did but I gracefully disagree :) > > Strictly speaking you are technically perfectly correct. >

Re: mintty - changing colours when logging in to remote host

Gary: > Is it possible to change the colour scheme when connecting to a remote > system, to remind me where I am actually "running"? Yes. There are control sequences for changing the colours, so you could do this with the appropriate echo commands in your remote login script. Or you could have a l

Re: UTF-8 in ftp client.

Oleksandr Gavenko: > How can I force Cygwin ftp client use UTF-8? > > ftp> ls > 200 Port command successful > 150 Opening data channel for directory list. > drwxr-xr-x 1 ftp ftp              0 Oct 16  2009 music > drwxr-xr-x 1 ftp ftp              0 Sep 11  2009 pub > drwxr-xr-x 1 ftp ftp          

Re: Xcompose like input for UTF-8 ?

Rurik Christiansen wrote: > Is there a way to have something similar to Xcompose for utf8 input ? You can have actual Xcompose by running an X server and using xterm or rxvt-unicode. For the console and mintty, you depend on Windows' native mechanisms, in particular, "dead keys". Different keyboa

Re: UTF-8 versus utf8

Tim McDaniel: > Eric Blake: >>> Why does talk >>> all about a charset of UTF-8, then "For a list of locales supported >>> by your Windows machine, use the new locale -a command", which >>> shows "utf8" (which matches my XP machine)? >> >> UTF-8 is

Re: Installing mintty in a restricted environment

Rance Hall wrote: > I had to check the box on setup that said I was installing for just me > so that setup wouldnt try to install shortcuts in ALL USERS which it > does not have the right to do. > > mintty did not self-setup correctly under this scenario. > > I did not get a mintty icon on my deskt

Re: Need help on terminal emulation in Cygwin console

Tomasz Pona: >> No, I meant the big bold text in the middle of that page about sending >> cygcheck output as an attachment. > > I'm not dumb man >> I did see Chuck's followon mail and obviously he knows much more about >> the subject than I do. So, I withdraw my attempt to help. > > ...are you to

Re: spaces in title of mintty command

Roe, Kevin L.: > I have been trying to get the title for mintty to work. > > Specifically, I want a title with spaces. > > I have tried: > > mintty -t one two      result:  obviously didn't work.  It bombed. Because 'one' is takes as the title, and 'two' as a command to execute. > mintty -t "one

Re: Fwd: cannot search for -a in man inside mintty under cygwin-1.7

> moo.tinys wrote: >> >> using mintty >> LANG=zh_CN.UTF-8 mintty >> inside mintty: >> $ man man >> /- >> Pattern not found  (press RETURN) With UTF-8, hyphen/minus symbols in the man page are displays as the Unicode codepoints for hyphen or minus. These are different from ASCII '-', which is why y

Re: "svn --version" halts in 1.7.2-2

Charles Wilson: > Hmm.  I remember having transient problems with svn and many of the > 1.7.0 snapshots, but they were intermittent and I had bigger fish to > fry.  I don't recall any issues with 1.7.1, nor am I having any trouble > with 1.7.2.  However, I would not be surprised if > > (a) the "pro

Re: [ANNOUNCEMENT] mintty-0.6.1-1

Corinna Vinschen: >> - Fall back to /bin/bash rather than /bin/sh if no shell is specified >> otherwise. This is for the benefit of Windows domain account users, >> for whom Cygwin setup does not create /etc/passwd entries by default. > > Wouldn't it be more helpful to open a MessageBox like this:

[ANNOUNCEMENT] mintty-0.6.1-1

mintty 0.6.1-1 is on its way to the Cygwin mirrors. This is a feature release with lots of small improvements, for example, dropped files are now inserted as Cygwin paths and options dialog settings can be specified on the command line using the new -o switch. The mintty manual page ('man mintty')

Re: modified cygwin.bat for rxvt - window does not stay up in 1.7.2

Andy Koppe: > j8raa6t5a9: >> I updated to 1.7.2 and the cygwin.bat I modified ages ago to run rxvt does >> not work anymore.  The window pops up and quickly disappears (I'm using >> Windows XP). >> >> cygwin.bat looks like: >> @echo off >> C:

Re: modified cygwin.bat for rxvt - window does not stay up in 1.7.2

j8raa6t5a9: > I updated to 1.7.2 and the cygwin.bat I modified ages ago to run rxvt does > not work anymore.  The window pops up and quickly disappears (I'm using > Windows XP). > > cygwin.bat looks like: > @echo off > C: > chdir C:\cygwin\bin > rxvt -e bash --login -i Does changing 'bash' to '/

Re: 1.7.2-1: Problems with regtool and cyglsa.

David Rothenberger: > I'm having two problems with cygwin-1.7.2-1: >  * regtool get returns "Error (2): The system cannot find the file >   specified." >  * cyglsa appears to break by system > > I'm using Windows XP SP3. I upgraded to cygwin-1.7.2-1 and then ran > cyglsa-config, which failed becaus

Re: [ANNOUNCEMENT] Updated: cygwin-1.7.2-1

Corinna Vinschen: > Hi Cygwin friends and users, > > we're proud to present the next Cygwin release 1.7.2. It's a hippo! Congratulations! Also, three cheers for 1.7.1, which held up rather well for a .1 release with lots of big changes. Andy -- Problem reports: http://cygwin.com/problems.

Re: text cursor is not being positioned

John Lewis: > My apologies for > the new e-mail, I have subscribed to the mail list so that I can reply > properly in the future. Great, much better without the privacy guff. > This is a fresh install, with no modifications (I haven't even run mkpasswd > yet). > > I start bash with the desktop ic

Re: text cursor is not being positioned

John Lewis wrote: > My text cursor is not being positioned correctly. This is a fresh > install of 1.7.1-1 onto Microsoft Windows XP Professional, Service Pack > 2. > > In the bash shell the backspace key doesn't back up and overwrite the > last character, same with ctrl-U, the line remains on the

Re: mintty - char encoding problems

David Balažic: > Hi! > > I have again LANG=SL  in  minTTY. > > I also see LANG=SL in cmd.exe. > > No idea where it came from. > > Info: > Regional: standards and formats: Slovenian; Location: United States; > Languages (kbd): English > > > I'll post more as I discover things. Any luck with this?

Re: Cygwin vs Via C3: nothing happens, no output

Scott Little: >> Where do you get that idea from that CMOV is optional? Yes, there's a >> CPUID feature bit representing CMOV, but that's always set on the >> i686, its descendants, and compatible processors. Pre-Nehemiah C3s are >> not fully 686-compatible, simple as that. > > Old flamewars, eg. >

Re: Cygwin vs Via C3: nothing happens, no output

scott: > According to the internets... the C3 purports to be a i686-class > processor, and has MMX/3DNow, but does not have the supposedly optional > CMOV instruction that other processors of its class have.  Some people > managed to get i686 kernels to run, some didn't, depending on the distro. P

Re: Cygwin vs Via C3: nothing happens, no output

scott: >>> According to the internets... the C3 purports to be a i686-class >>> processor >> Without CMOV or out-of-order execution, that seems a bit of a scam. > [snip] >> For gcc, "i686" implies the presence of the CMOV instruction, because, >> well, CMOV was introduced with the Intel 686 (aka Pe

Re: Cygwin vs Via C3: nothing happens, no output

scott: >>> I'm attempting to install on a Via EPIA-5000 (533Mhz C3/Samuel 2) >>> without success... is this platform not supported? >>   Hmmm, quite likely not.  Everything in the Cygwin distro is compiled for >> i686 or above CPUs.  C3 is crippled, isn't it?  No SSE/MMX, all that stuff? > > Accord

Re: 1.7.1: cvs version built in is unstable

Roe, Kevin L: > I did read that page and I reiterate: "No write capability"  That includes > USB sticks. Yes, so you've said, and my post didn't doubt that in any way. I'm of course highly intrigued by what high-falutin' mystery system you might be working on. > Please continue to give construct

Re: 1.7.1: cvs version built in is unstable

Roe, Kevin L.: > obcaseinsensitive set to 0 > > What should it be? You could always have a look at the page that Corinna linked to. Oh, and perhaps answer the second part of her question: > Do you have casesensitivity enabled and does the local directory > "Utilities" have another case (like "uti

Re: filenames with characters that have the high bit set

David Byron: > I suppose, but the point about \x18 not working with a character set that > represents the desired codepoint wasn't clear.  Nor was the bash syntax for > using \x in general.  It's in the bash man page and not cygwin-specific, but > an example showing the gory details would have help

Re: filenames with characters that have the high bit set

David Byron: >> > And my ~/.inputrc contains: >> > >> > set meta-flag on >> > set convert-meta off >> > set input-meta on >> > set output-meta on >> >> Makes plenty of sense. But note that meta-flag is a synonym for >> input-meta, so you can remove one of them. > > I was just following the instruct

Re: cygwin 1.7: why there is a directory E/cygwin/dev in the tree of cygwin ?

Christopher Faylor: > rolandc: >>I have installed cygwin 1.7 in e:\cygwin1.7 >>After installation, there is a "strange" directory : >>  /E/cygwin1.7/dev/ (posix path) >>  E:\cygwin1.7\E\cygwin1.7\dev (win32 path) >> >>What is the role of this directory? > > It is "/dev". /dev would be E:\cygwin1.7

Re: filenames with characters that have the high bit set

David Byron: > I've read http://cygwin.com/faq/faq-nochunks.html#faq.using.unicode and > http://cygwin.com/cygwin-ug-net/setup-locale.html but I'm still stumped. > > My cygwin.bat now contains: > > @echo off > > C: > chdir C:\utils\cygwin\bin > set LANG=en_US.UTF-8 > bash --login -I > > And my ~/.i

Re: missing paths

Roe, Kevin L.: > My install is missing the /etc/profile file. > > I think this may be the reason for why I need the '-c "exec /bin/bash"' in my > shortcut. > > What do I need to have in my /etc/profile file besides what you mentioned. Lots. Probably best to reinstall the 'base-files' package at t

Re: missing paths

Roe, Kevin L.: > Ok, I can look at the other machine now (briefly), the sytax there already > has the --login > > So, that is not the problem... Check that /etc/profile actually exists and that it contains these lines near the start: PATH=/usr/local/bin:/usr/bin:/bin:$PATH export PATH (And lose

Re: missing paths

On 12 March 2010 18:57, Roe, Kevin L.: > First off, I cannot run cygcheck and give you the results.  My machine is > completely disconnected from the internet and has no external write > capability. > > I installed 1.7.1 on a machine that already had 1.5.  The machine is a dual > quad core Intel

mintty 0.6-beta3 problem (was: Re: Close==SIGHUP)

Reini Urban: > Looks like 6-beta3 is not good. > > Two mintty sessions with just bash doing nothing keep the CPU busy with 50% > per bash, so that I even cannot successfully open a google chrome url. Thanks. This won't be to do with the Close==SIGHUP thing, since that's not in beta3. And of course

Re: return value of mkshortcut on Windows 7

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

Re: allow executing a path in backslash notation

On 10 March 2010 10:46, Shaddy Baddah: >> The problem is that DOS paths are treated differently, even within the >> same program. >> Take for instance, bash: >> >> $ builtin test -x "$WINDIR\system32\cmd.exe"&&  echo ok >> yes >> $ builtin exec "$WINDIR\system32\cmd.exe" /C echo ok >> -bash: exec:

Close==SIGHUP

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://cygwin.c

Re: terminals getting killed on parent's termination

Thomas Wolff: >> Closing the terminal that a program was started from is not a completely >> unrelated event, > > this is also a matter of taste and use case but just using a command line to > *start* an application does not indicate the intent that the command line > should continue to *host* the

<    1   2   3   4   5   6   7   8   9   10   >