Re: [O] Index of cases

[David Rogers]

Alan L Tyree  writes:

> ... I am now senior enough to insist that the editor edit my files
> directly.

That single sentence really answers the question pretty effectively! The
whole explanation does make perfect sense, though.

I admit that the entire structure of the work-flow is not something I
really understand - it seems to have developed over time in response to
changing situations, and therefore has elements that one might not
choose if one were starting from scratch.

But (just throwing an additional idea out there) - the possibility of
having a considerable apparatus for yourself in Org-mode, and your final
step before sending to the editor being "export to plain text". (so that
your editor has bare plain text with no markup of any kind.)


-- 
David

Re: [O] Edit current tree-node?

[Suvayu Ali]

On Sun, Sep 08, 2013 at 07:58:33PM +0200, Fredrik wrote:
> In babel you can push C-c ' and a new buffer opens to edit the current code
> in a new buffer. Does something similar exist to edit a part of an org-file?
> Say I have the following :
> 
> * Tree 1
> ** SubTree2
> * Tree 2
> * Tree 3
> 
> My cursor is on SubTree2 and I would like to open that part in a new buffer
> to brainstorm around it and then put the changes back in to the original
> file.

C-x n s, `org-narrow-to-subtree'.

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] Index of cases

[Alan L Tyree]

On 09/09/13 08:17, David Rogers wrote:

Jambunathan K  writes:


Jambunathan K  writes:


I have (I think) got them to agree to accept plain text, but I would
like to make it just as plain as possible.

Oh, Ok.  Looks like there is "exchange of ideas" between the author and
publisher...

In lighter vein and tongue-in-cheek sort of way...

It seems like publishers are making you go in circles.

You were after epub.  Now you are after Word.  It is only a matter of
time, before a publisher insists on an LaTex, at which point you would
have done the full-circle and savour a moment of epiphany.


I'm wondering something a bit different:

It sounds as if the publisher actually demands Word documents, and had
never asked for anything but that.

I'm swallowing hard before I say this...

Why not just use Word?

Well, the book is already in LaTeX. I chose that back at the 4th edition 
and am now in the process of preparing the 8th. Earlier editions were in 
Word, and the new Word can't even read the early manuscripts. I 
regularly lost work using Word. The usual complaints.


I had special needs at the time: the publisher uses numbered paragraphs 
of the chapter-number variety, eg, [12-125], and index entries should 
point to the relevant paragraph. Rearranging paragraphs or inserting a 
new one made a mess of *everything* when using Word.


My nephew, a mathematician, suggested that I have a look at LaTeX and 
helped me get started.


I'm very, very happy with using LaTeX for writing. The usual reasons: 
enforced structure, automatic adjustments when rearranging material, 
embedded index entries, automatic generation of tables, the ability to 
use version control, etc. Maintaining a 700+ page book with a zillion 
cross references, index entries, and multiple indexes became a breeze. I 
could concentrate on writing.


The only problem has been interaction with editors, and I am now senior 
enough to insist that the editor edit my files directly. I'll get 
him/her to use TexStudio or something similar to edit my files directly. 
This will deal with the last problem: that of introduced errors through 
transcribing editor's corrections.


I would abandon the book rather than go back to Word :-).

End of rant.

Cheers,
Alan

--
Alan L Tyreehttp://www2.austlii.edu.au/~alan
Tel:  04 2748 6206  sip:typh...@iptel.org

Re: [O] Index of cases

[David Rogers]

Jambunathan K  writes:

> Jambunathan K  writes:
>
>>> I have (I think) got them to agree to accept plain text, but I would
>>> like to make it just as plain as possible.
>>
>> Oh, Ok.  Looks like there is "exchange of ideas" between the author and
>> publisher...
>
> In lighter vein and tongue-in-cheek sort of way...
>
> It seems like publishers are making you go in circles.  
>
> You were after epub.  Now you are after Word.  It is only a matter of
> time, before a publisher insists on an LaTex, at which point you would
> have done the full-circle and savour a moment of epiphany.


I'm wondering something a bit different:

It sounds as if the publisher actually demands Word documents, and had
never asked for anything but that.

I'm swallowing hard before I say this...

Why not just use Word?

-- 
David R

Re: [O] Installing update org in GNU Emacs in OS X

[mapcdi]

It worked like Achim suggested:

Remove the ELPA package, then install it again _in the same session_ of Emacs.

I removed org through Options - Manage Emacs Packages
and reinstalled it right away in the same manner
and all this in the same session of Emacs.

Now I can export from .org to .tex with the latest version of org (8.1).

Thanks Achim!

Re: [O] Installing update org in GNU Emacs in OS X

[mapcdi]

Hi:

Still struggling with update.

After adding this to .emacs:

_

(setq package-archives '(("gnu" . "http://elpa.gnu.org/packages/";)
("marmalade" . "http://marmalade-repo.org/packages/";)
("melpa" . "http://melpa.milkbox.net/packages/";)))

(setq package-enable-at-startup nil)
(package-initialize)

;; custom settings:
etc...



I am now fine in:
Org-mode version 8.1 (8.1-elpa @ /Users/admin/.emacs.d/elpa/org-20130906/)

But then if I try to export org to Latex I get this error:

org-refresh-category-properties: Invalid function: org-with-silent-modifications

and the export is aborted.

The problem therefore persists. Any clues?


Thanks,



08/09/2013, 12:18, map...@me.com:

> After installing the latest update of org-mode (8.1) through Options - Manage 
> Emacs Packages,
> I am able to install.
> 
> Then if I do: M-x org-version,  I get:
> Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ 
> /Users/admin/.emacs.d/elpa/org-20130906/)
> 
> So, even though I have now elpa/org-20130906/   I seem to reload with version 
> 7.9.3f
> 
> It seems that the previous version takes precedence.
> Do you know a way to achieve the desired update?
> 
> Thanks.

Re: [O] Installing update org in GNU Emacs in OS X

[Achim Gratz]

map...@me.com writes:
> org-refresh-category-properties: Invalid function: 
> org-with-silent-modifications
>
> and the export is aborted.
>
> The problem therefore persists. Any clues?

Remove the ELPA package, then install it again _in the same session_ of Emacs.


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

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] Installing update org in GNU Emacs in OS X

[mapcdi]

Hi:

Still struggling with update.

After adding this to .emacs:

_
   
(setq package-archives '(("gnu" . "http://elpa.gnu.org/packages/";)
 ("marmalade" . "http://marmalade-repo.org/packages/";)
 ("melpa" . "http://melpa.milkbox.net/packages/";)))

(setq package-enable-at-startup nil)
(package-initialize)

;; custom settings:
etc...



I am now fine in:
Org-mode version 8.1 (8.1-elpa @ /Users/lucassalom/.emacs.d/elpa/org-20130906/)

But then if I try to export org to Latex I get this error:

org-refresh-category-properties: Invalid function: org-with-silent-modifications

and the export is aborted.

The problem therefore persists. Any clues?


Thanks,
Mark



08/09/2013, 12:18, map...@me.com:

> After installing the latest update of org-mode (8.1) through Options - Manage 
> Emacs Packages,
> I am able to install.
> 
> Then if I do: M-x org-version,  I get:
> Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ 
> /Users/admin/.emacs.d/elpa/org-20130906/)
> 
> So, even though I have now elpa/org-20130906/   I seem to reload with version 
> 7.9.3f
> 
> It seems that the previous version takes precedence.
> Do you know a way to achieve the desired update?
> 
> Thanks.

Re: [O] mixed orgmode installation

[Achim Gratz]

John Hendy writes:
> I'm with you so far. But if all of Org lives in /path/to/org.git/lisp,
> what's to go wrong if it's there vs. /system/path/site-lisp?

It is only "there" when you've built Org and whenever you do something
in Git, it's "gone", only that you might not see that.  Having Org
installed in some other place decouples it from what you do in the work
tree.  That makes it less likely that you load up an Emacs session, do
something in Org, then do something in Git and then go back to sour
Emacs session and load some other parts of Org that won't fit with the
version you've started with.

> I'm not sure I follow this one. Does `make up2` look for changed paths
> (contrib/lisp vs lisp/) since the last `make up2` ? If not, how would
> I know to do `make clean-install` vs. just `make install`?

You should know if you changed something, I suppose.

> I'm talking about your original comment that running out of a git repo
> can lead to:
> - it being just to easy to mess up with the autoloads

Yes, if you forget to re-make them after a change to the source code.

> - have stale byte-compiled files I forgot about somewhere

Yes, because Emacs prefers the byte-compiled files over the sources,
even when it knows the sources are newer.  So when you update from Git,
but don't byte-compile, you will load an older version of Org rather
than the one you think you are using.  If you are running from a Git
tree, you should always keep Org uncompiled for this reason (that's why
that make target exists).

> P.S. And yes, I derailed from the mixed install case due to your
> comment as I thought it was worth looking into. I'm doing what you
> advise against and I wanted to know the risks and more details about
> what I might run into.

You can do whatever you want as long as you can deal with the resulting
problems.  Depending on how careful you are you may never encounter one,
but the most frequent reasons for mixed installs are forgetting to
generate the autoload files or using an init sequence that loads Org
from two different places.


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

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

[O] Edit current tree-node?

[Fredrik]

In babel you can push C-c ' and a new buffer opens to edit the current 
code in a new buffer. Does something similar exist to edit a part of an 
org-file?

Say I have the following :

* Tree 1
** SubTree2
* Tree 2
* Tree 3

My cursor is on SubTree2 and I would like to open that part in a new 
buffer to brainstorm around it and then put the changes back in to the 
original file.


Regards,

Fredrik

Re: [O] mixed orgmode installation

[John Hendy]

On Sun, Sep 8, 2013 at 11:41 AM, Achim Gratz  wrote:
> John Hendy writes:
>> Could you elaborate on this? I'd always thought the exact opposite due
>> to being burned in the past by stale junk littered around /usr/lib,
>> /usr/bin, /usr/local/[bin/sbin]. Thus, for some things, I prefer to
>> run them from the git repository since I know where they'll be vs.
>> where `make install` might desire to put them.
>
> Git provides and manages the source tree and nothing else.  To get a
> reliable Org you need a self-consistent and complete installation — that
> is usually provided by the build system.
>

I'm with you so far. But if all of Org lives in /path/to/org.git/lisp,
what's to go wrong if it's there vs. /system/path/site-lisp?

> http://orgmode.org/worg/dev/org-build-system.html
>
> The most logical place for that Org installation is site-lisp (since
> then load-path is already set up correctly), but you can install almost
> anywhere as long as you know where load-path is pointing to at all
> times.  You could then have multiple versions of Org installed and use
> them for different instances or versiosn of Emacs (one at a time,
> obviously).
>
>> What happens, for example, in this situation:
>> - git clone
>> - make && make install
>
> You just need to "make install" and it's been that way for over two
> years now…
>

Sorry, I never do make install, so that was an oversight.

>> - some file.el gets moved from org.git/contrib/lisp to org.git/lisp in master
>> - git pull
>> - make && make install
>
> And this is what "make up2" is doing, plus testing so the install won't
> be attempted if the tests don't pass.
>
>> Are there now two copies of file.el somewhere in the system?
>
> No, unless you've changed the install location inbetween.  If a file
> would be removed (or renamed), then you'd need to first issue a "make
> clean-install" to make sure it is really gone from your installation.
>

I'm not sure I follow this one. Does `make up2` look for changed paths
(contrib/lisp vs lisp/) since the last `make up2` ? If not, how would
I know to do `make clean-install` vs. just `make install`?

>> Anyway, if there's more to read on some of your situations, I'd love
>> to know as I've been doing exactly that and want to stop if it's
>> recommended against! Thanks for mentioning the potential risk, as I
>> had no idea!
>
> I'm not exactly sure what problem you are talking about, maybe you could
> clarify.  In any case it seems there's been a mixup of different problems
> in this thread.

I'm talking about your original comment that running out of a git repo
can lead to:
- it being just to easy to mess up with the autoloads
- have stale byte-compiled files I forgot about somewhere


John

P.S. And yes, I derailed from the mixed install case due to your
comment as I thought it was worth looking into. I'm doing what you
advise against and I wanted to know the risks and more details about
what I might run into.

>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> Factory and User Sound Singles for Waldorf rackAttack:
> http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
>
>

Re: [O] heading numbering in LaTeX export?

[Peter Salazar]

Ah, I see. Cool, then I will stick to {tocdepth}{3}. Thanks again!


On Sun, Sep 8, 2013 at 7:47 AM, Nick Dokos  wrote:

> Peter Salazar  writes:
>
> > That appears to work perfectly. Thank you so much!
> >
> > If I have 5 levels of heading, should I do it like this?
> >
> > #+LATEX_HEADER: \setcounter{secnumdepth}{0}
> > #+LATEX_HEADER: \setcounter{tocdepth}{5}
> >
>
> Yes, although IMO the TOC will be too busy with that many levels.
> But to each his/her own...
> --
> Nick
>
>
>

Re: [O] mixed orgmode installation

[Achim Gratz]

John Hendy writes:
> Then again, is Worg saying that if `M-x org-version` outputs the
> "correct" answer... we're all set and there's nothing to worry about?

The output of org-version is determined essentially by checking for two
files from the installation and comparing where they would be loaded
from.  This catches the most common problems, but certainly not all.  In
particular, it won't see when the load-path has been changed after some
parts of Org have already been loaded from someplace else (but
org-reload will give a warning for this case).


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

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [O] mixed orgmode installation

[Achim Gratz]

John Hendy writes:
> Could you elaborate on this? I'd always thought the exact opposite due
> to being burned in the past by stale junk littered around /usr/lib,
> /usr/bin, /usr/local/[bin/sbin]. Thus, for some things, I prefer to
> run them from the git repository since I know where they'll be vs.
> where `make install` might desire to put them.

Git provides and manages the source tree and nothing else.  To get a
reliable Org you need a self-consistent and complete installation — that
is usually provided by the build system.

http://orgmode.org/worg/dev/org-build-system.html

The most logical place for that Org installation is site-lisp (since
then load-path is already set up correctly), but you can install almost
anywhere as long as you know where load-path is pointing to at all
times.  You could then have multiple versions of Org installed and use
them for different instances or versiosn of Emacs (one at a time,
obviously).

> What happens, for example, in this situation:
> - git clone
> - make && make install

You just need to "make install" and it's been that way for over two
years now…

> - some file.el gets moved from org.git/contrib/lisp to org.git/lisp in master
> - git pull
> - make && make install

And this is what "make up2" is doing, plus testing so the install won't
be attempted if the tests don't pass.

> Are there now two copies of file.el somewhere in the system?

No, unless you've changed the install location inbetween.  If a file
would be removed (or renamed), then you'd need to first issue a "make
clean-install" to make sure it is really gone from your installation.

> Anyway, if there's more to read on some of your situations, I'd love
> to know as I've been doing exactly that and want to stop if it's
> recommended against! Thanks for mentioning the potential risk, as I
> had no idea!

I'm not exactly sure what problem you are talking about, maybe you could
clarify.  In any case it seems there's been a mixup of different problems
in this thread.


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

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

[O] Marking repeating task as done with the scheduled time

[Nikolay Kudryavtsev]

Hi all.

I have a habit set up that I need to mark done every day. If it's not 
done that day I can do it later. Basically I want to track how many days 
I'm running late and have the ability to catch up.


If I use "+1d" interval, when I mark task as done it updates the 
schedule by one 1 day, but puts the done record with the current date. 
So I have to edit every timestamp manually, to make the habit display 
properly.


Is there any way I can make my done records to use task scheduled time 
instead of now?


--
Best Regards,
Nikolay Kudryavtsev

Re: [O] Outline cycling does not preserve point's position

[Carsten Dominik]

On 7.9.2013, at 21:28, Sebastien Vauban  wrote:

> Hi Carsten,
> 
> Carsten Dominik wrote:
>> On 7.9.2013, at 14:11, "Sebastien Vauban"  wrote:
>> 
>>> Since a little while, I've observed that point's position is not anymore
>>> preserved when cycling buffer's view with S-TAB.
>>> 
>>> Sometimes, point stays where it was (even when in the body of entries);
>>> sometimes, not.
>>> 
>>> See http://screencast.com/t/1sr6Lezk:
>>> 
>>> - when on the first letter of "From", in that example, point's location is
>>> preserved;
>>> 
>>> - when on the second letter of it, point's location is lost: new position is
>>> at the end of the level 1 parent...
>>> 
>>> That's very annoying when you want to just look at your tree structure, but
>>> don't expect to land somewhere else by doing so.
>> 
>> you say "since a little while".  Have you tried to bisect?
> 
> Not yet. I have many Chinese plates turning at the moment, but I'll try to do
> that very soon. And I have other problems to report or bisect:
> 
> - not possible anymore to "cut" a code snippet in two parts with C-c C-v C-d
>  (demarcate block); already reported (without bisect), no answer;
> 
> - not possible anymore to use C-a or C-e in code blocks to select regions; not
>  reported yet, though I reported similar problems with C-arrows (apparently
>  due to a change which is now officially part of 8.1). IMO, that renders
>  editing of code block in the original buffer much more annoying.

Also this is now fixed.

Regards

- Carsten

> 
>> Or has it been like this always?
> 
> In my mind, this did work before; or, at least, in (many) more cases than it
> now does.
> 
>> Also, I am not convinced that staying in invisible places is the
>> right behavior at all.  Even though I would agree that three S-TAB
>> in a row should be a null operation.
> 
> At the very least, we could agree that point should always be part of the
> entry we were on; so never go up to the *parent* entry.
> 
>> May be it would be better to use something like
>> 
>>   (org-display-outline-path nil t)
>> 
>> to see where you are?
> 
> I know where I am: I'm using that. But, sometimes (in fact, often), I want to
> see the rest of the entries (brothers, parents, etc.) in the outline view.
> 
> I simply expect to land back at the entry I was at, when having cycled
> 3 times.
> 
> Best regards,
>  Seb
> 
> -- 
> Sebastien Vauban



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] ANN: Release 8.1

[Rainer Stengele]

Thanks Carsten!

ORG is always improving. It's amazing!
I like the performance improvement through org-agenda-ignore-drawer-properties 
a lot!

Keep up the good work!

- Rainer

Am 06.09.2013 22:21, schrieb Carsten Dominik:
> Hi everyone!
> 
> The current git master has just been tagged as release 8.1.  I would like
> to thank everyone who contributed to it.  I am extremely glad to see how
> little input from my side is really needed to move this project like a well
> oiled machine.  Thank you Org community, with its increasing number
> of people who take responsibility.
> 
> Special thanks to Bastien for pushing this release over the finish line,
> next time it will be truly me who will do this.  After struggling with
> this during the first few month after I took over the maintainer role
> again, I seem to have found a way now to make sufficient time.
> 
> Below is a list of changes.
> 
> Enjoy!
> 
> - Carsten
> 
>   
> 
>   ORG 8.1
>   
> 
> 
> 
> Incompatible changes
> 
> 
> Combine org-mac-message.el and org-mac-link-grabber into org-mac-link.el
> 
> 
>   Please remove calls to `(require 'org-mac-message)' and `(require
>   'org-mac-link-grabber)' in your `.emacs' initialization file.  All you
>   need now is `(require 'org-mac-link)'.
> 
>   Additionally, replace any calls to `ogml-grab-link' to
>   `org-mac-grab-link'.  For example, replace this line:
> 
>   ,
>   | (define-key org-mode-map (kbd "C-c g") 'omgl-grab-link)
>   `
> 
>   with this:
> 
>   ,
>   | (define-key org-mode-map (kbd "C-c g") 'org-mac-grab-link)
>   `
> 
> 
> HTML export: Replace `HTML_HTML5_FANCY' by `:html-html5-fancy' (...)
> 
> 
>   Some of the HTML specific export options in Org <8.1 are either nil or
>   t, like `#+HTML_INCLUDE_STYLE'.  We replaced these binary options with
>   option keywords like :html-include-style.
> 
>   So you need to replace
> 
>   ,
>   | #+HTML_INCLUDE_STYLE: t
>   `
> 
>   by
> 
>   ,
>   | #+OPTIONS: :html-include-style t
>   `
> 
>   Options affected by this change: `HTML5_FANCY', `HTML_INCLUDE_SCRIPTS'
>   and `HTML_INCLUDE_STYLE'.
> 
> 
> Important bugfixes
> ==
> 
> org-insert-heading has been rewritten and bugs are now fixed
> 
> 
> 
> The replacement of disputed keys is now turned of when reading a date
> ~
> 
> 
> New features
> 
> 
> You can now use `xdg-open' to control how to open files
> ~~~
> 
> 
> `C-c ^ x' will now sort checklist items by their checked status
> ~~~
> 
>   See org-sort-list: hitting `C-c ^ x' will put checked items at the end
>   of the list.
> 
> 
> Various LaTeX export enhancements
> ~
> 
>   - Support SVG images
>   - Support for .pgf files
>   - LaTeX Babel blocks can now be exported as `.tikz' files
>   - Allow `latexmk' as an option for org-latex-pdf-process
>   - When using `\usepackage[AUTO]{inputenc}', AUTO will automatically be
> replaced with a coding system derived from
> `buffer-file-coding-system'.
>   - The dependency on the `latexsym' LaTeX package has been removed, we
> now use `amssymb' symbols by default instead.
> 
> 
> Remapping `forward-paragraph' and `backward-paragraph'
> ~~
> 
>   `forward-paragraph' and `backward-paragraph' are now remapped to
>   org-forward-element and org-backward-element respectively.
>   E.g. hitting `C-' on a headline will move to the next headline.
> 
> 
> New entities in `org-entities.el'
> ~
> 
>   Add support for ell, imath, jmath, varphi, varpi, aleph, gimel, beth,
>   dalet, cdots, S (ß), dag, ddag, colon, therefore, because, triangleq,
>   leq, geq, lessgtr, lesseqgtr, ll, lll, gg, ggg, prec, preceq,
>   preccurleyeq, succ, succeq, succurleyeq, setminus, nexist(s), mho,
>   check, frown, diamond.  Changes loz, vert, checkmark, smile and tilde.
> 
> 
> New options
> ===
> 
> New option org-bookmark-names-plist
> ~~~
> 
>   This allows to specify the names of automatic bookmarks.
> 
> 
> New option org-agenda-ignore-drawer-properties
> ~~
> 
>   This allows more flexibility when optimizing the agenda generation.
>   See [http://orgmode.org/worg/agenda-optimization.html] for details.
> 
> 
> New option: org-html-link-use-abs-url to force using absolute URLs
> ~~
> 
>   This is an expor

Re: [O] mixed orgmode installation

[John Hendy]

On Sun, Sep 8, 2013 at 10:10 AM, Suvayu Ali  wrote:
> On Sun, Sep 08, 2013 at 09:37:23AM -0500, John Hendy wrote:
>>
>> On that note, is there a recommended "diagnosis" route someone could
>> recommend other than simply `M-x org-version`? Is it possible to get,
>> e.g. 8.0.7, from that command but be pulling from mixed org locations
>> (org shipped with Emacs, and org from tgz or git)? If so, I was
>> unaware, so it'd be great to understand how one can do a full
>> diagnostic.
>
> When in doubt, Worg is always your friend ;):
>
>   

I take it I'm a bad friend, as I apparently forget about that one
constantly with this list :)

So... from that page, here are my tools:
- `M-x org-version` : if that lists what you think it should via your
git or snapshot... so far so good

- If `M-x list-load-path-shadows` looks like...???... then you're
good. I'm assuming it should look like this:

#+begin_src list-load-path-shadows

~/.elisp/org.git/lisp/ob-latex hides /usr/share/emacs/24.3/lisp/org/ob-latex
~/.elisp/org.git/lisp/ob-scala hides /usr/share/emacs/24.3/lisp/org/ob-scala
~/.elisp/org.git/lisp/org-src hides /usr/share/emacs/24.3/lisp/org/org-src
~/.elisp/org.git/lisp/ob-java hides /usr/share/emacs/24.3/lisp/org/ob-java

[...]

94 Emacs Lisp load-path shadowings were found

#+end_src

I'm not sure how many there should be, but they all come from from my
git repo and shadow something in my emacs installation. That still
leaves two possibly redundant questions:

- How do I find out what's *not* shadowed?
- How do I find out how many Lisp load-path shadowings there *should
be* with a correct, non-mixed installation?

Then again, is Worg saying that if `M-x org-version` outputs the
"correct" answer... we're all set and there's nothing to worry about?
In other words, it won't output the correct, git-pointing,
version/path unless *everything* provided by the built-in Org has been
replaced by the snapshot/git version?


Thanks,
John

>
> --
> Suvayu
>
> Open source is the future. It sets us free.

Re: [O] mixed orgmode installation

[Suvayu Ali]

On Sun, Sep 08, 2013 at 09:37:23AM -0500, John Hendy wrote:
> 
> On that note, is there a recommended "diagnosis" route someone could
> recommend other than simply `M-x org-version`? Is it possible to get,
> e.g. 8.0.7, from that command but be pulling from mixed org locations
> (org shipped with Emacs, and org from tgz or git)? If so, I was
> unaware, so it'd be great to understand how one can do a full
> diagnostic.

When in doubt, Worg is always your friend ;):

  

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] mixed orgmode installation

