From: Boris DAIX <Boris.Daix@insa-lyon.fr>
To: blinux-list@redhat.com
Subject: Re: Comparing Brltty and Suse
Date: Wed, 26 Jun 2002 23:53:35 +0200 [thread overview]
Message-ID: <8766051zc0.fsf@Pulsar.resI.insa-lyon.fr> (raw)
In-Reply-To: <Pine.LNX.4.30.0206261654110.1029-100000@dave.private.mielke.cc> (Dave Mielke's message of "Wed, 26 Jun 2002 16:55:13 -0400 (EDT)")
Dave Mielke <dave@mielke.cc> writes:
> BRLTTY has nothing one would call a filter. Tell me what needs to be
> implemented, and we'll certainly look into it.
Thank you for your interest. I may be far from BRLTTY purpose, as I'm
a new (and happy !) user, but would it be possible to recognize a
modeline in emacs so that we can easily jump from one window to
another (to read them) ? (GNU Emacs), because we often open a secondary window
(i.e. completion) and have to scroll "a lot" to find bottom one. In
fact, my question is "would it be possible to sectorize tty with some
pattern-matching to be faster while browsing it ?".
I have to say that, for the moment, I use a 20-sized
brailledisplay... So I scroll a lot :-) Another example would be to
split MC screen for reading (two vertical sectors, a third at the
bottom) so that it helps finding things.
This may not be a good idea as we would have to find a way to
recognize screens (MC, centericq, emacs and so on), and
pattern-matching would be hazardous sometimes (it wouldn't be built on
semantics, only appearence), but it gives an idea of what kinds of
screen-viewers could feature.
Tell me what you think about
Regards, Boris.
P.S. : I've used screen sectorizing tools under Windows and I know it wasn't
a good way to help as when you just move one thing, all goes wrong...
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
John J. Boyer
` Nath
` Mario Lang
` Boris DAIX
` Dave Mielke
` Boris DAIX [this message]
` Mario Lang
` Boris DAIX
` Nath
` Mario Lang
` Christian Schoepplein
` John J. Boyer
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=8766051zc0.fsf@Pulsar.resI.insa-lyon.fr \
--to=boris.daix@insa-lyon.fr \
--cc=blinux-list@redhat.com \
/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).