zsh-workers
 help / color / mirror / code / Atom feed
From: st001008@HRZPUB.th-darmstadt.de (Thomas Pierre Schweikle)
To: bas@phys.uva.nl (Bas V. de Bakker)
Cc: mliggett@indiana.edu, zsh-workers@math.gatech.edu
Subject: Re: couple of zsh features
Date: Sat, 16 Dec 1995 01:52:40 +0100	[thread overview]
Message-ID: <v02130502acf214518f39@[130.83.177.13]> (raw)

At 10:07 Uhr 08.12.1995, Bas V. de Bakker wrote:
> Matt Liggett <mliggett@seven.ucs.indiana.edu> writes:
>
> > I can tell what's what, but it could save me the odd 0.75 second here
> > or there when I'm scanning up to find the command.
>
> But there is a way to do this.  Put an escape sequence in your prompt
> to make the text boldface, red, blinking, whatever your terminal can
> handle.  Then set the POSTEDIT variable to the sequence that resets
> this feature.

Quite the best way to find out where the last command was typed! But on
some (elderly) terminals this might not work - they don't have colours,
blinking, bold or even inverse! There is a solution too: just print a line
containing some 80 characters all the same:

-----------------------------------------------------------------------------
Like the above! I do this to find my way inbetween commands and there
output - expecialy when using terminal emulators. Most of them don't even
have inverse.

-- Thomas



             reply	other threads:[~1995-12-16  1:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-12-16  0:52 Thomas Pierre Schweikle [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-12-08  7:20 Sven Wischnowsky
1995-12-07 16:31 Matt Liggett
     [not found] ` <mliggett@seven.ucs.indiana.edu>
1995-12-07 17:29   ` Barton E. Schaefer
1995-12-07 17:59     ` Matt Liggett
1995-12-08  9:07       ` Bas V. de Bakker
1995-12-07 20:22     ` Richard Coleman
1995-12-07 19:02   ` Barton E. 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='v02130502acf214518f39@[130.83.177.13]' \
    --to=st001008@hrzpub.th-darmstadt.de \
    --cc=bas@phys.uva.nl \
    --cc=mliggett@indiana.edu \
    --cc=zsh-workers@math.gatech.edu \
    /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).