[John Hendy]

On Sun, Sep 8, 2013 at 12:40 AM, adam  wrote:
>
>> -Original Message-
>> From: Suvayu Ali 
>> To: emacs-orgmode@gnu.org
>> Subject: Re: [O] mixed orgmode installation
>> Date: Wed, 4 Sep 2013 17:07:49 +0200
>>
>> On Wed, Sep 04, 2013 at 04:52:34PM +0200, Johannes Rainer wrote:
>> > hm, that's an option.
>> > based on your suggestion I created now my own little makefile to install
>> > the git org-mode and directly over-write the one located in
>> > /Applications/Emacs.app/Resources/lisp/org . actually, I first delete all
>> > files in this org directory and install the one from git into the dir 
>> > again.
>>
>> This can actually cause difficult to diagnose problems sometimes.  The
>> simplest way to do it right is to setup your load-path early in your
>> init file.  To get an idea, you can take a look at my setup.
>>
>>   
>>
>> Look at the first 18 lines; after this I can customise, load, do
>> whatever I want with org.  You will notice I load a kill-old-org.el.
>> That line is experimental and optional, and you may skip it.
>>
>> Hope this helps,
>
> Very interesting thread.
>
> Being a novice, I grab the tgz snapshot, unarchive into a
> folder, and simply have that folder in the load-path early
> in .emacs.
>
> I don't  'make && make install'  so perhaps I am missing some
> things as a result. I just leave the old version Emacs-supplied
> Org as-is.

