2009/7/8 Stephen M. Kenton:
> Something very strange is going on. It happened on the second system also. I
> did a full Cygwin 1.7 install on the HP Media Center PC running Windows XP
> Media Center Edition at the lab and got the same results. After the install
> I pulled up a console and did a una
2009/7/7 William Deegan:
> If you do a from scratch install recently, you
> do not get the "XWin Server" under "Cygwin-X".
> For my install I did install the x windows, and can start from startx
> in the shell or the startxwin.bat, just no menu item.
Known issue: http://article.gmane.org/gmane.os.
2009/7/5 Sylvain Pasche:
> (by the way, I recently discovered MinTTY and I'm pretty impressed. MinTTY +
> screen offers a very nice multiple-tab environment on Cygwin).
Thanks!
Btw, you can enable browser-style tab switching with (Shift+)Ctrl+Tab
by mapping MinTTY's keycodes for those in .screenr
2009/7/5 Christopher Faylor:
>>I see the code for invoking it, but I don't fully understand it: how
>>come the helper process doesn't show up in task manager?
>
> In my testing, just starting the helper app with SW_HIDE creates a
> process which doesn't live on the toolbar. But, as the comments sa
2009/7/5 Christopher Faylor:
> I've checked in a workaround for the problem:
>
> http://cygwin.com/ml/cygwin-cvs/2009-q3/msg00010.html
>
> I checked this by removing the Windows 7 code from mintty and rebuilding
> it. With the currently released version of Cygwin 1.7.0-50 this causes
> a windows c
2009/7/4 Harry Putnam :
>>> I'd like to be able to open a cygwin shell at a specific location
>>> from windows explorer. Something like the old windows `power toy'
>>> where you could open a windows cmdline shell HERE.
>>
>> It exists; it's in the cygwin distro; it's called "chere" and you
>> ca
2009/7/3 Corinna Vinschen:
> I have some testing code which only tries to create an invisible console
> if the application to execv is not a Cygwin application. It seems to
> work nicely. I'm just not sure if it's really *that* simple...
Me neither.
Given that Cygwin applications themselves ar
2009/7/2 Eray Ozkura:
> I prefer not to subscribe to any high-volume lists, so if you have an
> answer please CC to me.
Ever heard of mail filters?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs
2009/7/2 Julio Costa :
> HKCU\Console\\WindowPosition = 0x80008000
Good idea!
> Why on Earth are we having this trouble to have an available console
> all the time? Is it necessary to redirect the in/out streams? Is it
> another thing?
>From earlier in the thread:
> me:
>> The proper, yet prob
2009/7/2 Jonathan :
> I still see 100% CPU usage per core with the latest snapshot (2009-07-01)
>
> I've tried removing tortoisesvn and virtualbox and still have performance
> issues, is my next step trying a clean windows install?
Only if you're gonna install XP. ;)
Andy
--
Problem reports:
2009/7/2 Christopher Faylor:
> And for those who want to wail about this, take a look at the various
> "Why is Cygwin so slow" threads that have been here in the last
> month. Every special case accommodation we make to allow MS-DOSisms
> to work seamlessly adds code to Cygwin and cause corres
2009/6/23 Christopher Faylor:
>>If posix_spawn() ever gets implemented in Cygwin to
>>avoid the slowness of fork(), /bin/sh might well change to the first
>>shell that supports it.
>
> It's really somewhat of an urban myth about Cygwin's fork being slow.
> Cygwin's exec is also pretty slow. I'm no
Shortcuts created by postinstall scripts using mkshortcut --allusers
--smprograms aren't readable for ordinary users, so all they get to
see in the start menu is a white dummy icon that doesn't do anything.
This affects both MinTTY and rxvt, at least with Cygwin 1.7 on Windows
7. I guess the script
2009/6/29 Dave Tang:
> So I've changed my home directory to /home/d.tang in my passwd file. I
> copied the .bashrc into my new home directory.
>
> But when I restart cygwin, it still doesn't load the .bashrc.
Bash on Cygwin is normally invoked as a login shell, in which case it
doesn't source .bas
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/6/15 Corinna Vinschen:
>> > Define the default for ja, ko, and zh to use width = 2, with a
>> > @cjknarrow (or whatever) modifier to use width = 1.
>>
>> I think it is good idea.
>
> If everybody agrees to this suggestion, here's the patch. Tested
> with various combinations like
>
> lang=ja
2009/6/26 Corinna Vinschen:
> On Jun 26 15:08, Julio Costa wrote:
>> I've been following this discussion, crossing fingers to someone came
>> to some conclusion, as this is the biggest show-stopper for Cygwin in
>> several months.
>>
>> I've not access to a Win 7, but I would like at least to drop
2009/6/26 Corinna Vinschen:
> > > Yes, I thought of trying AttachConsole first. It's a band-aid since
> > > it will of course not work if there's just no parent console
> >
> > That can be dealt with, because AttachConsole reports back whether it
> > did manage to attach, so if it doesn't, one can
2009/6/26 Corinna Vinschen:
>> Forgot to say: the occurances of this could at least be reduced by
>> trying AttachConsole to get a hold on the parent process' console, if
>> any. When I attempted that in MinTTY, though, I couldn't make it work.
>
> Yes, I thought of trying AttachConsole first. It'
2009/6/26 Corinna Vinschen:
>> The proper, yet probably completely impractical solution: compile
>> Cygwin programs for the GUI subsystem instead of the console one and
>> attach to the parent process' console, if any, with explicit calls at
>> program startup. POSIX programs don't use the Win32 co
2009/6/26 Corinna Vinschen
> The issue will definitely not be fixed in RTM. Oh well.
:(
> We will have
> to find a W7 workaround for our method of creating a hidden console. I
> have asked Microsoft to provide us with a workaround but I have no
> really big hope that they can or will do it. An
2009/6/26 Mark Harig
>
> Is is possible to display the upper 128 entries in the ASCII
> table in mintty using the 'cygutils' application 'ascii'?
>
> I have attempted to use two configurations, but neither one
> displays the table without problems in mintty:
>
> Configuration 1:
>
> - mintty: Usi
2009/6/26 Mark Harig:
>> From the 0.4.0 release announcement:
>>
>> - MinTTY now has its own identity, instead of pretending to be an old
>> xterm. The ^E answerback string is "mintty", the ^[[c primary device
>> attribute command reports a vt100, and the ^[[>c secondary DA command
>> reports termi
2009/6/25 Andrew Schulman:
>> After upgrading to mintty-0.4.1-1, the Enter, +, -, *, and / keys on my
>> number pad no longer with in orpie. Reverting to mintty-0.4.0-2 solves
>> the problem. Also, running "TERM=cygwin orpie" also solves the problem.
>> (TERM=xterm by default for me. I have no idea
2009/6/26 Matt Wozniski:
>
> > There's a bit in the TIPS section of the manual on how to set any
> > environment variable using the shell's -c option, e.g.:
> >
> > mintty sh -c "TERM=xterm-256color emacs"
>
> Hm. Maybe I'm missing something, but - isn't this a place where using
> /bin/env would m
2009/6/25 David Rothenberge:
>>> After upgrading to mintty-0.4.1-1, the Enter, +, -, *,
>>> and / keys on my number pad no longer with in orpie.
>>> Reverting to mintty-0.4.0-2 solves the problem.
>>
>> Sure about 0.4.0-2?
>
> Yup. I checked it a number of times.
Ah, you're right; I hadn't tried i
2009/6/25 Mark Harig:
> > (TERM=xterm by default for me. I have no idea where that comes from.)
>
> This is documented in the manual page for 'mintty':
>
>> TERM variable
>> The TERM variable for the child process is set to "xterm", so that pro‐
>> grams that pay attention to it expect xterm keycod
2009/6/25 David Rothenberger:
> After upgrading to mintty-0.4.1-1, the Enter, +, -, *,
> and / keys on my number pad no longer with in orpie.
> Reverting to mintty-0.4.0-2 solves the problem.
Sure about 0.4.0-2? I'm finding the behaviour changed between 0.4-rc3
and 0.4-rc4. That's when the keycode
2009/6/25 Mark Harig:
>> > At the bash shell prompt while editing commands is one example, but
>> > it is also the case for me in text editors, vim or emacs, for example.
>> > From the Options menu, I set the cursor type to block and set the
>> > cursor color to a light color, say, yellow, and then
2009/6/24 GJ Hagenaars:
> Hi there,
>
> On a Windows Server 2008, running cronbug from the (bash) command line
> results in an ever increasing cronbug.txt file because cygcheck walks the
> registry and gets into an infinite loop.
>
> It will repeatedly find these entries, deeper and deeper in the r
2009/6/23 Christopher Faylor:
> On Tue, Jun 23, 2009 at 04:13:39PM -0500, Thrall, Bryan wrote:
> >> Where can I find documentation on the setup-1.7.exe command line
> >> options, in particular the one for installing packages without
> >> invoking the GUI that I think was added last year?
> >>
> >>
2009/6/23 Mark Harig :
>> The background colour is used for text beneath the cursor, so if the
>> cursor is visible infront of the background, the text beneath the
>> cursor should be visible too. With the default white-on-black colours,
>> you get black text inside a white cursor block.
>>
>> Is i
Where can I find documentation on the setup-1.7.exe command line
options, in particular the one for installing packages without
invoking the GUI that I think was added last year?
I had a look in all the places I could think of, but without success,
and invoking setup with -h, -H, -help or --help d
2009/6/22 Mark Harig:
> 1. There is no description of the '-e' switch in mintty's manual page.
> Is it an "execute-this-command" option? Or, should the user be
> aware that it is specific to "execute this shell"?
The -e option was added for compatibility with xterm and other
terminals, but 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/6/18 Thomas.Wolff:
> And as a matter of fact,
> you can run both xterm and MinTTY with a non-CJK locale and ambiguous
> characters being wide. This is achieved by invoking xterm -cjk_width or
> by selecting an according font in MinTTY, e.g. Ming, SimSun, MS Mincho,
> or even just the popular L
2009/6/15 Christopher Faylor:
>>One issue that I've noticed on Windows 7, both with Cygwin 1.5 and
>>1.7, is that trying to log a utmp entry when starting a terminal can
>>take up to half a minute, presumably due to waiting for some sort of
>>timeout.
>
> Sorry but this isn't a much more useful rep
> Until now I was using cygwin on Windows XP and I was satisfied by
> cygwin-1.7 but these last few days
> I switched to a more powerful laptop with very fast hardware (Core Duo 3.0
> Ghz and SSD OCZ Vertex)
> and running windows Seven.
> Now when I test cygwin, everything is so sloowww
Not ex
> Here are some differences between the terminfo capabilities
> 'rxvt-cygwin-native' and 'Eterm-256color':
>
> 1. max_colors:
> rxvt - max_colors: 8
> Eterm - max_colors: 256
I'd say it's a bug that the rxvt max_colors entry is 8, since rxvt
does support 256 colours in its default setting. (And
> No, when Emacs is run in terminal (text-only, non-X-windows)
> mode, it will use whatever terminal capability is in effect,
> not only in `term-mode'.
Yes, but nevertheless the TERM setting needs to fit the terminal that
Emacs is actually running in, so "rxvt" (or some variation thereof)
for rxv
> I'm using Win2000-SP4, and I've created a shortcut in the quick launch bar
> to start an RXVT terminal with this parameters:
>
> Target: C:\cygwin\bin\rxvt.exe -e bash --login
> Start in: C:\cygwin\bin
>
> The problem is when I click this shortcut, the terminal opens and closes
> immediately
The
>> And then there are rxvt and xterm and their termcap and terminfo
>> entries as well ...
>
> That I don't understand. What have xterm and rxvt terminals to
> do with the "cygwin" terminal type represented by a Windows console?
Nothing, sorry. Erroneous copy & pasting from a previous post.
Andy
Me scribbled:
>>> - When running Cygwin applications in the Windows console window, the
>>> Backspace key now returns ASCII DEL (^?, \177) instead of ASCII BS
>>> (^H, \008). The Control-Backspace key now returns ESC-DEL (^[^?,
>>> \033\177) or \377, dependent on the meta mode set by the set
2009/6/10 Dave Korn:
> Corinna Vinschen wrote:
>
>> What's new in contrast to 1.7.0-48
>> ===
>>
>> - When running Cygwin applications in the Windows console window, the
>> Backspace key now returns ASCII DEL (^?, \177) instead of ASCII BS
>> (^H, \008). The Con
> I have started cygwin-1.7 setup to update to latest cygwin dll and now when
> I start mintty,
> seems are very weird.
> My terminal looks like a mix between a windows terminal and mintty, for
> instance I have the following
> text in black and white :
>
> Microsoft Windows XP [version 5.1.2600]
>
2009/6/9 Vincent R.:
> I already have the minus...
> I have uninstalled and resinstalled mintty but same problem.
> I can also see that start menu shortcut is not created anymore.
Ah, packaging bug, sorry. I forgot to include the postinstall and
preremove scripts. I'll upload a corrected 0.4.0-2 a
2009/6/8 David Arnstein:
> can anyone suggest how to get mousewheel working with
> 1. X11 xterm windows, while at shell prompt.
Not sure that's possible/practical. What would you expect it to do?
> 2. X11 xterm windows, while in vim.
Put this line in ~/.vimrc:
:set mouse=a
Andy
--
Unsubscribe
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
> 2) if the length of the actual pathname to the DLL is more than 2k wide
> characters (e.g. 4k bytes) then issue #1 is made increasingly likely,
Surely anyone with paths like that deserves all the pain that comes
their way. 2k characters means 85 levels of "Documents and Settings".
:)
Andy
--
U
>
> Thomas, couldn't you have discussed this in the two weeks I was on
> vacation? Why did you wait until I implemented the language-based
> approach?
>
Sorry, that's largely my fault. Among a bunch of other MinTTY issues
we were privately discussing various more or less mad schemes to
communic
2009/6/5 Thomas Wolff:
> the locale syntax allows for an optional "modifier" which can be used to
> specify deviations, e.g.
> de_DE has charmap ISO-8859-1
> de...@euro has charmap ISO-8859-15
> uz_UZ has charmap ISO-8859-1
> uz...@cyrillic has
2009/6/5 Ken Brown:
>> I guess what I could do is remove the setting from the dialog and
>> instead make it a config file or command line option only, because
>> it's not really something that users should normally have to worry
>> about.
>
> Does the command line option currently exist?
No. Sorry
Back to the cygwin list, since this is getting off-topic for cygwin-apps.
2009/6/3 Ken Brown:
> On 6/3/2009 10:32 AM, Corinna Vinschen wrote:
On non-English keyboards, the right Alt key is called AltGr and returns
the modifiers Left-Control/Right-Alt.
>>>
>>> So maybe the answer is that
> I think there's a minor bug in the way mintty handles the ^H/^? option for
> the Backspace key. Suppose you have mintty set up so that Backspace sends
> ^H (the default). You then use the options menu to change this so that
> Backspace sends ^?. Then stty -a still shows erase = ^H, and some
>
>> We unfortunately don't have a package of man pages for our C library
>> functions.
>
> Actually the cygwin-doc package does have man pages for much of the C
> standard library.
D'oh, that's what Dave said in the next sentence.
Sorry,
Andy
--
Unsubscribe info: http://cygwin.com/ml/#unsub
>> I couldn't figure this out. What package to install to get
>> man 3 printf ?
Search http://cygwin.com/packages for "printf.3".
> We unfortunately don't have a package of man pages for our C library
> functions.
Actually the cygwin-doc package does have man pages for much of the C
standard li
2009/5/31 Ken Brown:
> As I long-time emacs user, I have to say that I have never been tempted to
> type Ctrl-Backspace in emacs. But, as a result of this discussion, I just
> tried it in three different settings and got three different behaviors.
> (The three settings were: emacs under X, emacs
2009/5/30 Ken Brown:
> Now C-h and Backspace work as expected when I run emacs in a Cygwin console,
> provided I do stty erase ^? first. Am I right in assuming that this won't
> be necessary once the termios default is changed?
Yep.
2009/5/30 Matt Wozniski:
> On Debian, at least, the console se
2009/5/31 Roger Head:
> Thanks for the reply, Matt. I don't have a really good idea of how Cygwin and
> Windows are both supposed to be able to handle .LNKs to e.g. G++, but a dump
> of
> g++.exe.lnk shows strings for /etc/alternatives and
> L:\cygwin\etc\alternatives.
> So yes, I don't know if W
>>The Linux console in Opensuse actually does the same thing, and two's
>>a standard, right? ;)
>
> Actually, no. I emulated the linux console on my system. kterminal and
> xterm also makes no distinction that I can see between CTRL-Backspace
> and Backspace.
As I said, I've seen the ^_ in the t
> One more thing: with your change, Alt can be used to override ^? and
> get ^H instead. Usually though, Ctrl is used as the modifier for this,
> whereas Alt acts as Meta (i.e. it sends a ^[ prefix).
Actually, we could take this one step further. In MinTTY, if Backspace
is set to send ^?, Ctrl+Bac
Christopher Faylor wrote:
>>Now of course if emacs can translate low-level console I/O as it sees
>>fit, then the Cygwin DLL could also be able to translate Backspace into
>>^? characters rather than ^H, in CYGWIN=tty mode anyway. So I had a
>>look at fhandler_console.cc. It already uses ReadCon
>>> Actually, this holy war can be bypassed, without sacrificing Emacs
>>> correctly working on a console. What the console should send for that
>>> is the function key.
>>
>> Makes sense to me. Andy, is there any reason all cygwin terminals shouldn't
>> do this (including mintty)? This already
>> Actually, this holy war can be bypassed, without sacrificing Emacs
>> correctly working on a console. What the console should send for that
>> is the function key.
>
> Makes sense to me. Andy, is there any reason all cygwin terminals shouldn't
> do this (including mintty)? This already happe
> Sorry, I guess I haven't been expressing myself very well. I wasn't
> suggesting any particular course of action, and I certainly don't want to
> break other applications.
No worries. I was just trying to explain why the proper and obvious
fix of switching the backspace defaults to ^? might be
>> Can cygwin terminals be
>> configured so that emacs can tell the difference between the Backspace key
>> and "pressing h while holding down the control key"?
>
> "pressing h while holding down the control key" produces ^H (0x08).
> By default, this is also what backspace sends. As Andy says, ma
Ken Brown:
> A separate issue that has arisen in this thread is that when emacs runs
> in a cygwin terminal [*], it sees C-h as DEL instead of as the help key.
> Can someone familiar with cygwin terminals help with this? I'm speculating
> again (bad habit), but it seems that the keycodes are being
> In an xterm (with TERM=xterm) a few keypad keys do in fact have a (not very
> useful) definition: kp-f1, kp-f2, kp-f3, kp-f4 are (incorrectly) mapped to f1,
> f2, f3, f4 and kp-enter is correctly mapped.
With xterm's default config, F1 to F4 do actually send the keypad
codes ^[OP to ^[OS. That's
> As I understand the emacs documentation, the setting TERM=xterm should cause
> emacs to load term/xterm.el. In that file I find lines like
>
> (define-key map "\eOq" [kp-1])
> (define-key map "\eOr" [kp-2])
>
> This looks like the place where emacs should learn to interpret the keypad
> keys.
x
> Remember, the semantics of fork is that BOTH processes (the parent and
> child) must see the SAME memory, and that includes all shared libraries
> being mapped at the SAME location. But since Windows doesn't provide a
> native fork, the child must remap everything that the parent had, and hope
>
> How should that work? The first half of the surrogate pair has not
> enough information to decide that. For instance, take the ranges
> 0x10A01, 0x10A03 }, { 0x10A05, 0x10A06 }. The information about the low
> 10 bits of the Unicode value is in the second half of the pair. From
> the first ha
2009/5/12 Corinna Vinschen:
>> Trouble is, there's the thorny issue of the "CJK Ambiguous Width"
>> category of characters, which consists of things like Greek and
>> Cyrillic letters as well as line drawing symbols. Those have a width
>> of 1 in Western use, yet with CJK fonts they have a width of
2009/5/8 Corinna Vinschen:
> Unfortunately I got the reply that this issue cannot be addressed this
> time but MSFT will consider addressing the issue in a future version of
> Windows.
Forgot to say: thanks for the update.
> This is really bad.
Yep. And the workaround with ShowWindowAsync() isn'
2009/5/13 Gary Johnson :
>> Cygwin installs to one directory, usually c:\cygwin.
>> You can choose to use it or not. I really don't understand the
>> question. Sorry.
>
> Doesn't setup.exe add entries to the Windows registry as well?
Only a few for Cygwin's own use, e.g. for the mount points (an
> Not necessarily better, but here is a chart:
>
> Sys: App: function expects/returns
> NULL: NULL: UTF-8
> C/UA: NULL: UTF-8
> NULL: C/UA: UTF-8
> C/UA: C/UA: UTF-8
> SPEC: NULL: System Locale
> SPEC: C/UA: UTF-8
> NULL SPEC: Application Locale
> C/UA: SPEC: Application Locale
> - why do you need to touch the filename at all? I haven't read all of it. Is
> the UTF-16 on disk and we need to work around UTF-16 being intractable as C
> string?
Yes. If you simply treated each UTF-16 symbol as two chars, you'd get
unintended NULs and slashes. For starters, the upper halves o
> And here's another question. The utf8*.h files claim they have been
> generated from the unicode.txt file of the Unicode 3.2 standard. Do we
> have the script which generated the utf8*.h files? Can we regenerate
> the files to match the current Unicode 5.1 standard?
There's Markus Kuhn's wcwi
> I am going to present the seminar on Cygwin in my organization.In that
> seminar I want to show you can access windows shared folder of any PC
> from Cygwin. To demonstrate that I have tried to mount that windows
> shared folder in cygwin but it didn't work. When I have searched in
> google for i
2009/5/7 Georg Nikodym:
>
> On 7-May-09, at 10:56 AM, Kyeto wrote:
>
>> I have disabled DEP and now Cygwin run.
>> But i have just the pompt with :
>> bash-3.2$ : _
>>
>> None commands are available
>> When i do a "ls" => command not found.
>> It's the same for a lot (touch, chmod ...)
>>
>> But
> By the way, I don't like that setup maximizes the window when on the package
> selection step.
I haven't seen it, but it certainly sounds wrong for a "wizard"-style
window to change its size when you press the Next button.
> An option somewhere to disable it would be nice. :)
No, it wouldn't.
> There is now a Cygwin related newsgroup alt.comp.cygwin on mainstream usenet
> for
> anarchists, lunatics, and terrorists. This group is available on usenet for
> access using a conventional newsreader.
>
> If this group is not listed on your usenet server, and you require access to
> this group
> I have installed both versions of cygwin 1.5 and 1.7.
> Both seem to work fine with Xserver from 1.5 or 1.7 (i.e. cygwin 1.5
> works fine with Xwin from 1.5 and 1.7, cygwin 1.7 works fine with Xwin
> from 1.5 and 1.7).
> Any recommendation on which one to use?
The 1.7 one, to help testing it. ;)
Gus K:
> I installed the X server and i get an xterm window
> I type emacs& but emacs doesnt start
You've started the terminal version of emacs, which just stays quiet
if you put it into the background with '&'. Just omit the '&'.
(Or, as Ken said, install the X version of emacs and invoke it as
2009/5/1 Barry Kelly:
>> ReadConsoleOutput() on the hidden console only
>> gives you the cooked output in terms of character cell contents and
>> attributes, whereas the raw output as it came from the console app
>> would need to be sent to the pty to be displayed by the likes of
>> screen. As far
2009/4/21 Barry Kelly:
> Windows implements console mode as a client-server protocol between the
> executable (ntvdm.exe for DOS apps) and winsrv.dll (hosted in
> csrss.exe), but the protocol isn't easily hookable. I guess one would
> have to hijack the console APIs, perhaps by stepping into the
>
> This means either installing Cygwin in the root directory of the drive
> that you'll commonly be working in with both Windows and Cygwin tools
Speaking of which, it would be nice if setup.exe warned about doing
this only once when you first decide to install in the root directory.
Currently it w
MinTTY is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Its terminal emulation is largely
compatible with xterm, but it does not require an X server to be
running. It is based on code from PuTTY 0.60 by Simon Tatham and team.
This update fixes a couple
2009/4/29 Phil Betts:
> Charles Wilson wrote:
>> * Add -uas (--unixAltSpace) option to bypass Win32 handling
>> of Alt-Space key combination, and allow client (e.g.
>> Emacs) to handle it instead.
>
> Thanks for this Chuck.
>
> I can't see what in my previous post got you so worked up
The word
> This update contains a number of bugfixes that had accumulated during
> development for mintty-0.4. (Btw, 0.4-beta2 is available for download
> from the MinTTY project page.)
>
> CHANGES (since 0.3.8-1)
> ===
...
> - UTF-8 and other codepages are supported for the window title
2009/4/27 Vincent R.
> on unix terminals when I press CTRL + RIGHT_KEY or CTRL+LEFT_KEY, cursor
> move from one word to another
> which is very handy.
> It doesn't work on mintty and I am sad about it ... ;-)
You'll need to configure that behaviour in ~/.inputrc, the config file
for the readline l
> o Use cygutils to create shortcuts in Start Menu
I'm afraid the shortcuts don't work, because they have a rogue
backslash and newline in the target:
C:\bin\run.exe /usr/bin/rxvt.exe -display :0 -fn "Lucida Console-14" \
-tn rxvt-cygwin-native -e /bin/bash --login
C:\bin\run.exe /usr/bi
MinTTY is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Its terminal emulation is largely
compatible with xterm, but it does not require an X server to be
running. It is based on code from PuTTY 0.60 by Simon Tatham and team.
This update contains a numb
2009/4/24 Thomas Wolff>:
> Also (I know I asked this already 1 or 2 years ago...) do you see
> any chance now to combine the stand-alone feature (libW11...) with
> rxvt-unicode? (Maybe it's a new challenge for someone now that cygwin
> introduced native Unicode support)
You might want to give Min
> The loss of the POSIX permissions is fine for me. But what is then the
> purpose of tty in the CYGWIN variable?
Better Unix terminal emulation in the Cygwin console, but with the
drawback that many interactive Windows console apps won't work
correctly.
Andy
--
Unsubscribe info: http://cyg
Xterm supports an OSC sequence for accessing the clipboard/selection.
I don't know whether vim or emacs have support for this though. From
http://invisible-island.net/xterm/ctlseqs/ctlseqs.html:
OSC P s ; P t BEL
...
P s = 5 2 → Manipulate Selection Data. These controls may be disabled
using the a
> Maybe someone knows a solution to this, but I don't. Although I maintain
> screen
> for Cygwin, I know almost nothing of the details of how terminals work. I
> could
> imagine some kind of a DOS-to-Unix terminal wrapper program, but I've never
> seen one and have no idea how it would work.
I
2009/4/16 Corinna Vinschen:
>> This little test opens a console window on
>> 7, but not Vista, when compiled with 'gcc -mno-cygwin -mwindows'.
>>
>> int
>> main(void)
>> {
>> HWINSTA wst = CreateWindowStation (0, 0, WINSTA_ALL_ACCESS, 0);
>> SetProcessWindowStation(wst);
>> AllocConsole();
>>
Corinna Vinschen:
> If the above code also allocs a console window when run from a non-cygwin
> (mingw) application, then this should be reported as a bug to Microsoft.
I can confirm this one now. This little test opens a console window on
7, but not Vista, when compiled with 'gcc -mno-cygwin -mwi
Corinna Vinschen:
> Treat it as a bug in Windows 7, probably. Do you get the console window
> as soon as you call AllocConsole, or does it open later?
It opens when invoking AllocConsole(). If I take out both the
AllocConsole() and the execve(), no console is opened.
> If so, it could also be t
>> Letters in an error message don't just randomly change between upper and
>> lower case for no reason.
>
> It just prints argv[0], so if you invoke it as GREP it will report as
> GREP, thanks to case insensivity.
ps: Sorry, of course that doesn't account for "Memory Exhausted" being
uppercase.
801 - 900 of 1001 matches
Mail list logo
