emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Query for S. Vauban
Date: Mon, 20 Sep 2010 09:51:51 +0200	[thread overview]
Message-ID: <8762y0yhrc.fsf@mundaneum.com> (raw)
In-Reply-To: 2551CCE1-8C18-4ACA-A908-5725098C398C@tsdye.com

Aloha Thomas,

"Thomas S. Dye" wrote:
> While using the listings setup you sent to the list a while back, I found
> this line and wondered why you chose not to break long lines?
>
>         breaklines=false, %!! don't break long lines of code
>
> The !! in the comment led me to believe you might have some strong reasons.

You're right guessing that the !! do have a meaning. Yes, they mean: this is
not a standard comment, that's something you really must be aware of...

I guess I did that for 2 reasons:

- be sure to easy locate what could be a wrong setting, in case I would not be
  happy with the listings results

- emphasize on the importance of that setting.

Now, why choosing this?  First, let me tell you I'm sometimes a bit of a crazy
perfectionist. I want the things to be perfectly output, and my reports to be
of great quality on the presentation side as well -- I cannot easily judge on
my own for the contents ;-)

One of the constraints I use in my daily life is: no more than 80 rows in
files, be it text (Org) or code (.emacs, bash scripts, etc.). In fact, even
not more than 78, when possible. I have Emacs column markers in columns 78, 79
and 80, showing me when I reach the limits.

I want my code in my files to be formatted in such a way as well, and have
chosen the right font size (in LaTeX) so that my code is displayed in the
LaTeX PDF with the biggest font possible, so that an 80-wide line is displayed
on one line, within the normal allowed space.

What about longer lines, then?

Either I let LaTeX listings decide for me. Either I don't. I've explicitly
chosen the second one, with the above setting in Listings. Why?  Because I
consider that lines longer than 80 characters are bad, and that *I* have to
correct them somehow. I don't want to rest on Listings to rearrange my code.
Plus, Listings does not do it good, if I remember good. The wrapped text never
won't be placed in the way you would do it if you had to break the line
yourself, explicitly.

So, in a nutshell, by forbidding long lines to be wrapped by Listings, I have
a clear indication that my code is too wide at some spots, and that I do have
to cut it in a clean way, directly in the source.


> I'm asking because I'm finding it difficult to configure the listings
> package so it works perfectly.

You're welcome.

Do I answer your question in an understandable way?  Just asking if I'm clear
about *my* objectives; I can perfectly understand that others don't share this
quite strict point of view.

Best regards,
  Seb

-- 
Sébastien Vauban


_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-09-20  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19 22:47 Query for S. Vauban Thomas S. Dye
2010-09-20  7:51 ` Sébastien Vauban [this message]
2010-09-20  8:18   ` Thomas S. Dye

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8762y0yhrc.fsf@mundaneum.com \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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/org-mode.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).