emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Thomas Plass <thunk2@arcor.de>
Cc: emacs-orgmode@gnu.org, michael <m.schoenwaelder@posteo.de>
Subject: Re: Vertical bars in org file break export to ics
Date: Thu, 30 May 2019 15:02:51 +0200	[thread overview]
Message-ID: <87blzk9jt0.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <23791.40090.543113.153629@AGAME7.local> (Thomas Plass's message of "Thu, 30 May 2019 11:04:26 +0200")

Hello,

thunk2@arcor.de (Thomas Plass) writes:

> michael wrote at 08:57 on May 30, 2019:
> : for the following *.org file running org-icalendar-export-to-ics will fail
> : with "Args out of range: [nil nil], 2".
> : 
> : * This is a test
> :   <2020-01-01 Mi>
> : 
> : | | |
> : | | | | |
>
> Org recognizes the last two lines as a genuine Org table (with two
> rows), not as a collection of vertical bars having a completely
> different meaning.
>
> Making the export more robust by gracefully handling unequal
> numbers of columns won't help you as I guess you wish to have the
> vertical bars exported verbatim (which Org won't do).

You're right.

Meanwhile, I made export more robust in this case.

> Your best bet is probably to choose an unreserved character for use in
> the graphics, possibly just before exporting.  Unicode code point
> 0xFFE4 FULLWIDTH BROKEN BAR looks similar.

Or use ": ", i.e., fixed-width area, or \vert as the first bar.

Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2019-05-30 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  6:57 Vertical bars in org file break export to ics michael
2019-05-30  8:31 ` Fraga, Eric
2019-05-30  9:04 ` Thomas Plass
2019-05-30 13:02   ` Nicolas Goaziou [this message]

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=87blzk9jt0.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=m.schoenwaelder@posteo.de \
    --cc=thunk2@arcor.de \
    /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).