From: Lee Sau Dan <danlee@informatik.uni-freiburg.de>
Subject: Re: Efficient Emacs usage?
Date: 23 Nov 2004 15:49:31 +0800 [thread overview]
Message-ID: <87vfbx0zuc.fsf@informatik.uni-freiburg.de> (raw)
In-Reply-To: cnsuqo$smc$1@defalla.upc.es
>>>>> "FCC" == FCC <fcc509@netscape.net> writes:
FCC> I am wondering if I am missing anything of Emacs that could
FCC> be of great use to me
Yes, of course. Check what M-/ does, and be warned that it is addictive!
Also, if you have ispell installed and you're typing in text-mode (or
derived ones), you can M-Tab to complete the word. (And you'll start
to hate Windows, which gives you NO WAY to stop it from
stealing/robbing this key binding.)
Have you tried w3? I don't use it, as it is really slow. But I like
the way in which I can navigate the page displayed. This is quite
cool when filling in forms, because all the editing capabilities of
Emacs are there at your disposal. (But the UI of Mozilla and Firefox
are approaching such 'friendliness' recently. E.g. starting a search
with "/".)
And if you edit text files (including C/C++/Java/whatever source code,
LaTeX manuscripts, etc.) and you aren't using version control,
consider learning to use RCS or CVS under Emacs. I myself learnt RCS
first under Emacs, well before I got familiar with the RCS command
line. (Emacs has made it much easier to use RCS and CVS than on the
command line.) If you are developing programs, don't miss M-x compile
and M-x gdb or M-x perldb.
FCC> (sorry, gnus does not count for me, although I am very much
FCC> aware of its popularity among Emacs users,
I know a vi user who likes to browse Usenet with Gnus+Emacs. I don't
know why. Maybe, Gnus's features are really unparalleled. I myself
am both an Emacs and vi user, switching easily between them every
other minute.
FCC> because probably it would be more efficient for me if I did
FCC> not have to check or send e-mails and also spend less time on
FCC> the internet).
--
Lee Sau Dan 李守敦 ~{@nJX6X~}
E-mail: danlee@informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee
next prev parent reply other threads:[~2004-11-23 7:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 14:58 Efficient Emacs usage? FCC
2004-11-22 18:18 ` Phillip Lord
2004-11-22 18:47 ` Floyd L. Davidson
2004-11-22 18:58 ` FCC
2004-11-23 7:55 ` Lee Sau Dan
2004-11-23 12:20 ` FCC
2004-11-24 3:44 ` Lee Sau Dan
2004-11-23 7:49 ` Lee Sau Dan [this message]
2004-11-23 12:34 ` FCC
2004-11-23 18:21 ` Micha Feigin
2004-11-23 20:48 ` Eli Zaretskii
2004-11-24 3:30 ` Lee Sau Dan
[not found] ` <mailman.1043.1101236972.27204.help-gnu-emacs@gnu.org>
2004-11-24 3:33 ` Lee Sau Dan
2004-11-24 12:11 ` Phillip Lord
2004-11-25 17:02 ` Mathias Dahl
2004-11-25 17:23 ` Phillip Lord
2004-11-26 7:44 ` Mathias Dahl
[not found] ` <mailman.1072.1101243703.27204.help-gnu-emacs@gnu.org>
2004-11-24 8:59 ` FCC
2004-11-24 9:04 ` Brian Elmegaard
2004-11-24 15:39 ` FCC
2004-11-24 7:55 ` John Paul Wallington
2004-12-01 18:30 ` Kevin Rodgers
2004-11-23 11:31 ` Marco Gidde
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=87vfbx0zuc.fsf@informatik.uni-freiburg.de \
--to=danlee@informatik.uni-freiburg.de \
/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).