emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: William Denton <wtd@pobox.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Anyone doing any fancy customizations of source blocks?
Date: Tue, 2 Jun 2020 15:23:31 -0400	[thread overview]
Message-ID: <CAJ51ETqc6mBdOzVv=0qmGEh7og51zHvgR-yAHH-aNkLDEZdsSw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.2006021437310.2505@shell.miskatonic.org>

[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]

Here is one approach:


I feel like I have seen some work that used ruby and python icons as
displays over #+begin_src, but I can't find it now.


Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213

On Tue, Jun 2, 2020 at 2:54 PM William Denton <wtd@pobox.com> wrote:

> Is anyone doing any fancy formatting of source blocks, such as putting a
> line
> in the left fringe, or a box around them, or having some interesting
> background?
> I ask because I recently changed the theme I use to get the dark Solarized
> look
> I like,[1] and all of a sudden my #+begin_src lines were underlined and
> #+end_src had a line above it.  These come from org-block-begin-line and
> org-block-end-line, and are shown here, but I'd never noticed them in
> documentation or had them on my screen before:
> https://orgmode.org/worg/org-contrib/babel/examples/fontify-src-code-blocks.html
> Aside from fontifying the source blocks I've never done anything special
> about
> them (except wonder how I ever did anything without them), but seeing this
> made
> me wonder if anyone here has really customized them so they look like
> medieval
> manuscripts or something from a futuristic video game.  (If any of that is
> possible---but in Emacs, anything is possible ...)
> Bill
> [1] Now I'm using https://github.com/bbatsov/solarized-emacs, with
> variable
> pitch turned off and Org headline resizing turned off.
> --
> William Denton :: Toronto, Canada   ---   Listening to Art:
> https://listeningtoart.org/
> https://www.miskatonic.org/         ---   GHG.EARTH: https://ghg.earth/
> Caveat lector.                      ---   STAPLR: https://staplr.org/

[-- Attachment #2: Type: text/html, Size: 3180 bytes --]

  reply	other threads:[~2020-06-02 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 18:54 Anyone doing any fancy customizations of source blocks? William Denton
2020-06-02 19:23 ` John Kitchin [this message]
2020-06-03 18:23   ` Diego Zamboni
2020-06-03 20:09     ` briangpowell .
2020-06-04  6:29       ` Diego Zamboni
2020-06-19  4:04     ` William Denton
2020-06-19  7:19       ` Diego Zamboni via General discussions about Org-mode.
2020-06-19 12:53       ` Norman Tovey-Walsh
2020-06-19 13:12         ` Joost Kremers
2020-06-19 14:21           ` Norman Tovey-Walsh
2020-06-08 14:29   ` Rasmus

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:

  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='CAJ51ETqc6mBdOzVv=0qmGEh7og51zHvgR-yAHH-aNkLDEZdsSw@mail.gmail.com' \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=wtd@pobox.com \


* 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


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).