Re: More robust color terminal
On Jun 25 00:40, Igor Pechtchanski wrote: On Sat, 25 Jun 2005, Dave Hughes wrote: I can understand the rationale behind wanting to package gvim separately to vim (allows for people who want vim, but don't want X). Well, gvim is kinda special. You might want to compile it with both the X11 libraries and W11 libraries from rxvt, to allow people to run windowed gvim without X. I don't know how easy or hard it is, just a thought. YMMV, but I think it's ok if gvim is a pure X application, residing in /usr/X11R6/bin. If you don't have X, just start vim in another local rxvt window and you're all set. However, they're basically the same app. Would it make sense for a gvim package to include just the gvim binary, and have a dependency on the main vim package to provide the runtime files (syntax highlighting configs and such like)? Definitely yes. It would make even more sense to split the vim package into the base editor and the runtime support files. Corinna Vinschen, who, in addition to being the Cygwin project co-leader, also maintains quite a few packages (including vim), has repeatedly expressed desire to hand off some of her packages. Don't know if vim is one of them, but it doesn't hurt to ask. If you take over vim (provided Corinna agrees), you can handle the proper repackaging easily enough. I have no ambition to split the vim package. As long as I'm vim maintainer, I'd rather have gvim just being a binary package using the vim source package and having a dependency to the vim package as a whole. Talking about maintainership, vim isn't exactly tricky to maintain, so I never thought about passing it on. But if you really want to take over, feel free. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/
gvim packaging (Was Re: More robust color terminal)
On Sat, 25 Jun 2005, Corinna Vinschen wrote: On Jun 25 00:40, Igor Pechtchanski wrote: On Sat, 25 Jun 2005, Dave Hughes wrote: I can understand the rationale behind wanting to package gvim separately to vim (allows for people who want vim, but don't want X). Well, gvim is kinda special. You might want to compile it with both the X11 libraries and W11 libraries from rxvt, to allow people to run windowed gvim without X. I don't know how easy or hard it is, just a thought. YMMV, but I think it's ok if gvim is a pure X application, residing in /usr/X11R6/bin. If you don't have X, just start vim in another local rxvt window and you're all set. By the same token, if you *do* have X, just start vim in a local xterm window, and you're all set. I personally don't use gvim, but, as I understand, it has more features than a console-mode vim (e.g., menus, fonts, etc, etc). So far, the only Cygwin-aware editor with a native windowed mode is xemacs -- IMO, it's high time for vim to get there. However, they're basically the same app. Would it make sense for a gvim package to include just the gvim binary, and have a dependency on the main vim package to provide the runtime files (syntax highlighting configs and such like)? Definitely yes. It would make even more sense to split the vim package into the base editor and the runtime support files. Corinna Vinschen, who, in addition to being the Cygwin project co-leader, also maintains quite a few packages (including vim), has repeatedly expressed desire to hand off some of her packages. Don't know if vim is one of them, but it doesn't hurt to ask. If you take over vim (provided Corinna agrees), you can handle the proper repackaging easily enough. I have no ambition to split the vim package. As long as I'm vim maintainer, I'd rather have gvim just being a binary package using the vim source package and having a dependency to the vim package as a whole. Talking about maintainership, vim isn't exactly tricky to maintain, so I never thought about passing it on. But if you really want to take over, feel free. One (not very compelling) reason for such a split is that the runtime files could then be updated on a different schedule. Another is that if gvim is compiled with native windowed mode, it'll need a different build script, and (partly) a different source (though, of course, these modifications could be made on the common source as well). If we get a gvim maintainer, it might be easier to have him also maintain vim, rather than coordinate. But all of the above are just suggestions, however -- it's really up to you as the vim maintainer to decide what to do. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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: More robust color terminal
Igor Pechtchanski wrote: On Fri, 24 Jun 2005, Reid Thompson wrote: Gary R. Van Sickle wrote: Both rxvt and the cmd.exe window only support 16 colors. Welcome to 1983. I at least hope they include those horrid CGA colors. -- Gary R. Van Sickle recompiling rxvt for 256 colors is not hard. $ ./rxvt -help |head Rxvt v2.7.10 - released: 26 MARCH 2003 Options: XPM,transparent,utmp,menubar,multichar_languages,scrollbars=rxvt+NeXT+xterm,frills,linespace,256colour,.Xdefaults Ah, I knew I saw something about rxvt supporting 256 colors somewhere. The man page is misleading, apparently. Any idea why the current release doesn't use 256 colors? Igor P.S. Don't you mean rxvt -help 21 | head? Rxvt's help goes to stderr. LOL -- yeah -- i just selected the top portion to paste when it bypassed head. -- 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: More robust color terminal
On Thu, 23 Jun 2005, Laran Evans wrote: So, I'm working with 8 colors in my rxvt terminal. It seems that's all that's available. Where this really becomes a drag is when trying to apply different color themes in Vim. Most light colored themes all look the same, with colors reducing to the 8 available. So, my question is this: Can I use some different option to get a more robust color terminal? My Cygwin.bat currently looks like this: @echo off C: chdir C:\Cygwin\bin C:\Cygwin\bin\rxvt.exe -e bash --login -i Any suggestions? Both rxvt and the cmd.exe window only support 16 colors. I guess you could run X and use an xterm (which should support 256 colors, IIRC). Alternatively, you could compile (and, hopefully, contribute) gvim. :-) Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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: More robust color terminal
Alternatively, you could compile (and, hopefully, contribute) gvim.
:-) Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`'-. ;-;;,_ [EMAIL PROTECTED]
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
vim6.3 compiles ootb for X.
$ ls -lrt /usr/local/bin/*vim*
lrwxrwxrwx 1 Reid.Thompson Domain Users 7 Dec 16 2004
/usr/local/bin/gvim - vim.exe
lrwxrwxrwx 1 Reid.Thompson Domain Users 7 Dec 16 2004
/usr/local/bin/evim - vim.exe
lrwxrwxrwx 1 Reid.Thompson Domain Users 7 Dec 16 2004
/usr/local/bin/gvimdiff - vim.exe
lrwxrwxrwx 1 Reid.Thompson Domain Users 7 Mar 3 08:27
/usr/local/bin/vimdiff - vim.exe
-rwxr-xr-x 1 Reid.Thompson Domain Users 1273856 Jun 13 12:01
/usr/local/bin/vim.exe
-rwxr-xr-x 1 Reid.Thompson Domain Users1600 Jun 13 12:02
/usr/local/bin/vimtutor
not the cleanest way to handle it i'm sure, but. in .bashrc ( i have
both cygwin compiled *vim and native *vim on my machine, if X is
running, use cygwin gvim, else use native gvim, or use 'vim' instead of
'vi' from command line to get non-gui)
HAVEX=`ps -ef | grep XWin`
if [ $HAVEX != ]
then
HAVEX=1
export HAVEX
fi
alias vi='dovi'
function dovi {
if [ ! $HAVEX ]
then
if [ $1 != ]
then
value=`cygpath -w $*`
/C/Vim/vim62/gvim $value
else
/C/Vim/vim62/gvim $*
fi
else
if [ $1 != ]
then
value=`cygpath -w $*`
/usr/local/bin/gvim $value
else
/usr/local/bin/gvim $*
fi
fi
}
reid
--
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: More robust color terminal
Both rxvt and the cmd.exe window only support 16 colors. Welcome to 1983. I at least hope they include those horrid CGA colors. -- Gary R. Van Sickle -- 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: More robust color terminal
Gary R. Van Sickle wrote: Both rxvt and the cmd.exe window only support 16 colors. Welcome to 1983. I at least hope they include those horrid CGA colors. -- Gary R. Van Sickle recompiling rxvt for 256 colors is not hard. $ ./rxvt -help |head Rxvt v2.7.10 - released: 26 MARCH 2003 Options: XPM,transparent,utmp,menubar,multichar_languages,scrollbars=rxvt+NeXT+xt erm,frills,linespace,256colour,.Xdefaults reid -- 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: More robust color terminal
On Fri, 24 Jun 2005, Reid Thompson wrote: Gary R. Van Sickle wrote: Both rxvt and the cmd.exe window only support 16 colors. Welcome to 1983. I at least hope they include those horrid CGA colors. -- Gary R. Van Sickle recompiling rxvt for 256 colors is not hard. $ ./rxvt -help |head Rxvt v2.7.10 - released: 26 MARCH 2003 Options: XPM,transparent,utmp,menubar,multichar_languages,scrollbars=rxvt+NeXT+xterm,frills,linespace,256colour,.Xdefaults Ah, I knew I saw something about rxvt supporting 256 colors somewhere. The man page is misleading, apparently. Any idea why the current release doesn't use 256 colors? Igor P.S. Don't you mean rxvt -help 21 | head? Rxvt's help goes to stderr. -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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: More robust color terminal
On Fri, June 24, 2005 15:45, Igor Pechtchanski said: On Thu, 23 Jun 2005, Laran Evans wrote: [snip] Any suggestions? Both rxvt and the cmd.exe window only support 16 colors. I guess you could run X and use an xterm (which should support 256 colors, IIRC). Alternatively, you could compile (and, hopefully, contribute) gvim. :-) I vaguely recall trying to build gvim on Cygwin some time ago (and failing) but, as Reid Thompson pointed out elsewhere in this thread, gvim builds OOTB now. I've just tried this and it works like a charm (no special configure switches or anything, just a straight pull from CVS of the latest source, hit make and let it go)! Spent an hour hacking around some Python in gvim (GTK GUI) under Cygwin and found not one single problem. Very nice :-) Hopefully I'm not rushing headlong into this, but I've just skimmed through the Package Contributor's Guide and I think I might be able to put together a package for gvim (and, if building it stays this easy, maintain it). A few thoughts occurred though, and I just wanted to check I'm not completely mad (which is a distinct possibility at this time of the morning): I can understand the rationale behind wanting to package gvim separately to vim (allows for people who want vim, but don't want X). However, they're basically the same app. Would it make sense for a gvim package to include just the gvim binary, and have a dependency on the main vim package to provide the runtime files (syntax highlighting configs and such like)? If that's the case, it also sounds like the gvim package wouldn't include a src package but would use the external-source directive in the setup.hint to point at the vim package's sources. Or am I talking crazy talk? Anyway, I'll have a look at the natty package build-script tomorrow and see if I can't come up with something ... but right now I've got to catch up on a week of sleep deprivation :-) -- Dave Hughes -- 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: More robust color terminal
On Sat, 25 Jun 2005, Dave Hughes wrote: On Fri, June 24, 2005 15:45, Igor Pechtchanski said: On Thu, 23 Jun 2005, Laran Evans wrote: [snip] Any suggestions? Both rxvt and the cmd.exe window only support 16 colors. I guess you could run X and use an xterm (which should support 256 colors, IIRC). This should really say currently only support 16 colors, in light of Reid's message about recompiling rxvt... Alternatively, you could compile (and, hopefully, contribute) gvim. :-) I vaguely recall trying to build gvim on Cygwin some time ago (and failing) but, as Reid Thompson pointed out elsewhere in this thread, gvim builds OOTB now. I've just tried this and it works like a charm (no special configure switches or anything, just a straight pull from CVS of the latest source, hit make and let it go)! Spent an hour hacking around some Python in gvim (GTK GUI) under Cygwin and found not one single problem. Very nice :-) Hopefully I'm not rushing headlong into this, but I've just skimmed through the Package Contributor's Guide and I think I might be able to put together a package for gvim (and, if building it stays this easy, maintain it). That's great. A few thoughts occurred though, and I just wanted to check I'm not completely mad (which is a distinct possibility at this time of the morning): I can understand the rationale behind wanting to package gvim separately to vim (allows for people who want vim, but don't want X). Well, gvim is kinda special. You might want to compile it with both the X11 libraries and W11 libraries from rxvt, to allow people to run windowed gvim without X. I don't know how easy or hard it is, just a thought. However, they're basically the same app. Would it make sense for a gvim package to include just the gvim binary, and have a dependency on the main vim package to provide the runtime files (syntax highlighting configs and such like)? Definitely yes. It would make even more sense to split the vim package into the base editor and the runtime support files. Corinna Vinschen, who, in addition to being the Cygwin project co-leader, also maintains quite a few packages (including vim), has repeatedly expressed desire to hand off some of her packages. Don't know if vim is one of them, but it doesn't hurt to ask. If you take over vim (provided Corinna agrees), you can handle the proper repackaging easily enough. If that's the case, it also sounds like the gvim package wouldn't include a src package but would use the external-source directive in the setup.hint to point at the vim package's sources. Or am I talking crazy talk? No, that sounds about right. You'd need to coordinate with the vim maintainer for this, though, since the vim build script won't actually produce the gvim binary package. You could also provide the gvim build script as the sole file in the source package, and simply require the vim source to be present... Anyway, I'll have a look at the natty package build-script tomorrow and see if I can't come up with something ... but right now I've got to catch up on a week of sleep deprivation :-) Good luck. Don't forget, the generic-build-script is designed to be edited to adjust it for each package. FWIW, if you find yourself making changes that would make the g-b-s more configurable, please consider submitting a patch to the cygwin-apps list. Incidentally, if you intend to maintain a package, you'll need to subscribe to the cygwin-apps list. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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/
