From: Boris DAIX <Boris.Daix@insa-lyon.fr>
To: blinux-list@redhat.com
Subject: Re: Comparing Brltty and Suse
Date: Wed, 26 Jun 2002 21:51:53 +0200 [thread overview]
Message-ID: <877kklbyxy.fsf@Pulsar.resI.insa-lyon.fr> (raw)
In-Reply-To: <87k7olx37n.fsf@lexx.delysid.org> (Mario Lang's message of "Wed, 26 Jun 2002 21:14:04 +0200")
Mario Lang <mlang@teleweb.at> writes:
> "Nath" <nath31@ifrance.com> writes:
>
> I use mc with brltty regularly, and I don't have any problem.
Hi Mario :-) (you may remember my newbe question few weeks ago)
I feel like mc is really unconfortable to scroll, there are lots of
what I would call "garbage characters" (e.g. vert. and
horiz. lines). I use emacs/dired for managing files, and felt very
happy as BRLTTY works fine with emacs.
> mc presents the currently selected file in the bottom line of each
> split window. So I dont need attributes.
Sometimes file names are cut with ? between beginning and the end of
the name, preventing recognizing similar file names. Is there a way to
avoid this ? (I really can't think how)
> And the main menu and the dialog boxes all use the normal cursor
> to position correctly.
Ok - I personnaly can't stand menus... :-) (personnal feelings)
> There is a option in mc to enable this "statusline", but I forgot how it was
> called. I can look it up if you are interested.
I won't help here.
But, talking about BRLTTY features, are there generic filters to help
working on one program or another ?
Regards,
Boris
P.S.: I use BRLTTY with VisioBraille support and had to rebuild the
.deb because the config step broke down. Soon, when I'll be able to
understand Debian packages, I'll try to help about this.
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 [this message]
` Dave Mielke
` Boris DAIX
` 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=877kklbyxy.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).