It might be worth waiting for some others to chime in. While this is
one potential route (make install), I do exactly what you did, and it
works fine as far as I know. I haven't seen a concrete response above
as to what exactly can go wrong -- Achim hinted that it's not trivial
to disable the built-in org, but said it shouldn't matter if one loads
the git org early on (it's the first line in my .emacs), so I'm not
sure if it matters that the built-in org sort of "lives on" beneath
the surface.

On that note, is there a recommended "diagnosis" route someone could
recommend other than simply `M-x org-version`? Is it possible to get,
e.g. 8.0.7, from that command but be pulling from mixed org locations
(org shipped with Emacs, and org from tgz or git)? If so, I was
unaware, so it'd be great to understand how one can do a full
diagnostic.

If not, great, I won't worry about it and I'll view the `make install`
recommendations as more of a housekeeping suggestion vs. a functional
one (risk of mixed install).


Thanks,
John

>
>
>
>
>
>

Re: [O] mixed orgmode installation

[John Hendy]

On Wed, Sep 4, 2013 at 2:20 PM, Achim Gratz  wrote:
> Johannes Rainer writes:
>> is there a "clean" way to disable the built in org from emacs?
>
> Short answer: no.
>
>> I'm loading org mode from git externally, but newer emacs always come
>> with org mode included.
>
> That's not a problem as long as you set up the load-path to point to the
> install made via Git before loading Org.  I don't recommend working from
> a Git tree directly because it's just too easy to mess up with the
> autoloads or have stale byte-compiled files somewhere that you forgot
> about.
>

Could you elaborate on this? I'd always thought the exact opposite due
to being burned in the past by stale junk littered around /usr/lib,
/usr/bin, /usr/local/[bin/sbin]. Thus, for some things, I prefer to
run them from the git repository since I know where they'll be vs.
where `make install` might desire to put them.

What happens, for example, in this situation:
- git clone
- make && make install
- some file.el gets moved from org.git/contrib/lisp to org.git/lisp in master
- git pull
- make && make install

Are there now two copies of file.el somewhere in the system?

Anyway, if there's more to read on some of your situations, I'd love
to know as I've been doing exactly that and want to stop if it's
recommended against! Thanks for mentioning the potential risk, as I
had no idea!


Best regards,
John


>> would just deleting the org folder in the emacs (am using Emacs.app on
>> mac) installation help?
>
> No.  Leave your Emacs installation alone, unless you fancy compiling
> your own Emacs.  Install Org into site-lisp, whereever that is on Mac.
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> SD adaptation for Waldorf microQ V2.22R2:
> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
>
>

Re: [O] heading numbering in LaTeX export?

[John Hendy]

On Sat, Sep 7, 2013 at 5:51 PM, Peter Salazar  wrote:
> Thanks for the responses!
>
> John: Oh yes, of course. Sorry about that. inimal org file and config files
> are here. I had to make the org file long enough to make several pages, so
> the header displays. Here you go:
> https://github.com/petersalazar/org-troubleshooting

Hi Peter,


Actually, I hadn't understood your issue. I thought you weren't
getting headlines exported at all, as in a blank document, which might
require a bit more delving into. Now I get it and it makes sense. When
I use num:nil but want a TOC, I tend to just add the entries manually:

#+begin_example

* Introduction
\addcontentsline{toc}{subsection}{Introduction}

blah blah blah

* Conclusion
\addcontentsline{toc}{subsection}{Conclusion}

blah blah blah

#+end_example


Perhaps a bit manual, and it looks like you've gotten more automated
answers to use via #+latex_header arguments.


Good luck!
John

>
> Rasmus: #+OPTIONS: num:0 is what I started from. When I do that, the
> resulting PDF has no Table of Contents, and the header displays the section
> title as "Contents."
>
> The same thing happens with #+LATEX: \setcounter{secnumdepth}{0}.
>
> Richard: Your idea about
> #+LATEX_HEADER: \renewcommand{...}
>
> sounds very promising! I'd love to know what the exact command is!
>
> I don't need section numbers ever, so my desire is to turn off numbering
> forever, but still have an intact Table of Contents and header.
>
> Thanks guys!
>
>
> On Fri, Sep 6, 2013 at 4:30 PM, John Hendy  wrote:
>>
>> On Fri, Sep 6, 2013 at 2:43 PM, Peter Salazar 
>> wrote:
>> > I have a LaTeX template I created for use with org-mode, to export to
>> > PDF
>> > via LaTeX using xelatex.
>> >
>> > I don't edit LaTeX directly, I just generate from org-mode. This works
>> > perfectly for me except for one thing: it only works when I have heading
>> > numbering turned on.
>> >
>> > When I turn numbering off in org-mode, by adding this line to my
>> > org-mode
>> > file...
>> >
>> > #+OPTIONS:   num:nil
>> >
>> > ...LaTeX no longer recognizes my headings as headings. This creates two
>> > problems:
>> >
>> > 1. The Table of Contents is blank.
>> > 2. The \leftmark in the heading shows up as "Contents" instead of
>> > showing up
>> > as the title of the section.
>> >
>> > How do I modify these org-mode preferences such that my I can turn
>> > heading
>> > numbering off in org-mode while still correctly generating a Table of
>> > Contents and adding my section title to the header?
>> >
>> > I'm sorry, but I don't know enough about LaTeX to make a minimum
>> > representation of this. I have no idea where the problem is.
>> >
>>
>> At the very least, can you provide a minimal org file? This is over my
>> head with xelatex and all that customization, but I think people are
>> going to at least need:
>> - minimal emacs config (reproducible version that produces the
>> problem, not just the latex stuff)
>> - a .org file that produces the issue you're experiencing (even with
>> just a couple headlines and the words "blah blah blah" or what have
>> you as the text
>>
>>
>> John
>>
>> > Here are the org-mode preferences in question:
>> > http://pastebin.com/62Nugpsg
>> >
>> > Thanks!
>
>

Re: [O] Index of cases -- Revisited

[Jambunathan K]

Alan L Tyree  writes:

> I am concerned with the write -> send to editor -> rewrite -> send to
> editor cycle. When the editor and I are in agreement with everything,
> convert to Word and send to publisher.

Wikis..

Talk or comment pages separate from document content.

Changes shouldn't be inline but paragraph-oriented (helps with gitting
and diffing). It may happen outside the content flow, say at the tail of
the document (or think an extra sheet)

