org-export-select-tags

org-export-select-tags

[SW]

I have an org-file with many headlines of various levels, but no tags. I tagged
one top-level headline with :export: and exported to LaTeX with C-c C-e l. The
tagged headline and everything below it was exported, but so was the first
headline (and everything below it) in the org file, even though it did not have
any tags. The *only* tag is :exported: on the headline I want exported.

Re: org-export-select-tags

[Nick Dokos]

SW <sabrewolfy@gmail.com> wrote:

> I have an org-file with many headlines of various levels, but no tags. I tagged
> one top-level headline with :export: and exported to LaTeX with C-c C-e l. The
> tagged headline and everything below it was exported, but so was the first
> headline (and everything below it) in the org file, even though it did not have
> any tags. The *only* tag is :exported: on the headline I want exported.
> 
> 

Can't reproduce it here: Org-mode version 7.8.11
(release_7.8.11-107-ga69f4b @ /home/nick/elisp/org-mode/lisp/)
Tried both the old and the new exporter, exporting to ascii, latex
and html of the following file:

--8<---------------cut here---------------start------------->8---

* foo

** foo1
** foo2

* bar														:export:
** bar1
** bar2

* baz
** baz1
--8<---------------cut here---------------end--------------->8---

and I only get the bar tree exported in all cases.

NB: the tag should be ``:export:'', not ``:exported:'' if you are using
the default settings.

Nick

Re: org-export-select-tags

[SW]

Nick Dokos <nicholas.dokos <at> hp.com> writes:

> Can't reproduce it here: Org-mode version 7.8.11
> (release_7.8.11-107-ga69f4b @ /home/nick/elisp/org-mode/lisp/)
> Tried both the old and the new exporter, exporting to ascii, latex
> and html of the following file:
> 
...
> 
> and I only get the bar tree exported in all cases.
> 
> NB: the tag should be ``:export:'', not ``:exported:'' if you are using
> the default settings.

Thanks. I *can* reproduce it (exporting to LaTeX) with your example above. If I
export that example, I get headlines "foo" and "bar" in the export. I'm using
Org-mode version 7.8.11-1 and haven't (to my knowledge) adjusted any export
settings.

Re: org-export-select-tags

[Suvayu Ali]

Hi,

On Mon, Jul 09, 2012 at 08:54:53AM +0000, SW wrote:
> Nick Dokos <nicholas.dokos <at> hp.com> writes:
> 
> > Can't reproduce it here: Org-mode version 7.8.11
> > (release_7.8.11-107-ga69f4b @ /home/nick/elisp/org-mode/lisp/)
> > Tried both the old and the new exporter, exporting to ascii, latex
> > and html of the following file:
> > 
> ...
> > 
> > and I only get the bar tree exported in all cases.
> > 
> > NB: the tag should be ``:export:'', not ``:exported:'' if you are using
> > the default settings.
> 
> Thanks. I *can* reproduce it (exporting to LaTeX) with your example above. If I
> export that example, I get headlines "foo" and "bar" in the export. I'm using
> Org-mode version 7.8.11-1 and haven't (to my knowledge) adjusted any export
> settings.
> 

Have you tried with a minimal setup? It's quite easy. Some instructions
are included in the Org mode manual[1]. It also helps if you provide a
minimal example org file, we like to call that an ECM[2] on the list.

Hope this helps.


Footnotes:

[1] <http://orgmode.org/manual/Feedback.html#Feedback>

[2] <http://orgmode.org/worg/org-faq.html#ecm>

-- 
Suvayu

Open source is the future. It sets us free.

Re: org-export-select-tags

[SW]

Suvayu Ali <fatkasuvayu+linux <at> gmail.com> writes:

> Have you tried with a minimal setup? It's quite easy. Some instructions
> are included in the Org mode manual[1]. It also helps if you provide a
> minimal example org file, we like to call that an ECM[2] on the list.

I have already confirmed that the problem exists in the minimal example which
Nick Dokos posted earlier.

Re: org-export-select-tags

[Nick Dokos]

SW <sabrewolfy@gmail.com> wrote:

> Suvayu Ali <fatkasuvayu+linux <at> gmail.com> writes:
> 
> > Have you tried with a minimal setup? It's quite easy. Some instructions
> > are included in the Org mode manual[1]. It also helps if you provide a
> > minimal example org file, we like to call that an ECM[2] on the list.
> 
> I have already confirmed that the problem exists in the minimal example which
> Nick Dokos posted earlier.
> 

