From: Tim X <timx@spamto.devnul.com>
Subject: Re: What did you do with Emacs!!!!!
Date: 10 Apr 2003 18:11:53 +1000 [thread overview]
Message-ID: <87u1d6py9i.fsf@tiger.rapttech.com.au> (raw)
In-Reply-To: x5el4ds4x3.fsf@lola.goethe.zz
David Kastrup <dak@gnu.org> writes:
> Tim X <timx@spamto.devnul.com> writes:
>
> > David Kastrup <dak@gnu.org> writes:
> >
> > > Tim X <timx@spamto.devnul.com> writes:
> > >
> > > > The first thing I did when moving to emacs 21 was finid out how to
> > > > get rid of the toolbar, the blinking cursor and rebuilt it without
> > > > image support.
> > >
> > > What does the last buy you except make it completely impossible to
> > > use something like <URL:http://preview-latex.sourceforge.net>?
> >
> > I don't need it - I'm a blind user and ALL forms of graphics are a
> > total waste of time for me.
>
> A detail worth mentioning.
Didn't think it was relevant since the original poster was asking
about how to make their emacs 21 like older emacs.
> Is there an advantage of using a window
> environment at all in that case? I would imagine that it would not
> buy you anything over a pure tty Emacs.
Frames for one, which I find more convenient than constantly splitting
and switching windows. Sawfish makes this easy to integrate and ensure
you have full screens etc. Also, there are some programs which only
work well under a windowing environment (e.g. real player) which I
like to use plus it use to be a lot easier to setup so that you had
more characters and lines per screen than you could get in a tty. I
also got use to X when I was working on pure X workstations where you
didn't have the option of a tty.
Tim
--
Tim Cross
The e-mail address on this message is FALSE (obviously!). My real e-mail is
to a company in Australia called rapttech and my login is tcross - if you
really need to send mail, you should be able to work it out!
next prev parent reply other threads:[~2003-04-10 8:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 16:44 What did you do with Emacs!!!!! R. Readi
2003-04-01 16:57 ` Marco Parrone
2003-04-01 18:02 ` R. Readi
2003-04-01 18:09 ` John Russell
2003-04-01 18:24 ` Adam
2003-04-02 2:02 ` Miles Bader
2003-04-01 19:28 ` Stefan Monnier
2003-04-02 9:13 ` Ivan Kanis
2003-04-02 10:32 ` Alfred M. Szmidt
2003-04-02 17:02 ` R. Readi
2003-04-02 18:25 ` Kai Großjohann
2003-04-02 19:06 ` Bijan Soleymani
2003-04-02 17:33 ` Alan Mackenzie
2003-04-03 11:20 ` R. Readi
2003-04-03 8:28 ` Tim X
2003-04-04 7:00 ` Lee Sau Dan
2003-04-06 17:27 ` David Kastrup
2003-04-06 19:39 ` Niels Freimann
[not found] ` <mailman.4183.1049658173.21513.help-gnu-emacs@gnu.org>
2003-04-07 13:08 ` Mario Domgörgen
2003-04-07 17:59 ` Adam
2003-04-08 8:31 ` Tim X
2003-04-08 9:40 ` David Kastrup
2003-04-08 11:10 ` Phillip Lord
2003-04-09 6:33 ` Lee Sau Dan
[not found] ` <m3n0j07n7g.fsf@mika.informatik.uni-f\x04reiburg.de>
2003-04-09 9:45 ` Phillip Lord
2003-04-09 6:33 ` Lee Sau Dan
2003-04-09 8:36 ` David Kastrup
2003-04-10 8:11 ` Tim X [this message]
2003-04-10 9:01 ` David Kastrup
2003-04-10 14:40 ` Hubert Chan
2003-04-03 9:27 ` Francois Fleuret
2003-04-03 11:27 ` R. Readi
2003-04-03 15:19 ` Adam
2003-04-04 20:19 ` John Russell
2003-04-06 17:25 ` David Kastrup
[not found] <mailman.3960.1049221960.21513.help-gnu-emacs@gnu.org>
2003-04-01 18:48 ` R. Readi
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87u1d6py9i.fsf@tiger.rapttech.com.au \
--to=timx@spamto.devnul.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).