zsh-workers
 help / color / mirror / code / Atom feed
* Re: PATCH: History bug with "print -s"
@ 2000-05-05  7:44 Sven Wischnowsky
  0 siblings, 0 replies; 2+ messages in thread
From: Sven Wischnowsky @ 2000-05-05  7:44 UTC (permalink / raw)
  To: zsh-workers


Wayne Davison wrote:

> Appended is a patch that should fix the funkiness associated with
> running "print -s" while zle is active.  I've done some very basic
> testing, and it appears to work fine.
> 
> However, if "print -s" is supposed to make the line immediately
> available for history browsing (before pressing return), that is not
> happening.  I can check into this next, but I don't have time to do
> that right now.

Yes, that's what Bart wanted. And it would be nice to have, wouldn't it?

> The following diff is based on an unpatched 3.1.7-pre-2.

I've committed it.

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


^ permalink raw reply	[flat|nested] 2+ messages in thread
* Re: PATCH: Re: History bug (Re: Completion debugging)
@ 2000-05-04 17:39 Bart Schaefer
  2000-05-05  7:25 ` PATCH: History bug with "print -s" Wayne Davison
  0 siblings, 1 reply; 2+ messages in thread
From: Bart Schaefer @ 2000-05-04 17:39 UTC (permalink / raw)
  To: zsh-workers

On May 4,  5:34pm, Sven Wischnowsky wrote:
} Subject: Re: PATCH: Re: History bug (Re: Completion debugging)
}
} There is so much mucking around curhist (and histline) in zle that I
} wonder if there is a clean way (other than changing the meaning of
} curhist in the core and then adapting zle).

Cf. "The one icky bit" in my "Dear old literal history" message.

} Maybe we should just make `print -s' put the strings added while zle
} is active into some list and then add those strings only after zle is
} left? I.e. in a toplevel-loop() or somewhere around that.

That's approximately what "print -z" does.  At least for _complete_debug,
the whole point is to get them into the history while you can still scroll
around and look at them.

Unfortunately that means either putting them into the future history or
changing the event number of the current command.  Neither works, at
least not easily, because the history is now stored as a ring rather
than as a simple linked list.  Wayne, are you out there?

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-05-05  7:44 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-05-05  7:44 PATCH: History bug with "print -s" Sven Wischnowsky
  -- strict thread matches above, loose matches on Subject: below --
2000-05-04 17:39 PATCH: Re: History bug (Re: Completion debugging) Bart Schaefer
2000-05-05  7:25 ` PATCH: History bug with "print -s" Wayne Davison

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).