From: Nick Dokos <nicholas.dokos@hp.com>
To: rpgoldman@sift.info
Cc: nicholas.dokos@hp.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Request for suggestions including source code
Date: Wed, 04 May 2011 19:10:16 -0400 [thread overview]
Message-ID: <7002.1304550616@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Robert Goldman <rpgoldman@sift.info> of "Wed, 04 May 2011 17:01:51 CDT." <4DC1CCCF.5070403@sift.info>
Robert Goldman <rpgoldman@sift.info> wrote:
> On 5/4/11 May 4 -4:44 PM, Nick Dokos wrote:
>
> > So there you have it: a frivolous exercise, almost completely OT for the
> > list and an almost useless answer[fn:1].
>
> This actually was pretty helpful. The problem is, of course, that I
> can't rewrite all of my source code to be in 65-width lines, nor can I
> convince my colleagues to do so.
>
Precisely: that's why it was useless :-) I took a quick look at
Stevens's "Advanced Programming in the UNIX environment" (which I think
of as well-typeset) and I find that most of the time, he adheres to the
65-char limit - there are some comments that go up to 72 or so and stick
out a bit into the right margin. But I'm pretty sure he planned it to
the 65-char limit.
> So what I need now is some way to fix the verbatim environments that are
> produced by org-mode to use a smaller font. I.e., instead of trying to
> fix the source code to match char-width, fix the char-width to match the
> source code. Any idea how to do that?
>
Here is one possibility: create a verbfont.sty file like this:
--8<---------------cut here---------------start------------->8---
\makeatletter
\def\verbatim@font{\normalfont\scriptsize\ttfamily}
\makeatother
--8<---------------cut here---------------end--------------->8---
and add this to your org file:
--8<---------------cut here---------------start------------->8---
#+LATEX_HEADER: \usepackage{verbfont}
--8<---------------cut here---------------end--------------->8---
Instead of \scriptsize, you can use any of the ones defined in
size1X.clo (for some X). If you use \tiny, you should package a
magnifier with the book...
Nick
next prev parent reply other threads:[~2011-05-04 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 20:53 Request for suggestions including source code Robert Goldman
2011-05-04 21:13 ` Thomas S. Dye
2011-05-04 21:44 ` Nick Dokos
2011-05-04 22:01 ` Robert Goldman
2011-05-04 23:10 ` Nick Dokos [this message]
2011-05-05 0:11 ` Robert Goldman
2011-05-04 21:59 ` Robert Goldman
2011-05-04 22:23 ` Thomas S. Dye
2011-05-04 22:29 ` Robert Goldman
2011-05-04 22:49 ` brian powell
2011-05-05 17:07 ` Eric Schulte
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=7002.1304550616@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=rpgoldman@sift.info \
/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).