Re: Compiling Cygwin on Linux
On Sat, 05 Apr 2008 00:29:06 -0700, Brian Dessent wrote: I can assure you that many of us cross compile Cygwin on Linux regularly... Er, why? -- Chris Game If at first you don't succeed, call it version 1.0 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Error opening terminal: cygwin.
On Fri, 4 Apr 2008 14:33:16 +0200, Corinna Vinschen wrote: You could copy the file from a machine which has that file, or, as a temporary hack, try to set terminal type to linux or xterm. Good luck trying to find a terminal that works with UTF-8. -- Chris Game All generalizations are false, including this one. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rxvt, once again...
In a recent post, Rui Carmo wrote: On Monday, Dec 23, 2002, at 11:58 Europe/Lisbon, Chris Game wrote: That's interesting, but what's the advantage of rxvt over opening cygwin/bash in a Windows command window, where all the formatting options (except initial placement I grant you) are available from the prompt window properties? The main of rxvt advantage for someone who uses Unix terminals extensively is a fully dynamic, resizable terminal window - something the built-in W2K/XP prompt cannot provide. And I mean resizable as in height _and_ width. Height and Width are adjustable from the properties of the command prompt window. -- === Chris Game chrisgame@!yahoo!dotcodotuk === -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bugs in Cygnus Tools bash
In a recent post, Cliff Hones wrote: A word of advice - don't report things as bugs unless you are sure they are bugs and not cockpit error - it can make you look foolish if you or your configuration are to blame. That seems a bit harsh. How else are people supposed to figure out what's wrong if they don't ask? There's no such thing as a stupid question, and any mis-reported bug gives an opportunity for Cygwin's usability to be improved - even if it's the documentation! And a few of us less-than-experts on here benefit from other's mistakes. -- === Chris Game chrisgame@!yahoo!dotcodotuk === -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rxvt, once again...
In a recent post, Rui Carmo wrote: [...] After all, we can debate this till the reindeer pass overhead, but nothing we can say actually replaces _using_ the darn thing and figuring out the differences for yourself. Of course you can say that about a lot of things. Unfortunately, life's just too short. That's why the advice from those who know about these things is so valuable. So thanks, Rui, and all those who took the trouble to respond. Season's Greetings to all! -- === Chris Game chrisgame@!yahoo!dotcodotuk === -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rxvt, once again...
In an earlier post, Randall R Schulz wrote: So, create a Windows shortcut by right-dragging your RXVT executable icon to some new location (start with the desktop; when you're done, put it in the Start menu or the QuickLaunch bar, e.g.). Now open the properties dialog for the shortcut. In the Shortcut tab you can control the arguments (set window size and position here using usual X Window -g / -geometry option) and any other RXVT options you like (font, scrollback, colors, etc.). Here's what I use: D:\cygwin\bin\rxvt.exe -g 110x89+485+-1 -bg #dd -fg #00 -fn Lucida ConsoleP-11 -sr -sl 5000 -tn rxvt -vb -e /bin/bash --login -i I set the initial working directory (Start in: field) to my Cygwin home directory (using Windows path name notation, of course). That's interesting, but what's the advantage of rxvt over opening cygwin/bash in a Windows command window, where all the formatting options (except initial placement I grant you) are available from the prompt window properties? -- === Chris Game chrisgame@!yahoo!dotcodotuk === -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: HOME set to / [Was: cygwin-1.3.16-1]
In an earlier post, John Morrison wrote: [...] The way this is set has changed and *should* work ootb with a clean installation. The easiest way (I believe) atm is to... $ cp /etc/group /etc/group.old $ cp /etc/passwd /etc/passwd.old $ /etc/postinstall/passwd-grp.sh.done this should recreate /etc/group and /etc/passwd (check before closing!) Then close and restart cygwin. You should now be your domain user *not* your local Admin. Also note that /etc/profile has changed, the new version is kept as /etc/profile.default and should not overwrite any previous copy. The functionality has changed slightly. It doesn't run ~/.bashrc by default, as per specs it runs ~/.bash_profile which should check and, if appropriate, run ~/.bashrc Feel free to change how this works - it is your system afterall :) Ah! Thanks for useful hints - now how do I get out of this 'None' group that I'm apparently in, and into 'Users' or even 'Administrators'? -- === Chris Game chrisgame@!yahoo!dotcodotuk === -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: bash isn't running my .bashrc!
In an earlier post, Larry Hall (RFK Partners, Inc) wrote: The login shell stuff sent me to look at the etc/passwd file and the stuff about that in the cygwin FAQ. As an occasional user of cygwin I have to say I find these documents written at too high a level to take in easily. A couple of hours searching for and reading and understanding docs is way too much for occasional users. Understood. Would you like to offer some suggestions/additions for the documentation with a patch? (I actually meant the Cygwin User Guide, not the FAQ) That would be a great suggestion Larry, if I were in a position to know what the docs should say! -- === Chris Game chrisgame@!yahoo!dotcodotuk === -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Moving cygwin discussions to Usenet? (e.g., alt.os.cygwin)
In an earlier post, Chris January said... Tried the Cygwin TWiki? http://www.doc.ic.ac.uk/~ccj00/twiki/bin/view/Cygwin It's maintained by NanFudd aka Charles Howes. Just make a page for beginner's questions there. Hopefully some helpful souls will check back every so often ;) The internal URLs don't seem to be set up right; but there's some interesting things on there, thanks. C. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
s2p tool
Anyone know why the s2p tool in Cygwin seems to demand brackets '('
around substitution lines in a sed script? What form of script does
it expect? Using echo and piping one-liners at the tool works but it
doesn't seem to like script files much.
C.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: s2p tool
In an earlier post, Gerrit P. Haase said...
Hallo Chris,
Am Montag, 20. Mai 2002 um 11:47 schriebst du:
Anyone know why the s2p tool in Cygwin seems to demand brackets '('
around substitution lines in a sed script? What form of script does
it expect? Using echo and piping one-liners at the tool works but it
doesn't seem to like script files much.
Can you please post a small example/testcase of this 'bug'?
On further investigation there are two things going on. First the
error message was overwriting itself onto one line, so sticking a \n
into the s2p script solved that annoyance. Then after further
fiddling I realised that setting the fileformat=unix rather than dos
(in vim) solved the problem. The script wasn't apparently built for
cross platform work!
Thanks for the prompt response.
C.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Bash shell in Cygwin/Windows
After spending ages trying to understand the syntax and highlighting to get the colours/colors in Vim to look nice, I realise that when I display a Man page some keywords are disappearing into the background, because of the default command window properties choices. If I change the props the vim colours/colors are shot to hell, so I'd like to understand how bash decides what keywords to highlight and where those colours/colors are defined? I can fire escape sequences through the command prompt to change colours/colors quickly (BTW how's that work? No ANSI.SYS on this winXP system - Oh I see there's one in the cygwin area, is that it?) as a quick fix but I'd like to understand this better. -- === Chris Game [EMAIL PROTECTED] === -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
