From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thomas S. Dye" Subject: Re: Re: Query for S. Vauban Date: Sun, 19 Sep 2010 22:18:25 -1000 Message-ID: <9878A6A7-2682-49E9-9FD8-058AACB53FBF@tsdye.com> References: <2551CCE1-8C18-4ACA-A908-5725098C398C@tsdye.com> <8762y0yhrc.fsf@mundaneum.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=58888 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oxba4-0002Tk-LA for emacs-orgmode@gnu.org; Mon, 20 Sep 2010 04:18:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oxba2-0006mn-Ti for emacs-orgmode@gnu.org; Mon, 20 Sep 2010 04:18:32 -0400 Received: from oproxy2-pub.bluehost.com ([67.222.39.60]:51958) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1Oxba2-0006mY-MR for emacs-orgmode@gnu.org; Mon, 20 Sep 2010 04:18:30 -0400 In-Reply-To: <8762y0yhrc.fsf@mundaneum.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?ISO-8859-1?Q?S=E9bastien_Vauban?= Cc: emacs-orgmode@gnu.org Aloha Sebastien, Yes, that makes perfect sense for situations where the line length is =20= specified in advance. Changing the font size to get a particular line length is an =20 interesting idea. My sense is that typographers would look first to =20 change the size of the text block. I can see benefits to both =20 approaches. Thanks for your help. All the best, Tom On Sep 19, 2010, at 9:51 PM, S=E9bastien Vauban wrote: > Aloha Thomas, > > "Thomas S. Dye" wrote: >> While using the listings setup you sent to the list a while back, I =20= >> found >> this line and wondered why you chose not to break long lines? >> >> breaklines=3Dfalse, %!! don't break long lines of code >> >> The !! in the comment led me to believe you might have some strong =20= >> reasons. > > You're right guessing that the !! do have a meaning. Yes, they mean: =20= > this is > not a standard comment, that's something you really must be aware =20 > of... > > I guess I did that for 2 reasons: > > - be sure to easy locate what could be a wrong setting, in case I =20 > 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 =20= > of a crazy > perfectionist. I want the things to be perfectly output, and my =20 > reports to be > of great quality on the presentation side as well -- I cannot easily =20= > judge on > my own for the contents ;-) > > One of the constraints I use in my daily life is: no more than 80 =20 > rows in > files, be it text (Org) or code (.emacs, bash scripts, etc.). In =20 > fact, even > not more than 78, when possible. I have Emacs column markers in =20 > 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, =20 > and have > chosen the right font size (in LaTeX) so that my code is displayed =20 > in the > LaTeX PDF with the biggest font possible, so that an 80-wide line is =20= > 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 =20 > explicitly > chosen the second one, with the above setting in Listings. Why? =20 > Because I > consider that lines longer than 80 characters are bad, and that *I* =20= > have to > correct them somehow. I don't want to rest on Listings to rearrange =20= > my code. > Plus, Listings does not do it good, if I remember good. The wrapped =20= > text never > won't be placed in the way you would do it if you had to break the =20 > line > yourself, explicitly. > > So, in a nutshell, by forbidding long lines to be wrapped by =20 > Listings, I have > a clear indication that my code is too wide at some spots, and that =20= > 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 =20= > I'm clear > about *my* objectives; I can perfectly understand that others don't =20= > share this > quite strict point of view. > > Best regards, > Seb > > --=20 > S=E9bastien Vauban > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode