From: Keith M. <kei...@to...> - 2007-03-28 09:37:31
|
[I'm cross posting to MinGW-MSYS, as this seems more applicable to users of that list, and I want their opinions. Nevertheless, I still value the opinions of the MinGW-users community. If you receive two copies because you subscribe to both lists, please accept my apologies; (I'll only count your vote once though, if it's obvious that you've replied more than once :-) )] Brian Dessent wrote, quoting me: >> I considered this, a few months ago. I could never get the development >> versions of console-2 to run on my Win2K box -- needed DLLs which are >> not present as part of the core OS. The released version runs, but I >> don't really see any advantage over the standard Win32 console. > > One of the main advantages to me is that the stock console only lets you > use a small number of fonts (a handful of fixed point sizes and Lucida > Console) whereas the Console-2 app lets you pick any installed font, > fixed or TrueType, in any size. And the tabbed interface, etc... Yeah, fonts are limited in standard Win32 console. I don't see that as a problem. Lucida Console seems quite acceptable to me as a console font; I don't need anything more, but clearly that's a personal choice. Tabbed interface? I don't see it in console-1.5; I haven't tried again recently, but when I did, I couldn't get console-2 to run. Shame, because that's an advantage I would appreciate. >> I use MSYS daily, since v1.0.8, and I've not used RXVT *ever*; (it's >> just too flaky for my needs). Just delete rxvt.exe from your MSYS /bin >> directory, or start with the --norxvt switch for v1.0.11, and it will >> start in a standard Win32 console. > > How about in the next release of MSYS reversing the sense of the test, > in other words, you must supply --rxvt otherwise you get the stock > console. It seems to be more headache than help at this point. That makes sense to me, but Earnie was always keen to promote RXVT; I agree that the more stable behaviour without RXVT is preferable. What do other users think; should I make this change, for Cesar's upcoming MSYS-1.0.11 release? Votes please! Regards, Keith. |
From: Curt S. <c.s...@ie...> - 2007-03-29 12:46:05
|
Keith MARSHALL <kei...@to...> wrote: >> How about in the next release of MSYS reversing the sense of the test, >> in other words, you must supply --rxvt otherwise you get the stock >> console. It seems to be more headache than help at this point. >> > > That makes sense to me, but Earnie was always keen to promote RXVT; I > agree that the more stable behaviour without RXVT is preferable. What > do other users think; should I make this change, for Cesar's upcoming > MSYS-1.0.11 release? Votes please! > > Regards, > Keith. > Yes, please make RXVT an option, instead of the default. |
From: Greg C. <chi...@co...> - 2007-03-28 11:47:10
|
On 2007-3-28 9:34 UTC, Keith MARSHALL wrote: > > Votes please! Yes. Favor stability. By default, don't use rxvt. |
From: Rich <rm...@ya...> - 2007-03-29 16:34:59
|
Keith MARSHALL wrote: > ........ > That makes sense to me, but Earnie was always keen to promote RXVT; I > agree that the more stable behaviour without RXVT is preferable. What > do other users think; should I make this change, for Cesar's upcoming > MSYS-1.0.11 release? Votes please! > > Regards, > Keith. While I do prefer RXVT because I've used Xterms for years, I do find that I must reluctantly use the CMD/Bash window to test my interactive C programs. I've not done any builds to date, but it is my understanding that some packages will not build in the RXVT window which I feel is the most compelling reason to consider making the CMD/Bash window the default. What I have to say about the CMD/Bash window probably should be in a thread of it's own. I'd be more inclined to use the CMD/Bash window by default if I could make it "better". By default, the CMD window with Bash that gets launched looks a lot like the ugly Command Prompt window launched from Windoze. I've recently begun playing around with the desktop shortcut for MSYS and the msys.bat file to get something that I find a bit more pleasing and functional. I'll have to go back through the archives to find the previous discussions on the topics of Mouse or Keyboard Selection, Cut and Paste of text in the CMD/Bash window as none of those functions seem to work for me at this time. I just feel that if the CMD/Bash window is launched by default instead of RXVT, then we as users need some configuration options so we can get a more useful or pleasing CMD/Bash window. Rich Simoes |
From: Keith M. <kei...@to...> - 2007-03-30 10:48:30
|
Rich Simoes wrote: > I just feel that if the CMD/Bash window is launched by > default instead of RXVT, then we as users need some > configuration options so we can get a more useful or > pleasing CMD/Bash window. FWIW, I agree with you that the *default* configuration of the native Woe32 console is just downright ugly. It doesn't have to be that way; here's how I set mine up in Win2K:-- 1) Open the properties dialogue of the shortcut which starts the MSYS session, and add the `--norxvt' flag to the command line used to start the session, (for Win2K, it's in the field tagged as `Target:' on the `Shortcut' tab). If you are still using MSYS-1.0.10, you may need to update your MSYS.BAT file, to get support for the `--norxvt' flag; grab the latest version from CVS: http://mingw.cvs.sourceforge.net/mingw/msys/dvlpr/bin/msys.bat or rename MSYS' /bin/rxvt.exe to /bin/rxvt.no, to permanently, (but reversibly), disable it. The remaining steps may also be completed in this same properties dialogue window, but I've found it more reliable to apply and quit the properties update, then start a session in the native console, right-click on the window title bar, reopen the properties dialogue from the context menu, and proceed from there; YMMV. 2) On the `Options' tab, select `Window' for the `Display options' property, and enable *both* `Quick Edit mode' and `Insert mode' for the `Edit options'. Set the `Cursor size' property as you prefer it, (I set mine to `Small'), and leave the defaults for the `Command history' property. 3) On the `Font' tab, select a font and font-size with which you feel comfortable; on my 17in monitor at 1280x1024 resolution, I find `Lucida Console' at size 14 suits me. 4) On the `Layout' tab, adjust the `Window size' settings to get the window size to fill whatever area of the screen you like. I've set mine with a `Width' of 180 and a `Height' of 80, to make the window fill my entire screen; you may have to tweak these, to suit your own preference or screen resolution. After you've set your preferred `Window size', you should adjust the `Screen buffer size' properties, to establish the scroll buffer; I find that keeping `Screen buffer size.Width' the same as `Window size.Width' works best, and I have the `Height' for `Screen buffer size' set to 300, to give me 300 lines of scrollable history. Set the `Window position' property to your own preference; I have mine with `Left' at -3, `Top' at -2, and I've disabled the `Let system position window' option. 5) On the `Colors' tab, activate the `Screen Background' property; select the leftmost slot in the colour pallette, and adjust the RGB fields of the `Selected Color Values' property, to achieve a background colour to your liking, (mine is RGB 255/255/192, which gives me a pale cream). After making the final RGB field adjustment, left-click in another RGB field, *without* making any further change, otherwise your final change may not be committed. Activate the `Screen Text' property, select the second palette slot from the left, and select appropriate RGB values for the `Selected Color Values' property; this selection will relate to the text colour mapped to the `ESC[31m' SGR sequence. Again, click in another RGB field, after the last adjustment. Repeat, selecting each of the remaining palette slots from left to right. Ensure that the colour in the eighth slot from the left is how you want your normal text to appear; also, if you use `man' or `nroff', be aware that the fourth and sixth colours from the left will be substituted for underlined and heading (bold) text respectively. Finally, select the eighth colour slot from the left, as the normal setting for the `Screen Text' property. Note: I haven't discovered the purpose of the `Popup Text' and `Popup Background' properties, but it does no harm to activate each of them, and select a suitable colour for each, from the palette you just defined for the `Screen Text' property; there is no need to adjust that palette any further--just select the colour slots you want to assign. 6) Select `Ok', and then the `Save properties for future windows with same title' option, `Ok' that, and you are done. > I'll have to go back through the archives > to find the previous discussions on the topics of Mouse > or Keyboard Selection, Cut and Paste of text in the > CMD/Bash window as none of those functions seem to work > for me at this time. It appears that you have not enabled the `Quick Edit mode' and `Insert mode' options, as described in (2) above. Do note that the behaviour is not identical to RXVT's; you must:-- a) Drag the mouse, with left button depressed, to mark a selection. b) Right click *once*, to copy the selection to the clipboard. c) Right click *again*, to paste at the cursor in *any* console window, or use Ctrl-V to paste in any non-console window. d) Repeat (c) as many times as you wish, for multiple copies of the same selection. e) Repeat from (a), for a new selection. HTH. I'll try to find time to publish some of the info from this thread on the Wiki, if no one beats me to it. Regards, Keith. |
From: Rich <rm...@ya...> - 2007-04-03 20:58:08
|
Keith MARSHALL wrote: > > 1) Open the properties dialogue of the shortcut which starts > > 2) On the `Options' tab, select `Window' for the `Display options' > > 3) On the `Font' tab, select a font and font-size with which you > > 4) On the `Layout' tab, adjust the `Window size' settings to get > > 5) On the `Colors' tab, activate the `Screen Background' property; > > 6) Select `Ok', and then the `Save properties for future windows > with same title' option, `Ok' that, and you are done. Keith, Thanks for taking the time to give me a very detailed answer. I tried some of your suggestions and I got a better text font and some mouse functionality. (Not bad.) If I understand your description of configuring the properties in the Console window, I limited my configuring to the MSYS desktop shortcut. I have a shortcut that runs a RXVT/BASH window and a separate one that runs the CMD/BASH window. I had modified my msys.bat file sometime ago for the --norxvt option. I also had to remove the "start" command from the line that launches the CMD/BASH window because the start command spawns a second CMD window and none of customization of the desktop shortcut got passed to the second CMD window. I'll experiment some more, but I'm happy with this step forward. Thanks for your help. Rich Simoes |