public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
* Re:  is sgi accessable?
@  Lar Kaufman
  0 siblings, 0 replies; 5+ messages in thread
From: Lar Kaufman @  UTC (permalink / raw)
  To: blinux-list, blinux-list

I have been enlightened, though I suspect for those of us who sometimes
get so sidetracked by other events that they may not get to read mailing
lists for days at a time, the statement-response pattern is preferable.
I will modify my practices for the blinux list, then...

-lar
"As a matter of constitutional tradition, in the absence of evidence 
to the contrary, we presume that governmental regulation of the content 
of speech is more likely to interfere with the free exchange of ideas 
than to encourage it...." -- _Reno v ACLU_ 1997, U.S. Supreme Court


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re:  is sgi accessable?
   Lar Kaufman
@  ` Luke Davis
  0 siblings, 0 replies; 5+ messages in thread
From: Luke Davis @  UTC (permalink / raw)
  To: blinux-list

My personal opinion is that: if you aren't going to quote in a Q/A fassion
(quoted question, answer, quoted question, answer, ...), and instead are
just going to quote the original message: put it at the end, so I don't
have to read through pages of stail stuff.

I hang around (and hung around) several mailing lists.

The consense of the procmail mailing list is as stated above, and many on
blindad, blind-l, etc. also seem to agree that you should put the quotes
at the end.

I have *never* encountered a blind individual who directly stated they
prefered the quote first; but I have encountered hundreds who prefer the
quote-at-end method.

It is not unheard of for me (and apparently 60 percent of the procmail
list as well <grin>), to delete entire messages when pressed for time, and
I don't feal like searching the maybe two lines of valid new data, in a 50
line quoted message that I saw not 10 minutes before.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re:  is sgi accessable?
@  Lar Kaufman
   ` Luke Davis
  0 siblings, 1 reply; 5+ messages in thread
From: Lar Kaufman @  UTC (permalink / raw)
  To: blinux-list, blinux-list

Jim's request that people answer his question before quoting it was a
surprise to me.  (Sorry, Jim, I can't answer the question you asked;
this comment takes off on a tangent.)  I dislike formats that offer long
answers and then append the prior message(s), having been trained in
the Usenet tradition of tagging the prior remark to which I am responding
and then replying.  Sure, I try to either extract the essential remarks
that I'm responding to, or I simply encapsulate a summary in square 
brackets, but I put the remarks in sequential order to prompt the readers
of what has gone on before and to prevent confusion about what I am 
addressing.

I can understand a reason for Jim's request, assuming that review is 
unnecessary or not immediately important.  (In this case, the header
of Jim's message provides the needed context, so quoting his query
is fairly redundant.) But is there a strong preference one way or the
other for people using adaptive devices?  I suspect one could add a
little code to a preferred emacs mail program to hide traditionally
tagged quotelines and toggle their presentation at the reader's option...
(maybe with a simple marker indicator to indicate that the suppressed
info is there?)

In other matters... my current beef is a mailserver (I can guess whose
product it is) that returns bounced email as mime-encapsulated RTF.  As
if, of course, you should have to use an RTF browser in order to read
the ASCII message you had sent...

 -lar
"As a matter of constitutional tradition, in the absence of evidence 
to the contrary, we presume that governmental regulation of the content 
of speech is more likely to interfere with the free exchange of ideas 
than to encourage it...." -- _Reno v ACLU_ 1997, U.S. Supreme Court


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: is sgi accessable?
   Jim Stevenson
@  ` Brian L. Sellden
  0 siblings, 0 replies; 5+ messages in thread
From: Brian L. Sellden @  UTC (permalink / raw)
  To: blinux-list

Hello -

Jim asked a question which I will repeat later...
To answer the question here is an excerpt from Raman's
emacspeak web page:

> I currently use Emacspeak at work on my Sparc20 workstation running SUNOS4.1;
> while at Digital I used Emacspeak on my DECALPHA workstation running Digital
> UNIX.

The emacspeak web site is at:
http://www.cs.cornell.edu/Info/People/raman/emacspeak/emacspeak.html

Now, for the original question...

>Can emacs speak or screader make command shell on SGI or Sun accessable?

-- 
---------------
Brian L. Sellden - brian@henge.com, brians@usa.net
User of Emacspeak 7.0,  making Unix talk.
http://www.henge.com/~brian
	      What on earth would a man do with himself
		if something did not stand in his way?
		-- H.G. Wells


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re:  is sgi accessable?
@  Jim Stevenson
   ` Brian L. Sellden
  0 siblings, 1 reply; 5+ messages in thread
From: Jim Stevenson @  UTC (permalink / raw)
  To: blinux-list

Can emacs speak or screader make command shell on SGI or Sun accessable?

Thanks.
And please answer before quoting me.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 is sgi accessable? Lar Kaufman
  -- strict thread matches above, loose matches on Subject: below --
 Lar Kaufman
 ` Luke Davis
 Jim Stevenson
 ` Brian L. Sellden

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).