all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathias Dahl <brakjoller@gmail.com>
Subject: Re: Emacs: a 21st century text-editor
Date: Wed, 09 Mar 2005 10:32:38 +0100	[thread overview]
Message-ID: <usm35f9l5.fsf@gmail.com> (raw)
In-Reply-To: mailman.3038.1110313983.32256.bug-gnu-emacs@gnu.org

"Christopher G D Tipper" <chris.tipper@gmail.com> writes:

> It just seems to be stuck in the 20th century with no sign of any
> attempt at modernisation.

Although I agree somewhat I think you are a bit unfair. Lately it has
got some nie-looking tool bar, the file dialog when accessed from the
menu bar is quite good (at least on Windows), etc.

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

Have you tried Ctrl-PgDown and Ctrl-PgUp? Works quite well. I too miss
a horizontal scroll bar sometimes though.

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

I agree with this and I really do not understand why it should be that
hard to "feel" if an Emacs instance is allready running, and opening
the file in that. But I am no low-level programmer, so I would not
know about technical limitations here.

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

Personally, that tab-bar would be so crowded that the tabs would not
do any good. I tend to have many files and buffers open, especially
since emacs is more than a text editor for me (reading news, mail,
todolists, calendar etc etc). Btw, have you tried out tabbar.el? I
don't like it, but you might.

Persistent files though sessions is solved in many ways (desktop.el is
built in in emacs).

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

On Windows, File -> Open File... works for me. I like to open the
files using the minibuffer though.

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

I used to like this. I used pc-selection-mode and
delete-selection-mode, which you will probably like, but nowadays I
have turned all that off. I do not even use transient-mark-mode. I
have got used to do C-SPC (set-mark-command), move the cursor to the
end of the region I want to operate on, and to C-w, M-w, delete-region
(which I have mapped to C-c d). And I like it. For deleting words or
lines, I use M-d, C-k etc.

Basically I see where you are coming from, but by being a bit flexible
and accepting some "old quirks" (which seems to be really thought
through when you get used to it), I like it the way it works. Just
because something is not familiar does not meen that it is bad.

IMHO, of course... :)

/Mathias

  parent reply	other threads:[~2005-03-09  9:32 UTC|newest]

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

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=usm35f9l5.fsf@gmail.com \
    --to=brakjoller@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.