emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Johnny <yggdrasil@gmx.co.uk>
To: emacs-orgmode@gnu.org
Subject: Re: Freemind export and import question/suggestion (newlines problem)
Date: Sat, 18 Feb 2012 15:20:33 +0000	[thread overview]
Message-ID: <87ehts5fsu.fsf@gmx.co.uk> (raw)
In-Reply-To: <87lio1j7nb.fsf@gmx.co.uk> (Johnny's message of "Sat, 18 Feb 2012 00:40:40 +0000")

Johnny <yggdrasil@gmx.co.uk> writes:

> Hi,
> I am trying out the excellent freemind exporter/importer and am running
> into issues with long node names and newlines. 
> 1) Exporting org to freemind (node name length limitation?)
> In org-mode, none of the headlines can contain newlines, so occasionaly
> they get a bit long. This is not a (big) issue in org, but when exorting to
> freemind, I would like to limit the names to a maximum length, as the
> mindmap display in freemind need reasonably short node names to give a
> clear overview. It would be great to be able to do this with the
> exporter by setting a variable / giving a prefix number.
> 2) Importing freemind to org (remove newlines?)
> For now, I have manually split some lines in freemind to get a good
> mindmap, but then the issue is that when re-importing to org, the
> headlines are including the newline, hence the org-mode headings are
> broken. This may be easily done by replacing all newlines in the node
> name when importing, but being Lisp challenged I cannot find where in
> org-freemind.el this replacement should be done.
> 3) Importing freemind to org (centered nodes)
> I noticed also that nodes in freemind that were centered broke the org
> import fairly bad by splitting the node name over several lines with
> blank lines in between. And none of the textual lines were actually
> displayed as a headline. I don't really have an issue with this, as I
> can do without changing from the default alignment in freeming, but
> thought I'd include it in this writeup.
> If anyone has an idea of how to solve this or could point me in the
> right direction that would be great!

Of course, right after posting I found the setting in freemind to limit
node length [1]. The solution for now is to avoid using newlines altogether in the
node names. This means all node levels will have the same length, but
this is ok for me. 

Sorry for the noise!

[1] Under 'Tools -> Preferences' under the tab 'Defaults' there's a 'Max
    Node Width' that can be set.


      reply	other threads:[~2012-02-18 15:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18  0:40 Freemind export and import question/suggestion (newlines problem) Johnny
2012-02-18 15:20 ` Johnny [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:

  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=87ehts5fsu.fsf@gmx.co.uk \
    --to=yggdrasil@gmx.co.uk \
    --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).