unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Christopher G D Tipper" <chris.tipper@gmail.com>
Subject: Emacs: a 21st century text-editor
Date: Tue, 08 Mar 2005 20:04:02 -0000	[thread overview]
Message-ID: <422E0532.13774.47E771@localhost> (raw)

Emacs: a 21st century text-editor

I have been using emacs for over a year now, and value its power and
flexibility. However, I cannot get used to some idiosyncrasies of its
behaviour which seem to me to be artifacts of its heritage, rather
than components of a piece of modern software. What I am talking about
is nothing to do with any superficial features, such as the complex
interface nor its architecture. It just seems to be stuck in the 20th
century with no sign of any attempt at modernisation.

1 Text-wrapping. Text wrapping is a limitation, and it would be nice
  to scroll past the edge of the screen. This is particularly acute in
  my case editing XSLT scripts where line-breaks become a
  presentational issue. Sometimes I actually need to compose documents
  with 250 columns, and I don't appreciate emacs telling me otherwise.

2 Shell open. Emacs really ought to be able recognise when the shell
  is requesting it to open a file. Gnu-client should be unnecessary in
  a modern application.

3 Tabbed buffers. Open buffers should be easily visible in a tabbed
  layout below the menu, in the manner of XEmacs. A proper history
  list would help here so that documents are persistent across
  sessions.

4 File Dialogs. I use dlgopen.el on Windows, which gets rid of the
  most serious interface issue of all, the lack of modern file
  dialogs. It wouldn't be rocket-science to adapt the interface to
  support this. XEmacs file dialogs are unusable IMHO.

5 Paste replaces edit. This idea that when I paste I end up with both
  the replacement text and the old text does not belong in the modern
  idiom. This is a real versioning issue when the replacement text
  scrolls past the bottom of the screen. I think this is just an
  old-fashioned feature that never got updated.

Best wishes,
Christopher Tipper
--------------------------------o00o--------------------------------
  "Since light travels faster than sound, isn't that why 
   some people appear bright until you hear them speak" 
                                          - Steve Wright

             reply	other threads:[~2005-03-08 20:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 20:04 Christopher G D Tipper [this message]
2005-03-08 21:14 ` Emacs: a 21st century text-editor Eli Zaretskii
     [not found] <mailman.3038.1110313983.32256.bug-gnu-emacs@gnu.org>
2005-03-08 20:42 ` Ulrich Hobelmann
2005-03-09  5:22   ` Gaetan Leurent
2005-03-09  9:32 ` Mathias Dahl
2005-03-10 20:01   ` Gian Uberto Lauri
2005-03-11 20:28     ` Richard Stallman
2005-03-15  0:07 ` Alan Mackenzie

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=422E0532.13774.47E771@localhost \
    --to=chris.tipper@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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