zsh-workers
 help / color / mirror / code / Atom feed
From: Timothy J Luoma <tjlists@bigfoot.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: yet another undesired 3.1.5-pws-15 change
Date: Fri, 23 Apr 1999 23:11:06 -0400	[thread overview]
Message-ID: <199904240311.XAA00619@ocalhost> (raw)
In-Reply-To: <199904231059.MAA32358@beta.informatik.hu-berlin.de>

Replying to message of Fri, 23 Apr 1999 12:59:46 +0200 (MET DST)
	from Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
	regarding ``Re: yet another undesired 3.1.5-pws-15 change''
	
> > ps -- there seem to be a LOT of these types of changes in 3.1.5....
>
> Please name them, because...

OK, I will make sure to mention them.

Earlier OLDPWD didn't behave the same way (it seems to now though)

There's still a problem with my PROMPT:

PROMPT='
---------------------------------------- %t/%T  
----------------------------------------
%S[OLDPWD: $OLDPWD]
   [PWD: %~]%s
%B%n$LOCAL_HOST%b $REMOTE_HOST
'

it produces an extra blank line at the end (unlike 3.1.4)


> > I wish there were more consideration given to keeping things
> > consistent for those who upgrade... changing the way things
> > behave and making the user reconfigure everything is not a good
> > thing...
>
> ...of course, we (w.r.t. the completion code: I) tried to keep the old
> behavior, but there were a lot of changes in the code needed for the
> new features (and there are many of them) and so I didn't manage to do
> so in some cases.

It was my misunderstanding then.  From some offlist replies I got to earlier  
comments, it sounded like "Things change, get over it."  I realize now that  
I should have guessed they were not the voice of authority.



> As for your other message: I need some more help here since I can't
> reproduce it. Can you complete the names that don't appear in the
> list? By giving an unambiguous prefix? Only with menucompletion? This
> is NextStep (right?): did you get any compiler warnings in
> Zle/zle_tricky.c? (Weird question, but I have no idea how what you
> described can happen...)

I don't remember any warnings... well, there were warnings, but I don't  
remember what they were.

I cannot solve it by giving unambiguous filenames:

# ls /
CDROM/              Users/              mach_kernel
LocalApps@          bin/                mach_kernel.OS42
LocalLibrary@       dev@                mach_kernel.nonY2K
Net/                drives/             private/
NextAdmin/          etc@                tmp@
NextApps/           lib/                usr/
NextDeveloper@      lost+found/
NextLibrary/        mach@

(note there is only one "/U")

# ls /U[tab]
# ls /U

# ls /drives/
IBM3/   win95/

# ls /drives/I[tab]
# ls /drives/I

NOTE: I can't build zsh again, I keep getting errors about files that end  
with .pro not existing (ie prompt.pro) and it dies.

I don't know how I did it before.

TjL



  reply	other threads:[~1999-04-24  6:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-23 10:59 Sven Wischnowsky
1999-04-24  3:11 ` Timothy J Luoma [this message]
1999-04-25 13:44   ` Peter Stephenson
1999-04-25 14:35     ` Geoff Wing
1999-04-25 15:22       ` PATCH: 3.1.5-pws-15: multiline prompt Geoff Wing
     [not found]   ` <990423234917.ZM30140@candle.brasslantern.com>
     [not found]     ` <199904241324.JAA23300@ocalhost>
     [not found]       ` <990424092703.ZM32177@candle.brasslantern.com>
     [not found]         ` <199904302157.RAA26524@ocalhost>
     [not found]           ` <990504100735.ZM28408@candle.brasslantern.com>
1999-05-11  2:40             ` success (mostly) pws 17 under NeXTStep 3.3 Timothy J Luoma
1999-05-11  8:06               ` Peter Stephenson
  -- strict thread matches above, loose matches on Subject: below --
1999-04-23 10:14 yet another undesired 3.1.5-pws-15 change Timothy J Luoma
1999-04-28 18:13 ` Wayne Davison
1999-04-30 23:24   ` Timothy J Luoma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199904240311.XAA00619@ocalhost \
    --to=tjlists@bigfoot.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).