emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dov Grobgeld <dov.grobgeld@gmail.com>
To: Bastien <bzg@altern.org>
Cc: "François Pinard" <pinard@iro.umontreal.ca>, emacs-orgmode@gnu.org
Subject: Re: Python code for producing Org tables
Date: Mon, 24 Dec 2012 15:26:30 +0200	[thread overview]
Message-ID: <CA++fsGE+X4uO_9XjqY0wZOaxi1iA6ss8QbjN-xfZuLN7o2rekg@mail.gmail.com> (raw)
In-Reply-To: <87sj6vsifi.fsf@bzg.ath.cx>

Nice! I've needed that often. But please add licensing information to
the code to make clear in what contexts it may be used.

Regards,
Dov

On Mon, Dec 24, 2012 at 3:12 PM, Bastien <bzg@altern.org> wrote:
>
> Hi François,
>
> François Pinard <pinard@iro.umontreal.ca> writes:
>
> > I do not know, and should check indeed.  Yet, even then, it does not
> > mean Org tables could not do better than standard practice! :-)
>
> Would you like something like
>
> | 3.1 |
> | 3.1415 |
>
> be aligned/modified as
>
> | 3.1000 |
> | 3.1415 |
>
> ?
>
> I personally wouldn't like this, but I'm curious.
>
> >> If so, this is a nice Elisp challenge for anyone willing to
> >> implement it :)
> >
> > I'd tackle it myself, yet if I do it before a few weeks, it'd mean I'm
> > toying rather than doing what I should rather be doing...  Sigh!
>
> Don't worry, once you'll dive into `org-table-align' chances are that
> you will feel like "working" instead of "toying" :)
>
> Bonnes fêtes !
>
> --
>  Bastien
>

  reply	other threads:[~2012-12-24 13:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19  3:43 Python code for producing Org tables François Pinard
2012-12-24  0:35 ` Bastien
2012-12-24 12:39   ` François Pinard
2012-12-24 13:12     ` Bastien
2012-12-24 13:26       ` Dov Grobgeld [this message]
2012-12-25 13:10         ` François Pinard
2012-12-25 13:04       ` François Pinard

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=CA++fsGE+X4uO_9XjqY0wZOaxi1iA6ss8QbjN-xfZuLN7o2rekg@mail.gmail.com \
    --to=dov.grobgeld@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \
    /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).