all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: bug-gnu-emacs@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: longlines-mode and comments
Date: Fri, 30 Nov 2007 07:22:30 +0000	[thread overview]
Message-ID: <FD88BF40-1288-42AA-A839-85B1FDB2A710@gmail.com> (raw)
In-Reply-To: <474E95A7.4090807@gmx.at>

On 29 Nov 2007, at 10:34, martin rudalics wrote:

>> (Also, when `longlines-wrap-follows-window-size' is turned on,  
>> then  the line/paragraph is reformatted.)
>> The expected (correct) behavior would be to add the comment command  
>> at  the beginning of the line in the file, i.e. at the beginning of  
>> the  paragraph, that is, after each hard return.
>> Note that the other expected thing there is that the syntax   
>> highlighting (font-lock) works, i.e. that the whole comment is  
>> shown  using the right face. This, IMHO, is a second bug.
>
> It's hardly trivial.  Have a look at the thread starting with:
>
> http://lists.gnu.org/archive/html/emacs-devel/2006-11/msg00634.html

Sure, one can fix longlines to deal with further eventualities. But  
each of them is going to be a further hack, because code everywhere  
assumes that a line in the buffer is a line in the file, and  
everything else would be a lot more complicated.

Longlines mode has a number of shortcomings that can't be addressed  
within the current architecture: for instance it looks rather bad with  
variable-width fonts and with different font sizes in the buffer, for  
instance when editing long LaTeX documents using AUCTeX.

The alternative is display-time word wrap (DTWW), and Kim Storm has  
developed a patch that was supposed to be applied after the 22.1  
release:

http://www.mail-archive.com/emacs-pretest-bug@gnu.org/msg03729.html

There was a good discussion in 2005 with the same conclusion:

http://www.nabble.com/flyspell-+-longlines:-hang-wait-t448677.html

I wish this could be updated and applied. Every modern text editor has  
this. It is really needed when you want to write text and not code on  
non-TTY displays.




  reply	other threads:[~2007-11-30  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 16:02 longlines-mode and comments David Reitter
2007-11-29 10:34 ` martin rudalics
2007-11-30  7:22   ` David Reitter [this message]
2007-11-30 16:48     ` Richard Stallman
2007-12-17 18:40   ` David Reitter
2007-12-17 22:11     ` martin rudalics

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=FD88BF40-1288-42AA-A839-85B1FDB2A710@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=rudalics@gmx.at \
    --cc=storm@cua.dk \
    /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.