From: Tim Cross <theophilusx@gmail.com>
To: "Barton, Mark" <Mark.Barton@disney.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
"Sébastien Gendre" <seb@k-7.ch>
Subject: Re: Code blocks and quotes export style
Date: Mon, 14 Mar 2022 08:13:03 +1100 [thread overview]
Message-ID: <87ilshy2b7.fsf@gmail.com> (raw)
In-Reply-To: <B23B82AA-92DC-4201-B9DB-682743BF59DF@disney.com>
"Barton, Mark" <Mark.Barton@disney.com> writes:
> I manually check the pdf to see if it fits and use a code formatter to get the
> line widths shorter. I use blacken for python and sqlformat for SQL within
> Emacs. Even then I still hit limits where I recently changed to font size to
> small for the code blocks.
>
> I use minted for syntax highlighting of code blocks.
> #+LaTeX_HEADER: \usepackage{minted}
>
> I set a local variable for org using minted to change the fontsize.
> # Local Variables:
> # org-latex-minted-options: (("fontsize" "\\small"))
> # End:
>
That is basically what I do as well. I use minted and a smaller font for
code listings. I also ensure that when programming, I use a fill column
of 80.
In this day of large monitors, a fill column of 80 for programming
languages can often seem frustrating as it means less code in a
'screen' (window). Increasing fill column to (lets say) 100 can work
well, until it comes time to generate documentation and PDFs etc. Then I
remember why 80 is a better default!
I do use local variables more these days and will set a larger fill
column setting for code when I know I won't be needing to print it or
use it in Latex, but the default is 80 so that whenever I do org blocks,
things wrap at a width which works better for export to PDF etc.
next prev parent reply other threads:[~2022-03-13 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 10:54 Code blocks and quotes export style Sébastien Gendre
2022-03-13 16:06 ` Kaushal Modi
2022-03-13 18:39 ` Juan Manuel Macías
2022-03-14 12:50 ` Max Nikulin
2022-03-14 18:09 ` Juan Manuel Macías
2022-03-13 18:55 ` Barton, Mark
2022-03-13 21:13 ` Tim Cross [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-13 16:22 autofrettage
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=87ilshy2b7.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=Mark.Barton@disney.com \
--cc=emacs-orgmode@gnu.org \
--cc=seb@k-7.ch \
/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).