zsh-users
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Stefan Monnier"
	<monnier+lists/zsh/users/news/@tequila.cs.yale.edu>,
	<zsh-users@sunsite.auc.dk>
Subject: RE: zsh startup files
Date: Mon, 29 Mar 1999 18:29:17 +0400	[thread overview]
Message-ID: <002501be79f0$86c54620$21c9ca95@mowp.siemens.ru> (raw)
In-Reply-To: <5ln20wgz57.fsf@tequila.cs.yale.edu>

>
> [ passing note:  if someone could tell me in which case terminal setup
>   is useful, I'd be happy to learn.

Our tty driver defaults to DEL for interrupt. Some of our terminals
(notably, vt-like ones) don't have DEL at all (they have Delete that sends
escape sequence). So, intr is remapped to ^C for such terminals.
>
> Could you give examples of zshrc (zlogin is irrelevant to me: you
> either use
> zlogin or zprofile, not both) settings that might depend on
> TERM/LINES/COLUMNS?

Setting truncation for {R,L}PROMPT. I'd probably would like to set this for
all interactive shells (if at all), and for this reasin this should go into
zshrc. Setting bold/standout etc attrs (depending on which is uderstood by
terminal). Resetting of some terminal attrs in precmd (in our case, FMLI
resets am attr if terminal has capabillity to do it. It leads to all sorts
of side effects, as all programs expect, that if am is listed, it is set
-( Hey, I can imagine binding to func keys as well.

>
> The /etc/z* files should be *minimal*.  Anything that is not strictly
> necessary should be moved to /etc/user/foo and explicitly sourced
> from ~/.z*

Entirely agreed.

cheers

/andrej


  reply	other threads:[~1999-03-29 14:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-24 22:48 Stefan Monnier
1999-03-24 23:15 ` Sweth Chandramouli
1999-03-25  0:47   ` Stefan Monnier
1999-03-25  5:53     ` Sweth Chandramouli
1999-03-25 11:17       ` Doug Morris
1999-03-25  2:20   ` Jason Price
1999-03-25  9:03 ` Peter Stephenson
     [not found]   ` <9903251002.AA18225@ibmth.df.unipi.it>
1999-03-25 10:55     ` Wolfgang Hukriede
1999-03-25 11:22       ` Peter Stephenson
1999-03-25 12:36         ` Stefan Monnier
1999-03-25 14:00           ` Peter Stephenson
1999-03-25 19:37             ` Stefan Monnier
1999-03-28  1:04               ` Bart Schaefer
1999-03-28 22:14                 ` Stefan Monnier
1999-03-29  1:57                   ` Bart Schaefer
1999-03-29  4:14                     ` Sweth Chandramouli
1999-03-29 14:15                     ` Stefan Monnier
1999-03-29 14:29                       ` Andrej Borsenkow [this message]
1999-03-31  7:14                         ` Bart Schaefer
1999-03-31  7:49                           ` Bart Schaefer
1999-04-02 13:12                           ` Stefan Monnier
1999-04-02 17:13                             ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2006-03-14 17:38 zzapper
2006-03-14 19:50 ` Wayne Davison
2006-03-15  2:43   ` Bart Schaefer
2006-03-15 18:22     ` Phil Pennock
2006-03-16 19:29     ` Dominic Mitchell
1996-10-19 23:04 Zsh " Nate Johnston
1996-10-20 11:09 ` Zefram

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='002501be79f0$86c54620$21c9ca95@mowp.siemens.ru' \
    --to=borsenkow.msk@sni.de \
    --cc=monnier+lists/zsh/users/news/@tequila.cs.yale.edu \
    --cc=zsh-users@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).