possible bug?

possible bug?

[Glenn Trigg]

Hi,

I have discovered an annoying quirk in zsh-3.0.6 (at least it's annoying for
me - an ex-tcsh user).

When I use backward-delete-word it appears to completely ignore the
$WORDCHARS variable. Vis:

ozpc92 >echo $WORDCHARS 
*?_-.[]~=/&;!#$%^(){}<>
ozpc92 >cd /usr/local/etc

typing \M-^H here results in

ozpc92 >cd 

instead of the expected (desired):


ozpc92 >cd /usr/local

Am I missing something?

Please CC any responses to my email address as I'm not subscribed to this
list.

Regards,

Glenn Trigg

Re: possible bug?

[Bart Schaefer]

On Sep 17,  8:59am, Glenn Trigg wrote:
} Subject: possible bug?
}
} When I use backward-delete-word it appears to completely ignore the
} $WORDCHARS variable.

Wordchars are the non-alphanumeric characters that *ARE* considered to be
part of a word.  If you want it to stop at slashes, you have to reset the
value of WORDCHARS to *not* include a slash character.

Either that, or use vi-backward-kill-word instead of backward-kill-word.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Re: possible bug?

[Glenn Trigg]

"Bart Schaefer" <schaefer@candle.brasslantern.com> said :

> On Sep 17,  8:59am, Glenn Trigg wrote:
> } Subject: possible bug?
> }
> } When I use backward-delete-word it appears to completely ignore the
> } $WORDCHARS variable.
> 
> Wordchars are the non-alphanumeric characters that *ARE* considered to be
> part of a word.  If you want it to stop at slashes, you have to reset the
> value of WORDCHARS to *not* include a slash character.

Whoops, I got that round the wrong way, didn't I? Yep, taking the / out of
that variable makes me very happy! :-)

Thanks for your quick reply.

Glenn

Possible bug?

[Mike Perez]

Well I am not sure if this is a bug or not, but I was able to reproduce
it on a few machines that all were in Y2K.

It has to do with the RPROMPT variable and strftime, I believe.

I have my RPROMPT set like this:

PROMPT='%n@%m: %~%(#.#.>) '
RPROMPT='[%D{%b %d, %G} / %t]'

And on the prompt, it displays this:

mike@mindcrime: ~>                            [Jan 01, 1999 / 3:04AM]

But date says this:

Sat Jan  1 03:04:42 PST 2000

- Mike

--
Mike Perez <mike@ef.net>
PGP fingerprint = 66 BF C5 DE 78 C6 01 63  76 D9 BF E7 70 24 55 50
"The difference between insanity and genius is only measured by success."

Re: Possible bug?

[pollux]

>>> "Mike" == Mike Perez <mike@ef.net> writes:

[...]

 Mike> RPROMPT='[%D{%b %d, %G} / %t]'
 Mike> And on the prompt, it displays this:
 Mike> mike@mindcrime: ~>                            [Jan 01, 1999 / 3:04AM]
 Mike> But date says this:
 Mike> Sat Jan  1 03:04:42 PST 2000

Since the ISO week is 52, %G is still saying 1999, wich is right.

       %G     The ISO 8601 year with century as a decimal number.
              The 4-digit year corresponding to the ISO week num­
              ber  (see  %V).  This has the same format and value
              as %y, except that if the ISO week  number  belongs
              to  the  previous  or  next year, that year is used
              instead.

You may want to use %Y instead.

 Mike> - Mike

-- 
Alexandre Duret-Lutz

Re: Possible bug?

[Zefram]

Mike Perez wrote:
>Well I am not sure if this is a bug or not, but I was able to reproduce
>it on a few machines that all were in Y2K.

I can reproduce it too:

% date
Sun Jan  2 00:48:08 GMT 2000
% print -P '%D{%G}'
1999
% date +%G
1999
% date +%Y
2000
% print -P '%D{%Y}'
2000

What is %G, anyway?  It's not one of the zsh extensions; it's just being
handled by the native strftime(3).  My strftime(3) doesn't document %G,
and I don't have its source handy.  I expect that %G is the year part
of the week specification for the current week; today is 1999-W52-7,
and 2000-W01 starts tomorrow (2000-01-03 == 2000-W01-1).  Ah, look:

% date -d tomorrow
Mon Jan  3 00:52:44 GMT 2000
% date -d tomorrow +%G
2000

-zefram

Re: Possible bug?

[Geoff Wing]

Zefram <zefram@fysh.org> typed:
:Mike Perez wrote:
:>Well I am not sure if this is a bug or not, but I was able to reproduce
:>it on a few machines that all were in Y2K.
:I can reproduce it too:
:% date
:Sun Jan  2 00:48:08 GMT 2000
:% print -P '%D{%G}'
:1999
:% date +%G
:1999


>From my strftime(3):

" %G	is replaced by the ISO 8601 year with century as a decimal number.

  %V	is replaced by the week number of the year (Monday as the first day
	of the week) as a decimal number [01,53].  According to ISO 8601
	the week containing January 1 is week 1 if it has four or more days
	in the new year, otherwise it is week 53 of the previous year, and
	the next week is week 1.  The year is given by the `%G' conversion
	specification."

Regards,
-- 
Geoff Wing : <gcw@pobox.com>     Work URL: http://www.primenet.com.au/
Rxvt Stuff : <gcw@rxvt.org>      Ego URL : http://pobox.com/~gcw/
Zsh Stuff  : <gcw@zsh.org>       Phone   : (Australia) 0413 431 874