emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting a subtree
Date: Thu, 19 Nov 2015 08:55:23 -0500	[thread overview]
Message-ID: <87vb8yum9g.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: 6sw6c7poz6gln8.fsf@pfdstudio.com

Peter Davis <pfd@pfdstudio.com> writes:

> Thanks for the tips. I was hoping this would be simple to answer. I
> don't really have hours of time to keep stopping and re-starting emacs
> with uncompiled org-mode files, with minimal startup, etc. If I get a
> chance, I'll post the details. Meanwhile, I'll live without this
> feature.
>

I understand the sentiment, but you will find out eventuallly that it
takes only a few minutes to do all that: the descriptions seem to make
it long and difficult but once you get down to brass tacks, it turns out
to be pretty simple ("it is easier done than said"). In particular, you
don't need to stop/start your current emacs: you can start a new one as
John described specially for this problem, do what you need to do to
reproduce the problem and kill it afterwards. It does take a little time
to come up with a minimal init file that sets up things, but there have
been examples posted on the list that you can adapt to your situation -
once you have one, just keep it around and modify it slightly for each
new situation.

In any case, the trouble here is that it does not seem to be
reproducible: at first sight at least, it seems to be related to your
particular setup, so nobody else can debug it.

And one more thing, now that I remember it: always provide versions
of your OS, emacs and org-mode. It is possible that the particular
version you are using exhibits the problem but earlier or later ones
don't. Of cource, if you update regularly, that is less of a concern,
but if you provide the version, then other people can try it with
that particular version (thanks to git, it's easy).

-- 
Nick

  reply	other threads:[~2015-11-19 13:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 13:32 Exporting a subtree Peter Davis
2015-11-19 13:55 ` Nick Dokos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-19 13:51 Peter Davis
2015-11-19 14:39 ` Nick Dokos
2015-11-18 20:43 Peter Davis
2015-11-18 22:30 ` John Hendy
2015-11-19  1:20   ` Peter Davis
2015-11-18 20:29 Peter Davis
2015-11-18 20:35 ` John Hendy
2015-11-18 20:51   ` Nick Dokos
2015-11-20 16:21 ` Brett Viren

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=87vb8yum9g.fsf@pierrot.dokosmarshall.org \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).