Well, so far nobody else can reproduce it, so the working assumption is
that it is an artifact of either the version you are running or your
configuration. As Suvayu suggests, a minimal org setup[fn:1] would
distinguish between the two. Otherwise, as Jambunathan suggests (and
/pace/ your doubts), it's probably a bug in the version you are using
and you should upgrade to latest - or downgrade to the current maint
version, release_7.8.10-14-gaf6cb0b (which I tried with the old exporter
and latex: can't reproduce it there either.) If you are not going to keep
up with latest in the master branch, then sticking to maint is the best
policy.

Nick


Footnotes:

[fn:1] NB: this is different from just a minimal example. It involves
setting up a bare-bones .emacs and then starting emacs like this

          emacs -q --load /path/to/minimal/.emacs /path/to/minimal/example.org

and trying the export. I and others have posted examples of the process
on the list. See e.g.

          http://thread.gmane.org/gmane.emacs.orgmode/56734/focus=56752

Re: org-export-select-tags

[Nick Dokos]

Nick Dokos <nicholas.dokos@hp.com> wrote:

> Footnotes:
> 
> [fn:1] NB: this is different from just a minimal example. It involves
> setting up a bare-bones .emacs and then starting emacs like this
> 
>           emacs -q --load /path/to/minimal/.emacs /path/to/minimal/example.org
> 
> and trying the export.

... and if that breaks, try also with -Q in place of -q, to eliminate interactions
with the site file as a possible source of the problem.

Re: org-export-select-tags

[SW]

Nick Dokos <nicholas.dokos <at> hp.com> writes:

> Well, so far nobody else can reproduce it, so the working assumption is
> that it is an artifact of either the version you are running or your
> configuration. As Suvayu suggests, a minimal org setup[fn:1] would
> distinguish between the two. Otherwise, as Jambunathan suggests (and
> /pace/ your doubts), it's probably a bug in the version you are using
> and you should upgrade to latest - or downgrade to the current maint
> version, release_7.8.10-14-gaf6cb0b (which I tried with the old exporter
> and latex: can't reproduce it there either.) If you are not going to keep
> up with latest in the master branch, then sticking to maint is the best
> policy.

I am not familiar with downloading any version other than the one in my distro's
repository or the Debian version from orgmode.org. I will look into getting a
version later than "7.8.11-1", which is what my version is. I tested with the
minimal file before:

* Headline1
* Headline1     :export:

and exported from "emacs -Q" and *both* headlines were exported. Therefore, it
has to be something in the version I am using. Once I have figured out how to
install the snapshot I downloaded, I will post back here.

[FWIW, this link:

http://orgmode.org/worg/org-faq.php#keeping-current-with-Org%20mode-development

linked from here:

http://orgmode.org/org-mode-download.html

is broken.]

Re: org-export-select-tags

[Nick Dokos]

SW <sabrewolfy@gmail.com> wrote:


> [FWIW, this link:
> 
> http://orgmode.org/worg/org-faq.php#keeping-current-with-Org%20mode-development
> 
> linked from here:
> 
> http://orgmode.org/org-mode-download.html
> 
> is broken.]
> 

Yup, it should be a hyphen, not a space:

     http://orgmode.org/worg/org-faq.php#keeping-current-with-Org-mode-development


Nick

Re: org-export-select-tags

[SW]

SW <sabrewolfy <at> gmail.com> writes:
 
> I am not familiar with downloading any version other than the
> one in my distro's repository or the Debian version from
> orgmode.org. I will look into getting a version later than
> "7.8.11-1", which is what my version is. I tested with the
> minimal file before:
> 
> * Headline1
> * Headline1     :export:
> 
> and exported from "emacs -Q" and *both* headlines were exported.
> Therefore, it has to be something in the version I am using.
> Once I have figured out how to install the snapshot I downloaded,
> I will post back here.

Nevermind. Thanks anyway. I can't install the new version (some error about
emacs version N/A) and life's too short -- and I don't have the time (org-mode
is supposed to save time:)) to waste hours trying to install this. I'll live
with the bug until I can get a downloadable version. This triviality has taken
up too much of my time already. Thanks.
 

