public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Tyler Spivey <tspivey@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Slight speech irregularity with grml
Date: Sat, 11 Mar 2006 18:00:44 -0800	[thread overview]
Message-ID: <20060312020044.GA3444@test1> (raw)
In-Reply-To: <Pine.LNX.4.63.0603111438250.4051@c-68-54-168-42.hsd1.md.comcast.net>

The problem you're having is zsh. This turned me off of the shell, until
I found:
setopt singlelinezle
which fixed the problem. I've been using zsh ever since. In the debian
version (4.3 or something) you also need:
unsetopt prompt_cr
or else the shell will write a percent or a number sign, delete it, and
print the prompt (which speakup will, if course, read).
also, grml does some weird things with the prompt, using ansi color or
the like, so
export PS1='%m%# ' should do the trick.
If I could get grml to boot off my usb stick, I'd put all that in a
config file. I don't want to cary around a floppy, though, so that won't
work for the cd. It'll boot off the stick, but the kernel takes 2
minutes to load, then grml another 2.
Hope this helps, and if you have any other zsh questions, I'll try to
help.

Here is my .zshrc file. Under Arch (the distro I'm using now) prompt_cr
doesn't need to be unset because it's using zsh 4.2, or something to do
with the terminal, not sure.

#unsetopt prompt_cr
export PS1='%m%# '
autoload -U zmv
export PATH=$PATH:/home/tyler/bin:/usr/local/bin:/home/tyler/cdrutils
setopt singlelinezle autocd
setopt menucomplete 
unsetopt listbeep autolist
source ~/.zshalias
bindkey    "^[[3~"          delete-char
bindkey    "^[3;5~"         delete-char
	bindkey "\e[1~" beginning-of-line
	bindkey "\e[4~" end-of-line


  parent reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jim Wantz
 ` Gregory Nowak
   ` Jim Wantz
 ` Dan Murphy
   ` Garrett Klein
 ` Tyler Spivey [this message]
   ` Michael Prokop

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=20060312020044.GA3444@test1 \
    --to=tspivey@pcdesk.net \
    --cc=speakup@braille.uwo.ca \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).