Re: [O] Mixing Python2 and Python3 blocks in one file

[Thomas S. Dye]

William Henney writes:
>> Cool, I did not find this parameter yet.
>>
>> Is this undocumented? http://orgmode.org/org.html does not contain
>> the string ":python:" and
>> http://orgmode.org/org.html#Language_002dspecific-header-arguments
>> also does not mention this parameter.
>>
>>
> It is documented at
> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-python.html

As of a few hours ago, when I added it.  It probably wasn't there when
Karl looked.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] Agenda filter by any tag seems to be broken

[Eric Abrahamsen]

Kaushal Modi  writes:

> On Mon, May 16, 2016 at 8:38 PM Eric Abrahamsen
>  wrote:
>
> Starting with emacs -Q, then adding the org-plus-contrib directory
> to
> load-path:
>
> Are you installing both the git master version and org-plus-contrib? I
> do not have org-plus-contrib in my load-path. The only org I have in
> the load-path is the git master version. If you *are* installing both
> versions, then that could probably explain the issue you are facing.

I'm not running org from git anymore, just org-plus-contrib from...
melpa? Actually, since Emacs' package management has no way of
specifying "provides", I've got both org and org-plus-contrib. But
that's not the issue, see below...

> M-x org-agenda
> t ;; all todos, an empty list of course
> /
> SPC
>
> And I get the error.
>
> I tried that. But I don't get any error.
>
> I took the original org-agenda-filter-make-matcher-tag-exp function
> from the git master and added few debug statements as below:
>
> (defun org-agenda-filter-make-matcher-tag-exp (tags op)
>   "Return a form associated to tag-expression TAGS.
> Build a form testing a line for agenda filter for
> tag-expressions.  OP is an operator of type CHAR that allows the
> function to set the right switches in the returned form."
>   (message "arg tags: %S" tags)
>   (message "arg op: %S" op)
>   (let (form ret)
> ;; Any of the expressions can match if OP is +, all must match if
> ;; the operator is -.
> (dolist (x tags (cons (if (eq op ?-) 'and 'or) form)) 
>   (let* ((tag (substring x 1))
>  (f (cond
> ((string= "" tag) '(not tags))
> ((and (string-match-p "\\`{" tag) (string-match-p "}\\'" tag))

Okay, there's the problem. In the org git repo, the code above has been
that way since it was added in 2015. In the package-manager version,
however, it now looks like this:

  (let* ((tag (substring x 1))
 (isregexp (and (equal "{" (substring tag 0 1))
(equal "}" (substring tag -1
 regexp)

And the `substring' calls raise the error. The code is the same in the
"org" and "org-plus-contrib" packages.

I don't know where the different code comes from, or who maintains it,
or why it's different from the org git repo, but it would be nice if
someone could look into fixing that!

Eric

Re: [O] Agenda filter by any tag seems to be broken

[Kaushal Modi]

On Mon, May 16, 2016 at 8:38 PM Eric Abrahamsen 
wrote:

> Starting with emacs -Q, then adding the org-plus-contrib directory to
> load-path:
>

Are you installing both the git master version and org-plus-contrib? I do
not have org-plus-contrib in my load-path. The only org I have in the
load-path is the git master version. If you *are* installing both versions,
then that could probably explain the issue you are facing.


> M-x org-agenda
> t ;; all todos, an empty list of course
> /
> SPC
>
> And I get the error.
>

I tried that. But I don't get any error.

I took the original org-agenda-filter-make-matcher-tag-exp function from
the git master and added few debug statements as below:

(defun org-agenda-filter-make-matcher-tag-exp (tags op)
  "Return a form associated to tag-expression TAGS.
Build a form testing a line for agenda filter for
tag-expressions.  OP is an operator of type CHAR that allows the
function to set the right switches in the returned form."
  (message "arg tags: %S" tags)
  (message "arg op: %S" op)
  (let (form ret)
;; Any of the expressions can match if OP is +, all must match if
;; the operator is -.
(dolist (x tags (cons (if (eq op ?-) 'and 'or) form))
  (let* ((tag (substring x 1))
 (f (cond
((string= "" tag) '(not tags))
((and (string-match-p "\\`{" tag) (string-match-p "}\\'" tag))
 ;; TAG is a regexp.
 (list 'org-match-any-p (substring tag 1 -1) 'tags))
(t (list 'member (downcase tag) 'tags)
(message "in let, tag: %S" tag)
(message "in let, f: %S" f)
(prog1
(setq ret (push (if (eq op ?-) (list 'not f) f) form))
  (message "ret val: %S" ret))

Then when I do M-x org-agenda t / SPC, I get:

arg tags: ("+")
arg op: 43
in let, tag: ""
in let, f: (not tags)
ret val: ((not tags))

-- 

-- 
Kaushal Modi

[O] Bug: XML entities in the ox-rss exporter

[Arun Isaac]

The ox-rss exporter does not replace characters (such as < , > , etc.)
by their corresponding XML entities ( ,  , etc.) in the 
field of the generated XML.

For example, the following org file, when exported, will produce invalid
XML where the  field still contains the disallowed "<" character.

- org file begins here -
* Foo <- Bar

Some text
- org file ends here -

I'm guessing the ox-rss backend similarly fails to handle XML entities
in other fields as well.

I can provide a patch for this. But, do I use an external library like
xmlgen (https://github.com/philjackson/xmlgen), or do I write my own
find and replace functions like those in ox-html? I think the xmlgen
based approach provides better abstraction and avoids reinventing XML
generation. But, it will introduce an additional dependency.

Please provide thoughts and suggestions.

Thank you,
Arun Isaac.

[O] "global" variables in a babel document...

[Allen S. Rout]

org-version
org "8.2.10"
emacs-version
"24.5.1"


I'm seeing what seems to be some inconsistent treatment of :var header
args.  Or maybe I'm just missing something.   I'm trying to follow:

http://orgmode.org/manual/Header-arguments-in-Org-mode-properties.html#Header-arguments-in-Org-mode-properties

and I find that the local :var works (of course) and the outline level
one also works, but the document-level one does not.

Minimal example, with my results, below.

I'm wondering if I'm thinking about the problem wrong.  What I'm trying
to accomplish is setting, at a document level, a few variables which I
would like to be accessible in every code block in this document.

I know I can set them independently on every block, but that seems
tiresome.


- Allen S. Rout

-
#+PROPERTY:header-args:var tsmuser="query"

* foo
 :PROPERTIES:
 :header-args: :var tsmpass="query"
 :END:

#+name: toy
#+begin_src sh :var bloop="foo"
echo sss ${bloop} ddd
echo sss ${tsmpass} ddd
echo sss ${tsmuser} ddd
#+end_src

#+RESULTS: toy
| sss | foo   | ddd |
| sss | query | ddd |
| sss | ddd   | |
-

Re: [O] Best way of including tikz into latex (pdf and beamer) export with preview?

[briangpowell .]

* ImageMagick is great for shrinking images and/or making thumbnails for
previews and/or maybe the emacs elisp program "thumbs.el" will help:

;;; thumbs.el --- Thumbnails previewer for images files
;;;
;; Author: Jean-Philippe Theberge 
...



On Thu, May 12, 2016 at 4:45 AM, Rainer M Krug  wrote:

> Hi
>
> What is the best way of including tikz into org for latex export (beamer
> and pdf), and to have preview as well?
>
> Thanks,
>
> Rainer
>
> --
> Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
> Biology, UCT), Dipl. Phys. (Germany)
>
> Centre of Excellence for Invasion Biology
> Stellenbosch University
> South Africa
>
> Tel :   +33 - (0)9 53 10 27 44
> Cell:   +33 - (0)6 85 62 59 98
> Fax :   +33 - (0)9 58 10 27 44
>
> Fax (D):+49 - (0)3 21 21 25 22 44
>
> email:  rai...@krugs.de
>
> Skype:  RMkrug
>
> PGP: 0x0F52F982
>

Re: [O] Mixing Python2 and Python3 blocks in one file

[William Henney]

Hi Karl

On Tue, May 17, 2016 at 9:54 AM, Karl Voit  wrote:

> Hi William
>
> * William Henney  wrote:
> >
> > On Sun, May 8, 2016 at 3:31 AM, Karl Voit  wrote:
> >
> > Python2 and Python3 are two different languages. Unfortunately,
> >> Org-mode only uses ~#+BEGIN_SRC python~ for both and uses
> >> python-shell-interpreter to choose/switch the compiler.
> >>
> >> Shouldn't Org-mode introduce ~#+BEGIN_SRC python2~ and ~#+BEGIN_SRC
> >> python3~ to solve this issue in a clean way?
> >>
> >> ~#+BEGIN_SRC python~ can still default to python2.
> >>
> > You can use the :python header argument to the source block, which allows
> > you to specify the path to the python interpreter:
> >
> > #+BEGIN_SRC python :python /Users/will/anaconda/envs/py27/bin/python
>
> Cool, I did not find this parameter yet.
>
> Is this undocumented? http://orgmode.org/org.html does not contain
> the string ":python:" and
> http://orgmode.org/org.html#Language_002dspecific-header-arguments
> also does not mention this parameter.
>
>
It is documented at
http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-python.html

You are right that it would be better if the language-specific babel
documentation were better integrated in the general org info file.  But I
suppose nobody has been sufficiently motivated to do it yet


> > Also see original discussion at
> > https://lists.gnu.org/archive/html/emacs-orgmode/2014-04/msg01042.html
>
> Most interesting to me, thank you.
>
> With the parameter above as a workaround, I can accomplish the
> things I want to do for now. However, I still do think that Python2
> and Python3 as different languages demand different block
> identifiers.
>
> #+BEGIN_SRC python -> defaults to the default python interpreter
> #+BEGIN_SRC python2 -> uses Python2
> #+BEGIN_SRC python3 -> uses Python3
>
> Don't you think?
>
>
To be honest, I disagree that we need different block identifiers.  Python
is hardly the only language to have gone through multiple major versions,
and I don’t think a proliferation of org-babel languages is the answer.
What about C11 vs C99, etc?  I guess a good rule of thumb would be: do the
two versions use the same major mode in emacs?

Why is the :python parameter insufficient for your needs?  You can also use
it for different virtual environments

Cheers

Will



> --
> mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
>> get Memacs from https://github.com/novoid/Memacs <
>
> https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on
> github
>
>
>


-- 

  Dr William Henney, Instituto de Radioastronomía y Astrofísica,
  Universidad Nacional Autónoma de México, Campus Morelia

Re: [O] template for writing Emacs manuals in Org

[Charles C. Berry]

On Tue, 17 May 2016, Thomas S. Dye wrote:


Aloha Nicolas,

Nicolas Goaziou writes:


"Thomas S. Dye"  writes:


Nicolas Goaziou writes:


Once the manual is up-to-date, we might consider moving it to doc/ in
main distribution.


IIRC, Bastien doesn't like this idea.


Really? I admit I would be surprised. Do you recall why so, or do you
have any reference about it?




Maybe this thread:

http://thread.gmane.org/gmane.emacs.orgmode/85574

Where Bastien says: "the day we can export org.org to org.texi with very 
little headache and ad hoc configuration, yes, we will make the move."


which sounds supportive to me.

Chuck

Re: [O] template for writing Emacs manuals in Org

[Nick Dokos]

"Thomas S. Dye"  writes:

> Aloha Nicolas,
>
> Nicolas Goaziou writes:
>
>> "Thomas S. Dye"  writes:
>>
>>> Nicolas Goaziou writes:

 Once the manual is up-to-date, we might consider moving it to doc/ in
 main distribution.
>>>
>>> IIRC, Bastien doesn't like this idea.
>>
>> Really? I admit I would be surprised. Do you recall why so, or do you
>> have any reference about it?
>
> That is all I remember from three years ago, but it's not really
> important.
>
> Looking ahead, the question is whether or not maintaining the
> documentation in Org, rather than texinfo, is a possibility, and, if so,
> what are the conditions under which that change will or will not happen?
>
> What are Bastien's expectations and preferences?
>

I believe the main obstacle is that the emacs policy requires a texinfo
manual for all its component parts. If that can be generated
automatically from the org document, then any objections probably
disappear. Of course, Bastien might object to the extra effort required
to do the conversion, but if the conversion is indeed completely
automatic (or, perhaps more likely, a volunteer can be found to take
care of the conversion and any problems that might arise), then he might
be amenable to it. But it would be an extra step required at release
time and would require some coordination.

--
Nick

Re: [O] template for writing Emacs manuals in Org

[Thomas S. Dye]

Aloha Nicolas,

Nicolas Goaziou writes:

> "Thomas S. Dye"  writes:
>
>> Nicolas Goaziou writes:
>>>
>>> Once the manual is up-to-date, we might consider moving it to doc/ in
>>> main distribution.
>>
>> IIRC, Bastien doesn't like this idea.
>
> Really? I admit I would be surprised. Do you recall why so, or do you
> have any reference about it?

That is all I remember from three years ago, but it's not really
important.

Looking ahead, the question is whether or not maintaining the
documentation in Org, rather than texinfo, is a possibility, and, if so,
what are the conditions under which that change will or will not happen?

What are Bastien's expectations and preferences?

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

[O] bug#2409: bug#2409: 23.0.90; org-mode + viper-mode + ns make typing unresponsive

[Michael Brand]

Hi all

I did some trials in lisp/org/org.el with
- Emacs on OS X built with configure --with-ns, 24.5 and today's
  master
- Org from today's master

1) Removing the line containing org-self-insert-command from

   (org-remap org-mode-map
  'self-insert-command 'org-self-insert-command
  'delete-char 'org-delete-char
  'delete-backward-char 'org-delete-backward-char)

   lets the issue disappear. So the issue seems at least _related_ to
   org-self-insert-command.

2) When I instead remove all forms that contain
   org-self-insert-command or orgtbl-self-insert-command and then add

   ;; Reduce to a passing through to `self-insert-command'.
   (defun org-self-insert-command (N)
 (interactive "p")
 (self-insert-command N))
   ;; Leave this as it was originally.
   (org-remap org-mode-map
  'self-insert-command 'org-self-insert-command
  'delete-char 'org-delete-char
  'delete-backward-char 'org-delete-backward-char)

   the issue remains but I expect it to disappear. Did I not replace
   self-insert-command just with itself and it should behave the same
   way as with change 1)?

Michael

[O] org-tag-alist - fullscreen problem when adding tags

[Peter Sterner]

Hi,

I'm trying out org-mode's tagging-system. In my init.el file I added

(setq org-tag-alist '((:startgroup . nil)
  ("@work" . ?w) ("@home" . ?h)
  ("@tennisclub" . ?t)
  (:endgroup . nil)
  ("laptop" . ?l) ("pc" . ?p)))


Now when I add a tag the entire frame is split up in two windows both
of them showing the *Org tags* buffer.  Is it possible to disable
this?

There are no problems when I don't set org-tag-alist.

Many thanks for considering my request.

Petey

Re: [O] speed keys for plain lists?

[Bill White]

On Mon May 16 2016 at 13:17, Grant Rettke  wrote:

> On Thu, May 12, 2016 at 12:12 PM, Bill White  wrote:
>> But I'm open to suggestions & discussion - now's the time to play around
>> with formats to find the right balance between playing with words and
>> slogging through markup.  Perhaps this isn't the right mailing list for
>> that discussion, though.
>
> If it isn't then please post the name of that list when you find it.

I'm happy to post here, especially since I can't see moving this project
out of orgmode.

> I started out using only lists too because they are exactly as you
> describe them.
>
> Eventually I wanted to attach metadata to the lists, and now I love
> headings.

Could you post an example?

Here's a sample of my second iteration.  A poor man's database - still
pure orgmode and still plain text, but easily parsable:

 - main word|subordinate word, subdivided into grammatical relations A, B, C, 

   - identification
 - main form :: Abbacy
 - obsolete † :: no
 - non-naturalized ‖ :: no
 - pronunciation :: æ•băsi
 - part of speech :: substantive
 - specification :: none
 - status :: default
 - spellings :: 5-6 abbasy, 6-7 abbacie
 - inflections :: none
   - [morphology]
 - derivation (etymology) :: A modification of the earlier
  ABBATIE, assimilated to forms like prelacy, mediaeval Latin
  -acia, -atia.
 - subsequent form-history :: 
 - miscellaneous facts :: 
   - TODO: significations & illustrative quotations

> "Created, developed, and nurtured by Eric Weisstein at Wolfram
> Research" [http://mathworld.wolfram.com/]
>
> Org-Mode makes it easy to do that with whatever document you are
> nurturing.

That describes most of my uses of orgmode - thanks!

bw
--
http://members.wolfram.com/billw

Re: [O] template for writing Emacs manuals in Org

[Nicolas Goaziou]

"Thomas S. Dye"  writes:

> Nicolas Goaziou writes:
>>
>> Once the manual is up-to-date, we might consider moving it to doc/ in
>> main distribution.
>
> IIRC, Bastien doesn't like this idea.

Really? I admit I would be surprised. Do you recall why so, or do you
have any reference about it?

Regards,

Re: [O] Mixing Python2 and Python3 blocks in one file

[John Kitchin]

You can hack this to work:

#+BEGIN_SRC emacs-lisp
(defun org-babel-execute:python2 (body params)
  (let ((org-babel-python-command 
"/Users/jkitchin/Library/Enthought/Canopy_64bit/User/bin/python2"))
(org-babel-execute:python body params)))

#+END_SRC


#+BEGIN_SRC python2
print 'Hello'
#+END_SRC
#+RESULTS:
: Hello


One issue though is no font-lock in the source block. I think it uses
the language to set the mode.

Karl Voit writes:

> Hi William
>
> * William Henney  wrote:
>>
>> On Sun, May 8, 2016 at 3:31 AM, Karl Voit  wrote:
>>
>> Python2 and Python3 are two different languages. Unfortunately,
>>> Org-mode only uses ~#+BEGIN_SRC python~ for both and uses
>>> python-shell-interpreter to choose/switch the compiler.
>>>
>>> Shouldn't Org-mode introduce ~#+BEGIN_SRC python2~ and ~#+BEGIN_SRC
>>> python3~ to solve this issue in a clean way?
>>>
>>> ~#+BEGIN_SRC python~ can still default to python2.
>>>
>> You can use the :python header argument to the source block, which allows
>> you to specify the path to the python interpreter:
>>
>> #+BEGIN_SRC python :python /Users/will/anaconda/envs/py27/bin/python
>
> Cool, I did not find this parameter yet.
>
> Is this undocumented? http://orgmode.org/org.html does not contain
> the string ":python:" and
> http://orgmode.org/org.html#Language_002dspecific-header-arguments
> also does not mention this parameter.
>
>> Also see original discussion at
>> https://lists.gnu.org/archive/html/emacs-orgmode/2014-04/msg01042.html
>
> Most interesting to me, thank you.
>
> With the parameter above as a workaround, I can accomplish the
> things I want to do for now. However, I still do think that Python2
> and Python3 as different languages demand different block
> identifiers.
>
> #+BEGIN_SRC python -> defaults to the default python interpreter
> #+BEGIN_SRC python2 -> uses Python2
> #+BEGIN_SRC python3 -> uses Python3
>
> Don't you think?


--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

Re: [O] Mixing Python2 and Python3 blocks in one file

[Karl Voit]

Hi William

* William Henney  wrote:
>
> On Sun, May 8, 2016 at 3:31 AM, Karl Voit  wrote:
>
> Python2 and Python3 are two different languages. Unfortunately,
>> Org-mode only uses ~#+BEGIN_SRC python~ for both and uses
>> python-shell-interpreter to choose/switch the compiler.
>>
>> Shouldn't Org-mode introduce ~#+BEGIN_SRC python2~ and ~#+BEGIN_SRC
>> python3~ to solve this issue in a clean way?
>>
>> ~#+BEGIN_SRC python~ can still default to python2.
>>
> You can use the :python header argument to the source block, which allows
> you to specify the path to the python interpreter:
>
> #+BEGIN_SRC python :python /Users/will/anaconda/envs/py27/bin/python

Cool, I did not find this parameter yet.

Is this undocumented? http://orgmode.org/org.html does not contain
the string ":python:" and
http://orgmode.org/org.html#Language_002dspecific-header-arguments
also does not mention this parameter.

> Also see original discussion at
> https://lists.gnu.org/archive/html/emacs-orgmode/2014-04/msg01042.html

Most interesting to me, thank you.

With the parameter above as a workaround, I can accomplish the
things I want to do for now. However, I still do think that Python2
and Python3 as different languages demand different block
identifiers.

#+BEGIN_SRC python -> defaults to the default python interpreter
#+BEGIN_SRC python2 -> uses Python2
#+BEGIN_SRC python3 -> uses Python3

Don't you think?

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] template for writing Emacs manuals in Org

[Thomas S. Dye]

Aloha Nicolas,

Nicolas Goaziou writes:
>
> Once the manual is up-to-date, we might consider moving it to doc/ in
> main distribution.

IIRC, Bastien doesn't like this idea.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] Mixing Python2 and Python3 blocks in one file

[William Henney]

Hi Karl

On Sun, May 8, 2016 at 3:31 AM, Karl Voit  wrote:

Python2 and Python3 are two different languages. Unfortunately,
> Org-mode only uses ~#+BEGIN_SRC python~ for both and uses
> python-shell-interpreter to choose/switch the compiler.
>
> Shouldn't Org-mode introduce ~#+BEGIN_SRC python2~ and ~#+BEGIN_SRC
> python3~ to solve this issue in a clean way?
>
> ~#+BEGIN_SRC python~ can still default to python2.
>
>
>
You can use the :python header argument to the source block, which allows
you to specify the path to the python interpreter:


— BEGIN EXAMPLE 

* Default python version
#+name: check-python-version
#+BEGIN_SRC python
import sys
return sys.version
#+END_SRC

#+RESULTS: check-python-version
: 3.4.4 |Anaconda 2.5.0 (x86_64)| (default, Jan  9 2016, 17:30:09)
: [GCC 4.2.1 (Apple Inc. build 5577)]

This is the control experiment.

* Custom python version
#+BEGIN_SRC python :python /Users/will/anaconda/envs/py27/bin/python
import sys
return sys.version
#+END_SRC

#+RESULTS:
: 2.7.11 |Continuum Analytics, Inc.| (default, Dec  6 2015, 18:57:58)
: [GCC 4.2.1 (Apple Inc. build 5577)]

—  END EXAMPLE  

Also see original discussion at

https://lists.gnu.org/archive/html/emacs-orgmode/2014-04/msg01042.html

Will



> I only found those sources/solutions:
>
> http://thread.gmane.org/gmane.emacs.orgmode/47867
> ... file-variables to choose interpretor
>
> http://thread.gmane.org/gmane.emacs.orgmode/47867
> ... workaround with #+srcname (I don't get yet)
>
>
> --
> mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
>> get Memacs from https://github.com/novoid/Memacs <
>
> https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on
> github
>
>
>


-- 

  Dr William Henney, Instituto de Radioastronomía y Astrofísica,
  Universidad Nacional Autónoma de México, Campus Morelia

Re: [O] template for writing Emacs manuals in Org

[Phillip Lord]

Eric Abrahamsen  writes:

> "Thomas S. Dye"  writes:
>
>> Aloha Eric,
>>
>> Eric Abrahamsen writes:
>>
>>> "Thomas S. Dye"  writes:
>>>
 Rasmus writes:

> Once upon a time Tom ported the Org manual.  It's on his github, probably
> under tsdye.

 https://github.com/tsdye/orgmanual
>>>
> I remember where I originally saw this: it was a long thread on
> emacs.devel about moving documentation to HTML, which struck me as a
> terrible idea. I think Org was raised as a way of lowering the barrier
> to writing texinfo manuals for packages, so that we get the best of both
> worlds: write in Org, read in Info. I think it would be a great idea to
> facilitate that, if possible.


I still have a desire to take this forward, although lack the time to do
so on my own.

Having org generate texinfo that plugs directly into existing manuals
would be nice (as it would allow a piecemeal translation). Helping to
define a new HTML based representation (with adding semantics) that
would add the features of info to HTML (and the features of HTML to
info!) would be the ultimate. org-info.js is some of the way there
already.

Then we could use any kind of source (besides org) to generate the HTML,
and hopefully, have it all work together.

Phil

Re: [O] Tags management strategies

[Karl Voit]

* Martin Leduc  wrote:
> Hi !

Hi!

> Tags are a very useful feature to filter information in org-mode. 

Not only in org-mode ;-)[1][2]

> After few years of developing a system to organize my life with
> org-mode, I realize that tags can become rather difficult to deal
> with as we tend to define a lot of tags spread out over several
> org files.

I can copy this from my personal experience as well from PIM
research about tags. Huge field of research. But IMHO difficult to
compare: tags of images, tags for arbitrary files, tags for
bookmarks, tags for reference management, ...

> One general issue is to track all the tags that you have defined in all 
> your org files. 

OK, so you already made the evolutionary step from "hey, there are
tags - let's use as many of them as possible" to a controlled
vocabulary and then a *limited* controlled vocabulary. Good.

> Rather than requesting an org-mode feature that would 
> make a dynamical list of all the defined tags, I personally prefer the 
> approach of making a static list of all preferred tags in one place and 
> to try to keep this list as small as I can. 

That would be my recommendation as well.

> I can achieve this by defining a global list of tags through the
> variable "org-tag-alist", which allows to access all the tags from
> any of my org files, and also because it allows to make
> "grouptags" which are very convenient to organize tags by themes.

I maintain file-local variables for Org-mode files:
  #+TAGS: account advertisement agile ...

Different files cope with different contexts and therefore the
vocabularies overlap very vaguely. For example my business life
(professional SW development in an agile enterprise environment)
requires totally different tags than my private work with PIM
research/tools, contact management, house building, reference
management, and so forth.

> The latter approach seems however limited to the use of a rather small 
> number of tags since in the fast-tag-selection interface, tags entries 
> beyond the 33th are marked with extended ASCCI characters such as ^?, 
> \200, \201,... So my first question is how can I access these tags, and 
> if it is possible, what is the physical limit in terms of the number of 
> tags I can define and access ?

I do not use grouptags and tend to (manually) synchronize file
tags[2] with my private Org-mode tags.

> My second question is a bit more general, but I would like to know what 
> peoples are currently doing to manage, track and make an efficient use 
> of their numerous tags.

Please do read [2] and take a look at [3] with "filetags.py
--tag-gardening". 

> Many thanks,
> Martin

I don't want to spoil your tag-erotic but you should probably
check-out "Everything Is Miscellaneous" by David Weinberger. He
claims that the best meta-data is the content/data itself. To sum it
up, I can imagine him saying something like "Stop adding tags, make
use of advanced methods to filter and re-find according to the
content". He has some really excellent points and the book is worth
reading it in any case. However, I still enjoy maintaining my
controlled vocabulary with tags - especially when working with files.

[1] http://karl-voit.at/tagstore/
[2] http://karl-voit.at/managing-digital-photographs/ + linked GitHub
scripts
[3] https://github.com/novoid/filetags

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] speed keys for plain lists?

[Karl Voit]

* Grant Rettke  wrote:
> On Thu, May 12, 2016 at 12:12 PM, Bill White  wrote:
>> But I'm open to suggestions & discussion - now's the time to play around
>> with formats to find the right balance between playing with words and
>> slogging through markup.  Perhaps this isn't the right mailing list for
>> that discussion, though.
>
> Eventually I wanted to attach metadata to the lists, and now I love headings.

This is exactly my point: you can't add any meta-data to list items.

However, you've got plenty of possibilities to enrich headings with
suitable meta-data: tags, multiple/own drawers, standardized
properties.

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] Best way of including tikz into latex (pdf and beamer) export with preview?

[Rasmus]

Rainer M Krug  writes:

> What is the best way of including tikz into org for latex export (beamer
> and pdf),

I typically create tikz images with R tikzDevice or matplotlib.  In this
case, it’s useful to refer to the generated file:

  file:link/to/pix.tikz

> and to have preview as well?

I believe you’d have to include the code directly in the Org file to make
the preview of latex fragments work.  If this is essential, you could do
something like this:

#+latex_header: \usepackage{tikz}
#+Caption: A special block that’s a figure with a tikz picture.
#+begin_figure
\begin{tikzpicture}
\input{t.tikz} % raw tikz-content w/o \begin{}/end{}
\end{tikzpicture}
#+end_figure

See also the tikz section on ob-latex in worg:


http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-LaTeX.html#sec-4-3

Rasmus

-- 
Hooray!

[O] Best way of including tikz into latex (pdf and beamer) export with preview?

[Rainer M Krug]

Hi

What is the best way of including tikz into org for latex export (beamer
and pdf), and to have preview as well?

Thanks,

Rainer

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: [O] template for writing Emacs manuals in Org

[Eric Abrahamsen]

Rasmus  writes:

> Eric Abrahamsen  writes:
>
>> What might be nice to have in contrib is an exporter derived from the
>> current texinfo exporter, but specifically set up for Gnu project
>> manuals: so it does the copyright header, and index macros, and maybe
>> even the proper DIR integration (?).
>
> Maybe a "GNU template" would be enough? (template as in C-e #).

Yup, that would do it. I think the main thing is just advertising, in
some way, that Org is a suitable authoring tool for Gnus manuals, and
making it as easy as possible.

>> I remember where I originally saw this: it was a long thread on
>> emacs.devel about moving documentation to HTML, which struck me as a
>> terrible idea. I think Org was raised as a way of lowering the barrier
>> to writing texinfo manuals for packages, so that we get the best of both
>> worlds: write in Org, read in Info. I think it would be a great idea to
>> facilitate that, if possible.
>
> There's a recap here:
>
> https://lwn.net/Articles/625072/

Oof, that was depressing to revisit.

Re: [O] template for writing Emacs manuals in Org

[Rasmus]

Eric Abrahamsen  writes:

> What might be nice to have in contrib is an exporter derived from the
> current texinfo exporter, but specifically set up for Gnu project
> manuals: so it does the copyright header, and index macros, and maybe
> even the proper DIR integration (?).

Maybe a "GNU template" would be enough? (template as in C-e #).

> I remember where I originally saw this: it was a long thread on
> emacs.devel about moving documentation to HTML, which struck me as a
> terrible idea. I think Org was raised as a way of lowering the barrier
> to writing texinfo manuals for packages, so that we get the best of both
> worlds: write in Org, read in Info. I think it would be a great idea to
> facilitate that, if possible.

There's a recap here:

https://lwn.net/Articles/625072/

Rasmus

-- 
To err is human. To screw up 10⁶ times per second, you need a computer