Re: org-export-select-tags

[SW]

(1) I extracted the latest tar.gz file downloaded from org-mode.org
(org-mode-9d16365c201201679b190c601c8d32e06530a21a.tar.gz) to /tmp/org-mode.

(2) I loaded Emacs with "emacs -Q" and then entered:

(setq load-path (cons "/tmp/org-mode/lisp" load-path))

into the scratch buffer.

(4) I marked it and ran "eval-region". "M-x org-version" reported "N/A N/A"
instead of 7.8.11-1.

(5) I then tried the minimal file and exported to LaTeX and it *STILL* exports
Headline1 and Headline2:

-------------
* Headline1
* Headline2    :export:
-------------

(6) I repeated by evaluating:

(add-to-list 'load-path "/tmp/org-mode/lisp")
(require 'org-install)

in the scratch buffer and exporting again. As above.

I don't know what more I can do on this issue.

Re: org-export-select-tags

[Nick Dokos]

SW <sabrewolfy@gmail.com> wrote:

> (1) I extracted the latest tar.gz file downloaded from org-mode.org
> (org-mode-9d16365c201201679b190c601c8d32e06530a21a.tar.gz) to /tmp/org-mode.
> 
> (2) I loaded Emacs with "emacs -Q" and then entered:
> 
> (setq load-path (cons "/tmp/org-mode/lisp" load-path))
> 
> into the scratch buffer.
> 
> (4) I marked it and ran "eval-region". "M-x org-version" reported "N/A N/A"
> instead of 7.8.11-1.
> 
> (5) I then tried the minimal file and exported to LaTeX and it *STILL* exports
> Headline1 and Headline2:
> 
> -------------
> * Headline1
> * Headline2    :export:
> -------------
> 
> (6) I repeated by evaluating:
> 
> (add-to-list 'load-path "/tmp/org-mode/lisp")
> (require 'org-install)
> 
> in the scratch buffer and exporting again. As above.
> 
> I don't know what more I can do on this issue.
> 
> 

What does M-x locate-library RET org-install RET say?

Nick

Re: org-export-select-tags

[SW]

Nick Dokos <nicholas.dokos <at> hp.com> writes:

> What does M-x locate-library RET org-install RET say?

Library is file /usr/share/emacs/23.2/site-lisp/org-mode/org-install.elc

(The latest version download is now different -- it no longer says version N/A
N/A. It now says:

Org-mode version N/A-fixup (N/A-fixup !!check installation!! @ mixed
installation! /usr/share/emacs/23.2/site-lisp/org-mode/ and /tmp/org-mode/lisp/)

which it didn't say before.)

Because I could not get the latest version to compile, I tried running it
directly from the /tmp folder according to the instructions here:

http://orgmode.org/manual/Installation.html

with:

(setq load-path (cons "~/path/to/orgdir/lisp" load-path))

I didn't add it to .emacs because I am launching with -Q.

Clearly that has probably not worked.

Re: org-export-select-tags

[Achim Gratz]

SW writes:
> Library is file /usr/share/emacs/23.2/site-lisp/org-mode/org-install.elc

That is a completely borked installation (not your fault quite likely),
org-install.el should never be byte-compiled.  I see Sebastien is the
package maintainer, it would be nice if this (and actually a few other
things) could be fixed.

> Org-mode version N/A-fixup (N/A-fixup !!check installation!! @ mixed
> installation! /usr/share/emacs/23.2/site-lisp/org-mode/ and /tmp/org-mode/lisp/)

Good, that means it has at least loaded org.el from current master.

> which it didn't say before.)
>
> Because I could not get the latest version to compile

Which part of

make uncompiled

didn't work?  That shouldn't give any problems on a stock Debian system.

> Clearly that has probably not worked.

It has worked, sort-of.  Since you're working from a raw copy of the Git
worktree, you must generate the autoload files.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: org-export-select-tags

[Jambunathan K]

While in your org buffer do a 

C-c C-e t

You will now have a set of headers (as below).  Specifically note the
select and exclude tags directive.

Now do a export and report what happens.

Just to be sure, do a M-x locate-library RET org RET to make sure the
path is right.

#+TITLE:     1.org
#+AUTHOR:    Jambunathan K
#+EMAIL:     kjambunathan@gmail.com
#+DATE:      2012-07-10 Tue
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE:  en
#+OPTIONS:   H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS:   TeX:t LaTeX:dvipng skip:nil d:t todo:t pri:nil tags:t

#+EXPORT_SELECT_TAGS: export  <===================
#+EXPORT_EXCLUDE_TAGS: noexport <=================
#+LINK_UP:   
#+LINK_HOME: 
#+XSLT:



> (1) I extracted the latest tar.gz file downloaded from org-mode.org
> (org-mode-9d16365c201201679b190c601c8d32e06530a21a.tar.gz) to /tmp/org-mode.
>
> (2) I loaded Emacs with "emacs -Q" and then entered:
>
> (setq load-path (cons "/tmp/org-mode/lisp" load-path))
>
> into the scratch buffer.
>
> (4) I marked it and ran "eval-region". "M-x org-version" reported "N/A N/A"
> instead of 7.8.11-1.
>
> (5) I then tried the minimal file and exported to LaTeX and it *STILL* exports
> Headline1 and Headline2:
>
> -------------
> * Headline1
> * Headline2    :export:
> -------------
>
> (6) I repeated by evaluating:
>
> (add-to-list 'load-path "/tmp/org-mode/lisp")
> (require 'org-install)
>
> in the scratch buffer and exporting again. As above.
>
> I don't know what more I can do on this issue.
>
>
>

-- 

Re: org-export-select-tags

[SW]

Jambunathan K <kjambunathan <at> gmail.com> writes:

> 
> 
> While in your org buffer do a 
> 
> C-c C-e t

#+TITLE:     testing.org
#+AUTHOR:    
#+EMAIL:     
#+DATE:      2012-07-09 Mon
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE:  en
#+OPTIONS:   H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS:   TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0
path:http://orgmode.org/org-info.js
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:   
#+LINK_HOME: 
#+XSLT:

Looks fine to me ...

Re: org-export-select-tags

[Jambunathan K]

> Looks fine to me ...

What does that mean? Are you getting the behaviour you are expecting.

If you want to strip a tree from export, you can use the COMMENT
keyword.  I think the speed command is ";" or something.

Note: With template not in place, I could see the problem that you
reported.  Once the template is installed I got the right behaviour. Now
if I remove the templace and revert the buffer I get the "expected"
behaviour.

I believe some variables get set by installing those tags which are not
subsequently un-done.
-- 

Re: org-export-select-tags

[SW]

Jambunathan K <kjambunathan <at> gmail.com> writes:

> 
> > Looks fine to me ...
> 
> What does that mean? Are you getting the behaviour you are expecting.

What I meant is that the export tags *are* correctly set in the template, so
only the :export: headlines *should* be exported, which, despite that template
being correct, is *not* what I am getting.

I've "solved" it by inserting a blank line at the top of the file. If I do that,
then only the :export: headlines are exported.

Re: org-export-select-tags

[suvayu ali]

On Mon, Jul 9, 2012 at 10:01 PM, SW <sabrewolfy@gmail.com> wrote:
> [FWIW, this link:
>
> http://orgmode.org/worg/org-faq.php#keeping-current-with-Org%20mode-development
>
> linked from here:
>
> http://orgmode.org/org-mode-download.html
>
> is broken.]

This is the correct link: <http://orgmode.org/worg/org-faq.html#Keeping-current>

HTH

-- 
Suvayu

Open source is the future. It sets us free.

Re: org-export-select-tags

[SW]

Suvayu Ali <fatkasuvayu+linux <at> gmail.com> writes:

> Have you tried with a minimal setup? It's quite easy. Some instructions
> are included in the Org mode manual[1]. It also helps if you provide a
> minimal example org file, we like to call that an ECM[2] on the list.

If you would like a minimum example which is different to Nick's:

-------------
* Headline1
* Headline2
-------------

Export with C-c C-e l

This exports all three headlines. Modify as follows:

-------------
* Headline1
* Headline2      :export:
-------------

and export in the same way. This exports Headline1 and Headline2.

Modify:

-------------
* Headline1      :export:
* Headline2
-------------

and export. This exports only Headline1.

Re: org-export-select-tags

[SW]

Correction to previous post:

"This exports all three headlines. Modify as follows:"

should read:

"This exports all *two* headlines. Modify as follows:"

Re: org-export-select-tags

[Jambunathan K]

> I'm using Org-mode version 7.8.11-1

7.8.11-1 is very old.  Upgrade and problem will disappear.

-- 

Re: org-export-select-tags

[SW]

Jambunathan K <kjambunathan <at> gmail.com> writes:

> 
> 
> > I'm using Org-mode version 7.8.11-1
> 
> 7.8.11-1 is very old.  Upgrade and problem will disappear.
> 

From the org-mode download page right now:

"Current Version: Org 7.8.11"

How is 7.8.11 very old? Which version should I upgrade to?

Re: org-export-select-tags

[Jambunathan K]

SW <sabrewolfy@gmail.com> writes:

> Jambunathan K <kjambunathan <at> gmail.com> writes:
>
>> 
>> 
>> > I'm using Org-mode version 7.8.11-1
>> 
>> 7.8.11-1 is very old.  Upgrade and problem will disappear.
>> 
>
> From the org-mode download page right now:
>
> "Current Version: Org 7.8.11"
>
> How is 7.8.11 very old? Which version should I upgrade to?

How about something in the range of 130+ - say release_7.8.11-135?


>
>
>
>

-- 

Re: org-export-select-tags

[SW]

Jambunathan K <kjambunathan <at> gmail.com> writes:

> How about something in the range of 130+ - say release_7.8.11-135?

Unless there is something related to exporting and possibly
org-export-select-tags, I'm not sure this would help. A search here:

http://orgmode.org/w/?p=org-mode.git&a=search&h=HEAD&st=commit&s=org-export-select-tags

indicates the last change in this regard in February 2012, prior to 7.8.11. Have
you tested the minimal example with 7.8.11-135?

Re: org-export-select-tags

[Jambunathan K]

> I'm not sure this would help.

Oh, OK.
-- 

Re: org-export-select-tags

[Bastien]

SW <sabrewolfy@gmail.com> writes:

>> Can't reproduce it here: Org-mode version 7.8.11
>> (release_7.8.11-107-ga69f4b @ /home/nick/elisp/org-mode/lisp/)
>> Tried both the old and the new exporter, exporting to ascii, latex
>> and html of the following file:
>> 
> ...
>> 
>> and I only get the bar tree exported in all cases.
>> 
>> NB: the tag should be ``:export:'', not ``:exported:'' if you are using
>> the default settings.
>
> Thanks. I *can* reproduce it (exporting to LaTeX) with your example
> above.

I can't reproduce it.

Do you have any configuration related to org-export-*-tags?

-- 
 Bastien

Re: org-export-select-tags

[SW]

SW <sabrewolfy <at> gmail.com> writes:

> I have an org-file with many headlines of various levels, but no tags. I tagged
> one top-level headline with :export: and exported to LaTeX with C-c C-e l. The
> tagged headline and everything below it was exported, but so was the first
> headline (and everything below it) in the org file, even though it did not have
> any tags. The *only* tag is :exported: on the headline I want exported.

*A work-around:* If the first line of the Org file is blank/empty, *then* *only*
the headlines with tag :export: are exported. Instead of:

--------------------
* Headline1
* Headline2     :export:
--------------------

use:

--------------------

* Headline1
* Headline2     :export:
--------------------

*"Solved"*

Re: org-export-select-tags

[Jambunathan K]

I can duplicate what you say.  May be it is a bug...

ps: Text is no text with no whitespaces.  All along we have been
focussed on text, when we should actually have been focussed on the
whitespace (or in this curious case, the missing whitepace)

> SW <sabrewolfy <at> gmail.com> writes:
>
>> I have an org-file with many headlines of various levels, but no tags. I tagged
>> one top-level headline with :export: and exported to LaTeX with C-c C-e l. The
>> tagged headline and everything below it was exported, but so was the first
>> headline (and everything below it) in the org file, even though it did not have
>> any tags. The *only* tag is :exported: on the headline I want exported.
>
> *A work-around:* If the first line of the Org file is blank/empty, *then* *only*
> the headlines with tag :export: are exported. Instead of:
>
> --------------------
> * Headline1
> * Headline2     :export:
> --------------------
>
> use:
>
> --------------------
>
> * Headline1
> * Headline2     :export:
> --------------------
>
> *"Solved"*

-- 

Re: org-export-select-tags

[SW]

Jambunathan K <kjambunathan <at> gmail.com> writes:

> I can duplicate what you say.  May be it is a bug...
> 
> ps: Text is no text with no whitespaces.  All along we have been
> focussed on text, when we should actually have been focussed on the
> whitespace (or in this curious case, the missing whitepace)

"Should" all Org files start with blank line? You refer to the "missing
whitespace" as though it should be there?

If the first line of the file is actually a line of dashes (-------), as I used
to mark the starting "cut" line of my examples, the export is still broken.

The export only works if the first line is actually a blank line.

Re: org-export-select-tags

[Nick Dokos]

SW <sabrewolfy@gmail.com> wrote:

> SW <sabrewolfy <at> gmail.com> writes:
> 
> > I have an org-file with many headlines of various levels, but no tags. I tagged
> > one top-level headline with :export: and exported to LaTeX with C-c C-e l. The
> > tagged headline and everything below it was exported, but so was the first
> > headline (and everything below it) in the org file, even though it did not have
> > any tags. The *only* tag is :exported: on the headline I want exported.
> 
> *A work-around:* If the first line of the Org file is blank/empty, *then* *only*
> the headlines with tag :export: are exported. Instead of:
> 
> --------------------
> * Headline1
> * Headline2     :export:
> --------------------
> 
> use:
> 
> --------------------
> 
> * Headline1
> * Headline2     :export:
> --------------------
> 
> *"Solved"*
> 

I can confirm that without the empty line the first subtree gets
exported as well as the (tagged) second one (but not the third one in my
minimal example). That's a bug.

But the minimal example I posted *did* include the initial empty line;
nevertheless you reported reproducing the problem with it: how come?

Re: org-export-select-tags

[SW]

Nick Dokos <nicholas.dokos <at> hp.com> writes:

> I can confirm that without the empty line the first subtree gets
> exported as well as the (tagged) second one (but not the third one in my
> minimal example). That's a bug.
> 
> But the minimal example I posted *did* include the initial empty line;
> nevertheless you reported reproducing the problem with it: how come?

That was my fault. I recall seeing other blank lines elsewhere in your example,
so I must have deleted them all. Apologies for the confusion. I personally never
have such blank lines in a document, so it was a force of habit.

Why *did* you start that example with a blank line anyway?

Re: org-export-select-tags

[SW]

SW <sabrewolfy <at> gmail.com> writes:

> That was my fault. I recall seeing other blank lines elsewhere in your
> example, so I must have deleted them all. Apologies for the confusion.
> I personally never have such blank lines in a document, so it was a
> force of habit.

> Why *did* you start that example with a blank line anyway?

Having said that, I posted my example *without* the opening blank line many
times in this thread :)

Re: org-export-select-tags

[Nick Dokos]

SW <sabrewolfy@gmail.com> wrote:

> SW <sabrewolfy <at> gmail.com> writes:
> 
> > That was my fault. I recall seeing other blank lines elsewhere in your
> > example, so I must have deleted them all. Apologies for the confusion.
> > I personally never have such blank lines in a document, so it was a
> > force of habit.
> 
> > Why *did* you start that example with a blank line anyway?

That has been my habit since some very early bugs: see

    http://thread.gmane.org/gmane.emacs.orgmode/5285/focus=5417

Apparently the (old) latex exporter still shows symptoms of that
disease.  Note btw, that the buggy behavior is confined to the old
exporter: the new exporter DTRT with or without the empty line.

> 
> Having said that, I posted my example *without* the opening blank line many
> times in this thread :)
> 

But not originally: that's why I had to write and post my own and after you
reported failures with mine, I didn't bother running yours.

As an object lesson for all of us (we might as well get *something*
positive out of this disaster :-) ):

   o post an ECM to begin with - no ifs, ands or buts.
   o post what you tested *exactly*.
   o test what you (or somebody else) posted *exactly* as it was posted.

Nick

Re: org-export-select-tags

[suvayu ali]

Hello all,

On Tue, Jul 10, 2012 at 12:13 AM, Nick Dokos <nicholas.dokos@hp.com> wrote:
>
>    o post an ECM to begin with - no ifs, ands or buts.
>    o post what you tested *exactly*.
>    o test what you (or somebody else) posted *exactly* as it was posted.

A comment with regards to the above; from the experience in this thread
it seems posting an ECM is better done as a plain text attachment rather
than inline quoted regions. After all getting from inline quoted regions
to working examples require human intervention which, as we saw, is
prone to errors. ;)

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: org-export-select-tags

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> Hello all,
> 
> On Tue, Jul 10, 2012 at 12:13 AM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> >
> >    o post an ECM to begin with - no ifs, ands or buts.
> >    o post what you tested *exactly*.
> >    o test what you (or somebody else) posted *exactly* as it was posted.
> 
> A comment with regards to the above; from the experience in this thread
> it seems posting an ECM is better done as a plain text attachment rather
> than inline quoted regions. After all getting from inline quoted regions
> to working examples require human intervention which, as we saw, is
> prone to errors. ;)
> 

If the human intervention is the problem, then I would advocate
education, rather than attachments, as the solution: after all there is
nothing that would stop that kind of intervention *after* the attachment
has been saved. But in the face of more and more idiotic mail software
out there that mangles messages irredeemably, I will reluctantly agree:
I'm still old fashioned enough to prefer inline quoting, but I have been
known to repost something as an attachment if the inline post gets
mangled.

Nick

Re: org-export-select-tags

[suvayu ali]

Hi,

On Tue, Jul 10, 2012 at 2:54 AM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>
>> Hello all,
>>
>> On Tue, Jul 10, 2012 at 12:13 AM, Nick Dokos <nicholas.dokos@hp.com> wrote:
>> >
>> >    o post an ECM to begin with - no ifs, ands or buts.
>> >    o post what you tested *exactly*.
>> >    o test what you (or somebody else) posted *exactly* as it was posted.
>>
>> A comment with regards to the above; from the experience in this thread
>> it seems posting an ECM is better done as a plain text attachment rather
>> than inline quoted regions. After all getting from inline quoted regions
>> to working examples require human intervention which, as we saw, is
>> prone to errors. ;)
>>
>
> If the human intervention is the problem, then I would advocate
> education, rather than attachments, as the solution: after all there is
> nothing that would stop that kind of intervention *after* the attachment
> has been saved. But in the face of more and more idiotic mail software
> out there that mangles messages irredeemably, I will reluctantly agree:
> I'm still old fashioned enough to prefer inline quoting, but I have been
> known to repost something as an attachment if the inline post gets
> mangled.
>

:) Nothing beats inline quotes when it comes to readability. But I guess
some of the modern GUI clients offer smooth viewing of text attachments.
e.g. I think in T-bird you can see the contents of a text attachment
separated from the email by a horizontal separator without actually
opening it.

