zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: (partially) Re: %<< and %{%}
Date: Tue, 29 Feb 2000 18:12:44 +0000	[thread overview]
Message-ID: <1000229181244.ZM31539@candle.brasslantern.com> (raw)
In-Reply-To: <1000229173223.ZM29798@candle.brasslantern.com>

On Feb 29,  5:32pm, Bart Schaefer wrote:
} Subject: Re: %<< and %{%}
}
} On Mar 1, 12:26am, Tanaka Akira wrote:
} } Subject: %<< and %{%}
} }
} } I heard that the combination of %<< and %{%} in prompt doesn't work well.
} } 
} } Hm.  The string in %{..%} is affected to truncation.  It is wrong.

Had a quick look at this ... unfortunately, the way prompt truncation
is now calculated, the knowledge of what strings were contained inside
%{...%} has been lost by the time we start computing the truncation.
That means that we might even truncate into the middle of a %{...%}.

Prior to 4601 (and in the 3.0 series), prompt truncation applied to
exactly one following %-escape, which made it very difficult to specify
the total length of the prompt.  4601 introduced the idea of truncating
the entire remainder of the prompt, unless truncation were explicitly
limited by either enclosing it in %(...) or by an empty truncation, as
I suggested here:

} PS1=$'[%20<..<%/%<<]%{\e[33m%}'

Unfortunately this has the unwanted side-effect that the prompt is fully
generated before its size is counted for truncation -- and hence the
trouble with %{...%}.

Fixing this is going to require another rethinking of putpromptchar().

} There does seem to be a bug with handling of turncations inside the %()
} conditional construct; if the truncation is in the "true" branch, then
} the false branch and the trailing `)' are left as part of the prompt.

That, however, is easily fixed.

Index: Src/prompt.c
===================================================================
@@ -815,9 +815,9 @@
 	     */
 	    if (!putpromptchar(doprint, endchar))
 		return 0;
-	    /* Now we have to trick it into matching endchar again */
-	    fm--;
 	}
+	/* Now we have to trick it into matching endchar again */
+	fm--;
     } else {
 	if (*fm != ']')
 	    fm++;

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


  reply	other threads:[~2000-02-29 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-29 15:26 Tanaka Akira
2000-02-29 17:32 ` Bart Schaefer
2000-02-29 18:12   ` Bart Schaefer [this message]
2000-02-29 18:36     ` PATCH: (partially) " Bart Schaefer

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=1000229181244.ZM31539@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).