unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uday S Reddy <u.s.reddy@cs.bham.ac.uk>
To: emacs-devel@gnu.org
Subject: Re: visual-line-mode and line wrapping
Date: Tue, 25 May 2010 14:16:23 +0100	[thread overview]
Message-ID: <htgij6$uvr$1@dough.gmane.org> (raw)
In-Reply-To: <87ocg4kxs2.fsf@uwakimon.sk.tsukuba.ac.jp>

On 5/25/2010 12:48 PM, Stephen J. Turnbull wrote:
> Uday S Reddy writes:
>
>   >  Hi Stefan, My use for it would be that, occasionally, I want to
>   >  [vertically] enlarge the Emacs window for some purpose or the other.
>
> Sure.  My window manager has a maximize vertically option (button 2 on
> the maximize button).

No, I meant enlarge horizontally.  With my standard email summary format, 80 columns turn out to produce summary lines like this:

->2727 N  5/25  Hans Hüttel          11376-  [TYPES/announce] Book announcement:
   2662    5/23  Ulrich Müller         6629-  [Bug 584616] [NEW] vm-8.1.1 paralle
     51    5/21  Eli Zaretskii         3813-     Re: bug#6229: 23.2; Cancel debug

Most of the time they turn out fine.  The initial bits of the subject line are enough to tell me what is going on.  But sometimes they aren't.  So, horizontal enlargement of the frame is warranted.

I think the more general point is that an Emacs frame might contain some windows that have wrapped text and others that have unwrapped text.  We need to balance the needs of both.

Cheers,
Uday




  reply	other threads:[~2010-05-25 13:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 14:09 visual-line-mode and line wrapping Leo
2010-05-24 14:12 ` Lennart Borgman
2010-05-24 15:08   ` Leo
2010-05-24 15:29     ` Lennart Borgman
2010-05-24 16:42       ` Leo
2010-05-24 17:41         ` Lennart Borgman
2010-05-24 17:34 ` Stefan Monnier
2010-05-24 19:18   ` Leo
2010-05-24 19:31     ` Chong Yidong
2010-05-24 19:53       ` Leo
2010-05-24 20:33         ` Lennart Borgman
2010-05-24 19:58       ` Lennart Borgman
2010-05-24 20:27         ` Leo
2010-05-24 20:36           ` Lennart Borgman
2010-05-25  1:05         ` Johan Bockgård
2010-05-24 20:26     ` Stefan Monnier
2010-05-24 21:26       ` Lennart Borgman
2010-05-25 12:59         ` Sean Sieger
2010-05-25  5:10       ` Leo
2010-05-25  7:37   ` Miles Bader
2010-05-25 10:05     ` João Távora
2010-05-25 11:11       ` Lennart Borgman
2010-05-25 13:27         ` João Távora
2010-05-25 11:09     ` Lennart Borgman
2010-05-25 14:04     ` Stefan Monnier
2010-05-25 14:18       ` Lennart Borgman
2010-05-25 15:06         ` Drew Adams
2010-05-25 14:49       ` Drew Adams
2010-05-25 16:33       ` Leo
2010-05-25  8:36   ` Uday S Reddy
2010-05-25 11:48     ` Stephen J. Turnbull
2010-05-25 13:16       ` Uday S Reddy [this message]
2010-05-25 14:40         ` Drew Adams
2010-06-05  9:21     ` Uday S Reddy
2010-06-07 20:34       ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2010-05-25  2:52 MON KEY

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='htgij6$uvr$1@dough.gmane.org' \
    --to=u.s.reddy@cs.bham.ac.uk \
    --cc=emacs-devel@gnu.org \
    /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).