emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Creating hline in table from source block?
Date: Tue, 26 Nov 2013 09:54:10 +0100	[thread overview]
Message-ID: <8738mjtufh.fsf@gmx.us> (raw)
In-Reply-To: 87pppnoaej.fsf@hornfels.zedat.fu-berlin.de

"Loris Bennett" <loris.bennett@fu-berlin.de> writes:

> So Achim's suggestion of using ":results raw" might be the way to go
> (once I've worked out what the sed bit is doing ...)
> However, the table will ultimately be around 40000 lines long,
> so from a performance point of view it would be nice not to have to pipe
> the whole thing through sed, particularly as the files are on a remote
> server.  Having said that though, it is not a performance-critical
> application.
> So maybe I'll look at Rasmus' simpler suggestion (my lisp skill are
> unfortunately not quite up to the "fun" variant ...)

The "fun" variant works with any table.  You just specify a list of
positions where you want hlines, e.g. '(0 1 last) or '(0 1 -1).

> How complex would the elisp version of my grep and awk above be?  Just
> having one code block would be a little neater from my point of view.

If you use :post you can keep your utility functions in a :noexport:
section at the bottom of your file (or even in a library-of-babel (see
org-babel-lob-ingest)) and you don't litter your code with unnecessary
stuff.  It's also usable across blocks.  

When the facts change, I change my mind. What do you do, sir?

  reply	other threads:[~2013-11-26  8:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 10:52 Creating hline in table from source block? Loris Bennett
2013-11-25 20:13 ` Achim Gratz
2013-11-25 20:43   ` Achim Gratz
2013-11-26 16:40     ` Daniel E. Doherty
2013-11-25 21:38 ` Rasmus
2013-11-26  0:47   ` Rasmus
2013-11-26  2:41 ` Eric Schulte
2013-11-26  8:05   ` Loris Bennett
2013-11-26  8:54     ` Rasmus [this message]
2013-11-26 13:14     ` Eric Schulte
2013-11-26 14:23       ` Loris Bennett
2013-11-26 20:07         ` Achim Gratz

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=8738mjtufh.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \


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