However I also notice these clients often mess up the MIME types when
attaching something; this in turn screws up the archive and confuses
email clients on the receiving end[1].

Two examples of how not to do it:
1. <http://thread.gmane.org/gmane.emacs.orgmode/32038>
2. <http://thread.gmane.org/gmane.emacs.orgmode/32038/focus=32118>

> Nick
>

Footnotes:

[1] I believe I learnt about the importance of attachment MIME types
    from you Nick. ;)

-- 
Suvayu

Open source is the future. It sets us free.

Re: org-export-select-tags

[SW]

Nick Dokos <nicholas.dokos <at> hp.com> writes:

> Apparently the (old) latex exporter still shows symptoms of that
> disease.  Note btw, that the buggy behavior is confined to the old
> exporter: the new exporter DTRT with or without the empty line.

I've seen some mention of this new exporter. Where can I find out more? Is it
included in 7.8.11 yet, or still being tested?

> As an object lesson for all of us (we might as well get *something*
> positive out of this disaster  ):
> 
>    o post an ECM to begin with - no ifs, ands or buts.
>    o post what you tested *exactly*.
>    o test what you (or somebody else) posted *exactly* as it was posted.

Indeed. Good points, all.

Thanks.

Re: org-export-select-tags

[Jambunathan K]

> I've seen some mention of this new exporter. Where can I find out
> more? Is it included in 7.8.11 yet, or still being tested?

0. Checkout from git

1. Add contrib/lisp to load-path

2. Visit Org file.  M-x org-export-dispatch RET

3. Migrate your existing settings in to the new exporter by hand.  
   M-x customize-group RET org-export-e-TAB

--