You can say that the commenter indent his comments with an say tabs, so
that you can do `keep-lines' and `flush-lines' or
`set-selective-display' magic.

> "Plain" org mode seems to me to be a good choice for the
> manuscript. Now trying to figure out how to add the other requirements
> without cluttering the manuscript.

Number your paragraphs in the plain text file so that they can be easily
xref-ed.  It could be a little difficult getting used to numbers but it
could be useful.

Being an emacs user, you can always remove the numbers or re-number the
numbers at later in point in time.

> I am too far OT.

Re: [O] Index of cases

[Jambunathan K]

Jambunathan K  writes:

>> I have (I think) got them to agree to accept plain text, but I would
>> like to make it just as plain as possible.
>
> Oh, Ok.  Looks like there is "exchange of ideas" between the author and
> publisher...

In lighter vein and tongue-in-cheek sort of way...

It seems like publishers are making you go in circles.  

You were after epub.  Now you are after Word.  It is only a matter of
time, before a publisher insists on an LaTex, at which point you would
have done the full-circle and savour a moment of epiphany.



Booktype folks - http://www.sourcefabric.org/en/booktype/ - surfaced in
fsf.org a few months ago.

http://directory.fsf.org/wiki/Booktype

Re: [O] Index of cases

[Jambunathan K]

CC me in the reply.


Alan L Tyree  writes:

> G'day,
>
> I am the author of a legal text of about 700 pages. I currently have
> the book in LaTeX using the memoir class. A couple of macros define
> special indexes for a Table of Cases and a Table of Statutes.

Please share the existing macros.  Others may find it useful or get
inspiration from it.

> I would like to move the whole thing to Org to make it easier for my
> editors who can be easily alarmed by the LaTeX markup.
>
> The LaTeX is overkill since I submit the manuscript to the publisher
> in a Word file.

If you are interested in ODT export and find something missing, I would
be happy to implement.

The exporter currently doesn't print table of figures etc.  It is
something that I hope to flesh out.  Btw, the exporter already
categorises Math formula (meaning png images or MathML snippets
converted from Latex math snipppets) in to it's own sequence counter.
So I believe we can conjure up a way to enumerate the cases separately.

> Is there a standard way to get, say, the table of cases? A typical
> "case" looks like this:
>
> Howell v Coupland (1874) LR 9 QB 462; (1876) 1 QBD 258
>
> The Table of Cases needs to indicate where in the text the case is
> mentioned; reference to section numbers is OK. So, for example, in the
> Table of Cases, the above case appears as:
>
> Howell v Coupland (1874) LR 9 QB 462; (1876) 1 QBD 258  [15.16]
> [15.25]

Assuming that the cases are introduced in a paragraph you can attach a
label and caption to a paragraph and link to the NAME with the usual
"reference" link.  (This is possible with the new exporter.)

#+CAPTION: A Non-sensical case
#+NAME: case:dismissed
This paragraph describes HowellvCoupland.



Another alternative would be to introduce the title of the case as a
paragraph of its own and styled separately and then link to the
paragraph.

#+ATTR_ODT: :style "Cases"
A Non-sensical case

This paragraph describes HowellvCoupland.



The difference between the two is this: In the second case, the name of
the case goes right in to document content rather than as a paragraph
caption.

In ODT, it is possible to "collect" paragraphs that have a given style
in to an index of it's own.



I am writing from memory and you know better than to repose trust on
someone you have never met. 

Re: [O] Index of cases

[Jambunathan K]

> Here are the LaTeX macros that I use.

Seeing a concrete example helps.  Helps avoid speculation.  I don't
understand Latex, so I will speculate ...

> #+BEGIN_EXAMPLE
> Provided the documents are in order, the buyer must pay. This is so
> even if it is known that the goods have been lost at sea. For example,
> in \cdx{Manbre Saccharine Co Ltd v Corn Products Co Ltd}{[1919] 1
>KB 198} the defendants sold American pearl starch to the plaintiffs
> on CIF London terms.
> #+END_EXAMPLE

Seems like a heretical form of Inline footnotes to me.  I would suggest
that you "fake" a Bibliography entry in a *.bib file and use JabRef to
create your "References" or "Endnotes".

> but I haven't used it with book length writing that requires
> indexes. 

You need to just command the machine to do the export :-)

> Obviously would be nice, but I can submit the chapters
> separate from the indexes so it may not be necessary. 

As a side-note, I would like to at some point in time add support for
*.odm.

> both approaches would require quite a bit of markup to go back into
> the main part of the manuscript.

A markup is markup.  The markup I suggest is paragraph-oriented - which
Org is good at.  The markup that you have resorted to is
span/inline-style at which Org sucks.

> This is what I'm trying to avoid since the publisher and editors have
> always required Word. 

Why get caught in specifics of Markup when all you want is a Word or a
OpenDocument format or even a plain text format.  

In the grand scheme of things, insisting plain text or Org or Word
doesn't really matter.  If you want and do get Word, then markup - Org
or otherwise - doesn't matter.

> I have (I think) got them to agree to accept plain text, but I would
> like to make it just as plain as possible.

Oh, Ok.  Looks like there is "exchange of ideas" between the author and
publisher...

> Paragraphs in the text may refer to many cases, so I don't think your
> suggestions will meet that goal.

Seems like Citation or Footnote to me.

Re: [O] heading numbering in LaTeX export?

[Nick Dokos]

Peter Salazar  writes:

> That appears to work perfectly. Thank you so much! 
>
> If I have 5 levels of heading, should I do it like this? 
>
> #+LATEX_HEADER: \setcounter{secnumdepth}{0}
> #+LATEX_HEADER: \setcounter{tocdepth}{5}
>

Yes, although IMO the TOC will be too busy with that many levels.
But to each his/her own...
-- 
Nick

Re: [O] [BUG] [Babel] Do not try to process inline source in macro templates

[Eric Schulte]

Nicolas Girard  writes:

> 2013/9/2 Eric Schulte  :
>>>
>>> I've just pushed up a fix for this issue which should now ignore inline
>>> source blocks on lines starting with "#+" during export.  I don't know
>>> if there is a better way than using a regex to detect such non-exporting
>>> lines but this appears to work.
>>>
>
> Thanks very much !
>

I've just pushed up a better (read: functional) solution suggested by
Nicolas Goaziou which uses org-element to determine when code blocks
should be executed.  This the current Org-mode the following example
file exports without error as expected.

#+Title: Example
#+Options: ^:{}

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec
hendrerit tempor tellus. Donec pretium posuere tellus. Proin quam
nisl, tincidunt et, mattis eget, convallis nec, purus. Cum sociis
natoque penatibus et magnis src_emacs-lisp{(current-time-string)} dis
parturient montes, nascetur ridiculus mus. Nulla posuere. Donec vitae
dolor. Nullam tristique diam non turpis. Cras placerat accumsan
nulla. Nullam rutrum. Nam vestibulum accumsan nisl.

# Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec
# hendrerit tempor tellus. Donec pretium posuere tellus. Proin quam
# nisl, tincidunt et, mattis eget, convallis nec, purus. Cum sociis
# natoque penatibus et magnis src_emacs-lisp{(error "don't evaluate me!!")}
# dis parturient montes, nascetur ridiculus mus. Nulla posuere. Donec
# vitae dolor. Nullam tristique diam non turpis. Cras placerat
# accumsan nulla. Nullam rutrum. Nam vestibulum accumsan nisl.

- Lorem
- ipsum
- dolor src_emacs-lisp{(current-time-string)}
- sit
- amet

#+MACRO: name src_emacs-lisp{(error "don't evaluate me!!")}

#+begin_src emacs-lisp :exports results
  (current-time-string)
  ;; foo
  (current-time-string)
#+end_src

# #+begin_src emacs-lisp :export results
#   (error "don't evaluate me!!")
# #+end_src

Cheers,

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D

Re: [O] Outline cycling does not preserve point's position

[Eric Schulte]

>
> Not yet. I have many Chinese plates turning at the moment, but I'll try to do
> that very soon. And I have other problems to report or bisect:
>
> - not possible anymore to "cut" a code snippet in two parts with C-c C-v C-d
>   (demarcate block); already reported (without bisect), no answer;
>

This works for me, could you report a minimal recipe for reproduction,
and maybe a git bisect commit?

Thanks,

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D

Re: [O] Superscript before character

[Carsten Dominik]

On 8.9.2013, at 12:15, Rasmus  wrote:

> Carsten Dominik  writes:
> 
>> Yes, this will do the trick for LaTeX, but {{{...}}} is still not pretty.
>> Yes, maybe I should think more about the cechem package - did not know
>> it, and it looks good.
>> Thanks!
> 
> {{{·}}} looks terrible but it's pretty quick to type. . .  Perhaps we
> could fontify them like with URLs.
> 
> For more flexibility you could use a URL-like syntax which could then
> export conditional on the output format,
> 
> (org-add-link-type "ce" nil
> (lambda (path desc format) 
>  (cond ((eq format 'latex)
>  (format "\ce{%s}" desc))
>  ((eq format 'html)
>(format "\\nbsp%s" desc)
> 
> or something like  that . . . 

Another good idea - I'll try this.

- Carsten

> 
> –Rasmus
> 
> -- 
> There are known knowns; there are things we know that we know.



signature.asc
Description: Message signed with OpenPGP using GPGMail

[O] Installing update org in GNU Emacs in OS X

[mapcdi]

After installing the latest update of org-mode (8.1) through Options - Manage 
Emacs Packages,
I am able to install.

Then if I do: M-x org-version,  I get:
Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ 
/Users/admin/.emacs.d/elpa/org-20130906/)

So, even though I have now elpa/org-20130906/   I seem to reload with version 
7.9.3f

It seems that the previous version takes precedence.
Do you know a way to achieve the desired update?

Thanks.

Re: [O] Superscript before character

[Rasmus]

Carsten Dominik  writes:

> Yes, this will do the trick for LaTeX, but {{{...}}} is still not pretty.
> Yes, maybe I should think more about the cechem package - did not know
> it, and it looks good.
> Thanks!

{{{·}}} looks terrible but it's pretty quick to type. . .  Perhaps we
could fontify them like with URLs.

For more flexibility you could use a URL-like syntax which could then
export conditional on the output format,

(org-add-link-type "ce" nil
 (lambda (path desc format) 
  (cond ((eq format 'latex)
  (format "\ce{%s}" desc))
  ((eq format 'html)
(format "\\nbsp%s" desc)

or something like  that . . . 

–Rasmus

-- 
There are known knowns; there are things we know that we know.

[O] Bug: Can't follow a link to a relative html filename with a whitespace [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)]

[Diogo F. S. Ramos]

1. touch a file as `/tmp/bar baz.html'
2. Visit `/tmp/foo.org'
3. Link to the HTML file typing [[file:bar baz.html]]
4. Try following the link with C-c C-o

* Expected

Open the file inside a browser

* Happens

Two urls are open inside the browser:  and

Re: [O] heading numbering in LaTeX export?

[Peter Salazar]

That appears to work perfectly. Thank you so much!

If I have 5 levels of heading, should I do it like this?

#+LATEX_HEADER: \setcounter{secnumdepth}{0}
#+LATEX_HEADER: \setcounter{tocdepth}{5}


On Sun, Sep 8, 2013 at 1:54 AM, Nick Dokos  wrote:

> Peter Salazar  writes:
>
> > Thank you! That solution is very promising indeed.
> >
> > I see why it's quick and dirty though - it appears to be generation
> > section numbers, but just making the numbers invisible, so that the
> > headings are not flush with the left margin:
> > http://i.imgur.com/G6drpmf.png
> >
> > Is there a solution to that, or is that just the way it is?
> >
>
> Here is a cleaner way:
>
> #+LATEX_HEADER: \setcounter{secnumdepth}{0}
> #+LATEX_HEADER: \setcounter{tocdepth}{3}
>
> --
> Nick
>
>
>
>

[O] Index of cases -- Revisited

[Alan L Tyree]

Some clarification:

I realise that my aim wasn't clearly stated:

I am concerned with the write -> send to editor -> rewrite -> send to 
editor cycle. When the editor and I are in agreement with everything, 
convert to Word and send to publisher.


I can get an editor to agree to "plain" text. What I am afraid of is 
that LaTeX will scare the socks off an editor who is accustomed to 
editing legal submissions.


I am hoping to construct something that will be as "plain" as possible 
in the manuscript, then take care of other requirement (Table of cases, 
etc) by some other means.


"Plain" org mode seems to me to be a good choice for the manuscript. Now 
trying to figure out how to add the other requirements without 
cluttering the manuscript.


Thanks for listening, and just tell me if I am too far OT.

Cheers,
Alan

--
Alan L Tyreehttp://www2.austlii.edu.au/~alan
Tel:  04 2748 6206  sip:typh...@iptel.org