all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: Lennart Borgman (gmail) <lennart.borgman@gmail.com>
Cc: bug-gnu-emacs@gnu.org, Sean Ochoa <wakiewakie@gmail.com>
Subject: Re: What about "The Modernization of Emacs"?
Date: Fri, 21 Dec 2007 09:21:21 +0000	[thread overview]
Message-ID: <761B9F48-795C-418C-834E-B6688FF31950@gmail.com> (raw)
In-Reply-To: <476AF064.4020900@gmail.com>

On 20 Dec 2007, at 22:44, Lennart Borgman (gmail) wrote:
>
> ;; * Make longlines-mode the default editor behavior for any
> ;;   file. (So that, the up arrow and down arrow keys moves
> ;;   the cursor by a visual line, not by line-return
> ;;   character.
>
> I think this deserves some thought.
>
> By default Emacs wraps long lines. This is not the same as longlines- 
> mode. I think it would be useful to be able to use down/up arrows to  
> move to the next/previous visual line. I believe this might be what  
> beginners expect. (Maybe there is already such an option in Emacs?)

Longlines mode is littered with problems. It fails to break lines  
correctly just when you need soft word wrapping most, i.e. for long  
prose texts  which are displayed with a variable width font, or where  
lines are shown in different font sizes (AUCTeX). Longlines fails to  
recognize comments, e.g., in LaTeX (this is a bug!). Because the line- 
number correspondence between files and buffer lines get lost, a lot  
of functions simply don't work any longer (this is a bug!), such as  
jumping to the place of errors in LaTeX files (compiler reports file  
lines, then jumps to buffer lines). I wrote some code to make  
`pdfsync' work with longlines in AUCTeX, but these things are really  
just hacks because the mode rightfully assumes that buffer line = file  
line.
Longlines also isn't recognized automatically when a text file with  
many long lines is loaded. The setting "use longlines for all text  
modes" is rather cumbersome.

Rather than going on with this rant, I'd like to point readers to a  
post by Fernando Pereira:

http://article.gmane.org/gmane.emacs.macintosh.osx/3524

Instigating change is good. But solving the problems is better. Write  
code!




  reply	other threads:[~2007-12-21  9:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 15:13 What about "The Modernization of Emacs"? Sean Ochoa
2007-12-20 22:44 ` Lennart Borgman (gmail)
2007-12-21  9:21   ` David Reitter [this message]
2007-12-21 19:49   ` Richard Stallman
2007-12-21 16:21 ` Eli Zaretskii
2007-12-21 16:33 ` Shawn Boyette ☠

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=761B9F48-795C-418C-834E-B6688FF31950@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=wakiewakie@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.