all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
	Christopher Schmidt <christopher@ch.ristopher.com>
Subject: Re: Emacs 24 - next line with wrapped lines
Date: Mon, 2 Jul 2012 17:57:24 +0200	[thread overview]
Message-ID: <CAMXnza1XVEeL3bONgZdtV+vW15DE1OEWnMUzn=Pmwa6OJU25vQ@mail.gmail.com> (raw)
In-Reply-To: <CA+5B0FMFVv-XvMHWt-7KzqkLHgyneHVtoh2qwb=Lc21xBYf9WA@mail.gmail.com>

On Mon, Jul 2, 2012 at 5:29 PM, Aurélien Aptel
<aurelien.aptel+emacs@gmail.com> wrote:
> On Mon, Jul 2, 2012 at 4:40 PM, Doug Lewan <dougl@shubertticketing.com> wrote:
>> One of the things that attracted me to emacs from the beginning is that you can edit /files/. Most editors want you to edit /text/. The whole visual-line thing was a big step backwards for me, but I've never known how to undo it.
>
> Also if you don't want lines to wrap in any way you can add this to your .emacs:
>
> (setq truncate-partial-width-windows nil)
> (setq-default truncate-lines t)
>

Well, I wrap lines for modes meant for prose, and turn it off for
programming modes. These are my relevant configs:

  (custom-set-variables
   ;; ...
   '(truncate-lines t))

  (add-hook 'text-mode-hook '(lambda() (visual-line-mode t)))

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.



      reply	other threads:[~2012-07-02 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 22:57 Emacs 24 - next line with wrapped lines nroose
2012-06-29 23:07 ` Christopher Schmidt
2012-07-02 14:40   ` Doug Lewan
2012-07-02 15:29     ` Aurélien Aptel
2012-07-02 15:57       ` suvayu ali [this message]

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='CAMXnza1XVEeL3bONgZdtV+vW15DE1OEWnMUzn=Pmwa6OJU25vQ@mail.gmail.com' \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=aurelien.aptel+emacs@gmail.com \
    --cc=christopher@ch.ristopher.com \
    --cc=help-gnu-emacs@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 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.