On Nov 11, 2007 1:24 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Matthew Wozniski wrote:
Now that 88 and 256 color terminals are so ubiquitous, I find it
frustrating that very few colorschemes support 256 color terminals.
Unfortunately, writing a colorscheme that properly supports
On Mon, Nov 12, 2007 at 02:56:24AM -0500, Matthew Wozniski wrote:
Do all the terminals supporting 88 and 256 colors really use the same
color values?
Well... As far as I can tell, they seem to _default_ to the same
values. In the interest of researching this properly, I've
Nikolai Weibull wrote:
[...]
It would be even better if the best approximation of a color could be
found and used. That is, if I specify a color of #fe, Vim should
be able to determine that #ff is the best match.
BTW: I have read that there is a set of 216 colors which are safe to
On Nov 12, 2007 4:29 AM, Gautam Iyer [EMAIL PROTECTED] wrote:
On Mon, Nov 12, 2007 at 02:56:24AM -0500, Matthew Wozniski wrote:
Do all the terminals supporting 88 and 256 colors really use the same
color values?
Well... As far as I can tell, they seem to _default_ to the same
echo glob('~/{,}')
/home/user//
/home/user//
The bug is that an extra slash is added at the end. It's only a
minory issue, as slashes are usually folded by the OS anyway, but it
would be better if they weren't added.
Another issue is that there's doesn't seem to be a way to escape a
comma
Hi,
Another issue is that there's doesn't seem to be a way to escape a
comma inside a brace expansion. Neither two commas in a row or a
backslash seem to generate a comma.
glob behaves depending on your shell settings. Out of my experience,
best is csh or tcsh, where glob works reliably.
On Nov 12, 2007 3:09 PM, Vladimir Marek [EMAIL PROTECTED] wrote:
Another issue is that there's doesn't seem to be a way to escape a
comma inside a brace expansion. Neither two commas in a row or a
backslash seem to generate a comma.
glob behaves depending on your shell settings. Out of
On Nov 12, 2007 3:36 PM, Vladimir Marek [EMAIL PROTECTED] wrote:
Another issue is that there's doesn't seem to be a way to escape a
comma inside a brace expansion. Neither two commas in a row or a
backslash seem to generate a comma.
glob behaves depending on your shell settings.
On Nov 12, 2007 3:40 PM, Matt Wozniski [EMAIL PROTECTED] wrote:
On Nov 12, 2007 9:16 AM, Nikolai Weibull [EMAIL PROTECTED] wrote:
On Nov 12, 2007 3:09 PM, Vladimir Marek [EMAIL PROTECTED] wrote:
Another issue is that there's doesn't seem to be a way to escape a
comma inside a
On Nov 12, 2007 9:42 AM, Nikolai Weibull [EMAIL PROTECTED] wrote:
Either way, there's no way to escape a comma inside braces.
:echo glob('/tmp/{a,b\\054c}')
That works for shell=/bin/zsh and shell=/bin/tcsh for me, though not
for shell=/bin/bash. While I agree that you ought to be able to
:set shell=/bin/tcsh
:echo glob(a 'b/*)
- a 'b/file
:set shell=/bin/bash
:echo glob(a 'b/*)
- a
[...]
Uh. That's horrible. It's a pain that whenever you do any kind of
VimScripting you always have to cover all your bases. It's getting to
become unmanageable.
Personally I would
On Nov 12, 2007 9:56 AM, Vladimir Marek [EMAIL PROTECTED] wrote:
Personally I would like to see something like glob_internal() which
would do globbing entirely in c without accessing your shell. But I'm
not going to write the patch, so I just silently hope :) Or having
readdir to be able to
On Mon, Nov 12, 2007 at 05:41:12AM -0500, Matt Wozniski wrote:
Do all the terminals supporting 88 and 256 colors really use the same
color values?
Well... As far as I can tell, they seem to _default_ to the same
values. In the interest of researching this properly, I've
On Nov 12, 2007 8:42 PM, Gautam Iyer [EMAIL PROTECTED] wrote:
Finally, t_Co is a bad measure. If you're not running xterm, t_Co is
read directly from your termcap / terminfo files. The default terminfo
files shipped with most distributions sets it to 8 colors. The user has
to tweak a little
Nikolai Weibull wrote:
echo glob('~/{,}')
/home/user//
/home/user//
The bug is that an extra slash is added at the end. It's only a
minory issue, as slashes are usually folded by the OS anyway, but it
would be better if they weren't added.
Yes, it's strange that the extra {} results
On Mon, Nov 12, 2007 at 10:23:09PM +0100, Nikolai Weibull wrote:
Finally, t_Co is a bad measure. If you're not running xterm, t_Co is
read directly from your termcap / terminfo files. The default terminfo
files shipped with most distributions sets it to 8 colors. The user has
to tweak a
dickey wrote:
Bram Moolenaar wrote:
Do all the terminals supporting 88 and 256 colors really use the same
color values?
[snip]
Like konsole, it uses (even) more memory but comes with prettier
menus.
Konsole seems to support 16777216 colors.
$ echo -e '\e[38;2;128;160;128mhello\e[0m' #
Zvi Har'El wrote:
I don't think it is worth the trouble insisting to pass % to an external
command instead of passing %.
The big plus here is much less typing:
comparing :e %CR vs :e %CR gives
5 vs 7 characters to type.
Maybe some modifier might be added to % to make
it usable in or ''. I
18 matches
Mail list logo
