Re: [O] Filtering properties in agenda view

[Nick Dokos]

Georg Otto  writes:

> On 01/11/2015 21:49, Brenda Butler wrote:
>
> On Sun, Nov 1, 2015 at 4:04 PM, Georg Otto  wrote:
>
> Thanks for your answer! Unfortunately, it does not work for me as 
> described in the manual.
>
> Try putting the value in double-quotes:
>
> Match: Category="Test"
>
> I should have mentioned that I tried quotes and upper case/ lower case, but 
> no avail... My impression given the message
>
> Headlines with TAGS match: Category="Test"
> Press `C-u r' to search again with new search string
>
> is that for some reason it only searches for tags.
>

See

 (info "(org) Matching tags and properties")

for the syntax.

-- 
Nick

Re: [O] Filtering properties in agenda view

[Brenda Butler]

On Mon, Nov 2, 2015 at 4:35 AM, Georg Otto  wrote:

> On 01/11/2015 21:49, Brenda Butler wrote:
>
>
>
> On Sun, Nov 1, 2015 at 4:04 PM, Georg Otto  wrote:
>
>> Thanks for your answer! Unfortunately, it does not work for me as
>> described in the manual.
>>
>> For example I have an entry with the Property "Test"
>>
>> * TODO test
>> SCHEDULED: <2015-11-01 Sun>
>> :PROPERTIES:
>> :CATEGORY: Test
>> :END:
>>
>>
>> C-c am
>>
>> Match: Category=Test
>>
>
> Try putting the value in double-quotes:
>
> Match: Category="Test"
>
>
> I should have mentioned that I tried quotes and upper case/ lower case,
> but no avail...
>

I tried a few times with different case in the keyword and in the value -
it seems both are case-sensitive and must match the item in the entries
exactly.  And the double-quotes around the value are required.

Now that I look back at your example, I see the search term should be

CATEGORY="Test"


> My impression given the message
>
> Headlines with TAGS match: Category="Test"
> Press `C-u r' to search again with new search string
>
> is that for some reason it only searches for tags.
>

But, on the prompt before you get to this one, it says:

m match a TAGS/PROP/TODO query

bjb

Re: [O] Babel: How to call code in one org file into another org file

[Nick Dokos]

Eric S Fraga  writes:

> On Saturday, 31 Oct 2015 at 16:51, Lawrence Bottorff wrote:
>> I guess I'm saying that the whole `org-babel-lob-ingest` into
>> `org-babel-library-of-babel` exercise should make code ready and available.
>
> But it does.  There are two levels here: the babel codes and the results
> of the codes.  If your babel codes are emacs which define functions,
> these latter functions are not available until the babel codes are
> executed.  However, the babel codes are now there and ready to be
> executed by name.
>
> I would not want ingest to execute the codes for two reasons: many of
> the codes do not make sense without special arguments and there may be
> many such codes.

Indeed - and just to amplify this a bit, you can arrange (and it's
arguably "better" if you have files whose code blocks you want to reuse)
for all the relevant files to be in org-babel-library-of-babel during
initialization; you do not *need* to have them added through the Local
Variables trick: just add org-babel-lob-ingest calls to .emacs.

You can also add the block evaluations in your .emacs, but that is
probably a bad idea as Eric points out. Instead, use Local Variables
with

eval: (org-sbe "foo")

calls to evaluate just what you need for the current buffer (and make
sure that the relevant inferior process running the language interpreter
is started *before* you open the file: emacs-lisp is exempt, since
it's always there).

The difference of opinion arises in the interpretation of "ready and
available". The LOB in this case (and maybe in all cases, but I haven't
used it often enough to be able to make such a statement) behaves more
like an #include file in C, rather than a library of precompiled code
that you link against (think libc.so or equivalent): you need to
"compile" (i.e. evaluate) the code block before it becomes available
to your code.

-- 
Nick

[O] Publishing a Book as PDF and ePub.

[Ian Barton]

Next year our mountaineering club has its 50th anniversary. On the
21st anniversary we published a book of articles written by members of
the club. Luckily the text was written in WordPerfect and I have
converted it to a series of org-mode files, one per chapter. For the
upcoming 50th anniversary we want to make the book available in both
pdf and ePub or mobi format.

Creating ePub doesn't look too hard by exporting to html and using
something like Calibre to make the ePub/mobi file. However, as a Latex
neophyte I was wondering which of the several Latex packages would be
suitable. The structure of the book is very simple. No tables or
formulae but has some photos and cartoons, which I have scanned from
the originals.

All I need is something that will let me format chapter headings,
author attributions and produce a TOC. Templates like Memoir seem to
be vast overkill for my needs and have documentation several times
longer than our book!


--
Best wishes,

Ian.

[O] org-mode git master. ox-latex export errors out due to a table

[Kaushal Modi]

Hi,

I updated my copy of org-mode from git master after about 2-3 weeks. The
ox-latex export used to work fine but now it is failing due to something in
the tables I have in my .org files.  If I comment out those tables, the
ox-latex export works fine. Else it errors out due to (void-function nil)
error.

Here is one of such tables. The below is a MWE which can reproduce the
error I am seeing. The error occurs when I do "C-c C-e l l"

= MWE =

* Severity
#+CAPTION: Macros for reporting messages of different severities
#+NAME: tab__uvm_reporting_macros
|--+--+---|
| Severity | Macro| Default Verbosity |
|--+--+---|
| Info | =`uvm_info("ID", "Message", UVM_MEDIUM)= | No default|
| Warning  | =`uvm_warning("ID", "Message")=  | =UVM_NONE=|
| Error| =`uvm_error("ID", "Message")=| =UVM_NONE=|
| Fatal| =`uvm_fatal("ID", "Message")= [fn:1] | =UVM_NONE=|
|--+--+---|


* Footnotes
[fn:1] Simulation is quit when this macro is called


= Backtrace =

Debugger entered--Lisp error: (void-function nil)
  nil(((paragraph (:begin 740 :end 785 :contents-begin 740 :contents-end
785 :post-blank 0 :post-affiliated 740 :parent (footnote-definition (:label
"fn:1" :begin 733 :end 785 :contents-begin 740 :contents-end 785
:post-blank 0 :post-affiliated 733 :parent (section (:begin 733 :end 785
:contents-begin 733 :contents-end 785 :post-blank 0 :post-affiliated 733
:parent (headline ... #5)) #3)) #1)) #("Simulation is quit when this macro
is called\n" 0 45 (:parent #1)
  #[257 "\303 \300\"\2050 \301 \301\242B\240\210\304 \211;\203 \305\306
#\202# \307 A@ \"\266\202\310=\2050 \302\311 \300\"!\207" [(:export-options
nil :input-buffer "ox-latex-table-export-error.org" :input-file
"/home/kmodi/sandbox/org/ox-latex-table-export-error.org" :latex-class
"article" :latex-class-options nil :latex-header nil :latex-header-extra
nil :description nil :keywords nil :subtitle nil
:latex-active-timestamp-format "\\textit{%s}" :latex-caption-above (table)
:latex-classes (("article" "\\documentclass[11pt]{article}"
("\\section{%s}" . "\\section*{%s}") ("\\subsection{%s}" .
"\\subsection*{%s}") ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}") ("\\subparagraph{%s}" .
"\\subparagraph*{%s}")) ("report" "\\documentclass[11pt]{report}"
("\\part{%s}" . "\\part*{%s}") ("\\chapter{%s}" . "\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}") ("\\subsection{%s}" .
"\\subsection*{%s}") ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
("book" "\\documentclass[11pt]{book}" ("\\part{%s}" . "\\part*{%s}")
("\\chapter{%s}" . "\\chapter*{%s}") ("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}") ("\\subsubsection{%s}" .
"\\subsubsection*{%s}"))) :latex-default-figure-position "H"
:latex-default-table-environment "tabular" :latex-default-table-mode table
:latex-diary-timestamp-format "\\textit{%s}" :latex-footnote-separator
"\\textsuperscript{,}\\," :latex-format-drawer-function #[514 "\207" [] 3
"\n\n(fn _ CONTENTS)"] :latex-format-headline-function
org-latex-format-headline-default-function
:latex-format-inlinetask-function
org-latex-format-inlinetask-default-function :latex-hyperref-template
"\\hypersetup{\n pdfauthor={%a},\n pdftitle={%t},\n pdfkeywords={%k},\n
pdfsubject={%d},\n pdfcreator={%c}, \n pdflang={%L}}\n"
:latex-image-default-height "" :latex-image-default-option ""
:latex-image-default-width ".9\\linewidth" ...) (((footnote-reference
(:label "fn:1" :type standard :begin 610 :end 616 :contents-begin nil
:contents-end nil :post-blank 0 :parent (table-cell (:begin 579 :end 622
:contents-begin 580 :contents-end 616 :post-blank 0 :parent ...) (verbatim
...) #4) nil org-export-footnote-first-reference-p :type
get-text-property 0 plist-get standard org-export-get-footnote-definition]
7 "\n\n(fn REF)"]((footnote-reference (:label "fn:1" :type standard :begin
610 :end 616 :contents-begin nil :contents-end nil :post-blank 0 :parent
(table-cell (:begin 579 :end 622 :contents-begin 580 :contents-end 616
:post-blank 0 :parent (table-row (:type standard :begin 567 :end 643
:contents-begin 568 :contents-end 642 :post-blank 0 :post-affiliated 567
:parent (table (:begin 12 :end 719 :type org :tblfm nil :contents-begin 111
:contents-end 719 :value nil :post-blank 0 :post-affiliated 111 :caption
... :name "tab__uvm_reporting_macros" :parent ...) (table-row ...)
(table-row ... ... ... ...) (table-row ...) (table-row ... ... ... ...)
(table-row ... ... ... ...) (table-row ... ... ... ...) #4 (table-row
...))) (table-cell (:begin 568 :end 579 :contents-begin 569 :contents-end
574 :post-blank 0 :parent #4) #("Fatal" 0 5 (:parent #5))) #2 (table-cell
(:begin 622 :end 642 :contents-begin 

Re: [O] sh - script: how to control the output.

[Johann Spies]

>
> You could try out some of the options for the ":results" header
> argument, as described here:
>
> http://orgmode.org/manual/results.html#results
>
>
>
Thanks Myles.  After a bit of experimenting I got this to work (I have to
remove the *example*  lines to make a table of the output.  But that is OK.


#+BEGIN_SRC sh :results verbatim
#!/bin/sh
echo "\d wos.za_wos_subject_percent_v" | psql -h localhost -p 63334
book_citation | sed '1,2d' | \
sed '/[|+]/s/^/|/'| sed -e '/[|+]/s/$/|/'

#+END_SRC

#+results:
#+begin_example
 View "wos.za_wos_subject_percent_v"
|Column |  Type   | Modifiers |
|---+-+---|
| id| integer | |
| subject   | citext  | |
| pubyear   | integer | |
| sa_papers | numeric | |
| world_papers  | bigint  | |
| za_percentage | real| |
| rest  | real| |

#+end_example

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

Re: [O] Org Babel resolution of `:var` value reference inconsistent

[Nick Dokos]

Andreas Leha  writes:

> ...
> So, to me it is more surprising that the manual execution works.  For
> instance, I might have two tables with the same name.  Then, COMMENTing
> one of them should ensure that the other one is used.
>

COMMENT works during export *only* I believe. You have to explicitly
comment out one of the tables otherwise. If there are two tables with
the same name, babel will use the one nearer the beginning of the file
and ignore the second one (I determined this experimentally, *not* by
reading and understanding the code - ymmv).

-- 
Nick

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Nick Dokos]

Thank you for providing the backtrace, but ... You knew there was
a "but" coming, right? :-)

Although some people can make sense of a backtrace produced with
compiled code, it is far more useful to provide a backtrace produced
with *uncompiled* code. What you have to do is

C-u M-x org-reload RET

and *then* produce the backtrace. If you want to go back to compiled
code afterwards, do the M-x org-reload  without the C-u.

See

  (info "(org) Feedback")

particularly the section entitled "How to create a useful backtrace".

Also, please always provide the org-mode version:

C-u M-x org-version

FWIW, I can export your sample to PDF with no problems. I'm on
Org-mode version 8.3.2 (release_8.3.2-178-g96681f)

--
Nick

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Kaushal Modi]

> Although some people can make sense of a backtrace produced with
compiled code, it is far more useful to provide a backtrace produced
with *uncompiled* code.

Apologies, I was unaware of that. I should have read that Info node first.
Below is a gist link to the full backtrace with uncompiled code.

https://gist.github.com/kaushalmodi/b76de1274b7a7bfe6020

Here's more info about this issue I am facing:
- I cannot reproduce this error in emacs -Q with the same git version of
org-mode in load-path.
- But I can reproduce this error consistently even if I "delete/move" my
~/.emacs.d/init.el and ~/.emacs.d/elpa. I do not have a ~/.emacs file.
While this step should be equivalent to emacs -Q, it doesn't seem to work
that way for me. Even the load-path var is exact same as with emacs -Q (I
install org-mode in the share/emacs dir).

While I resolve the mystery of why removing the init.el is not the same as
emacs -Q for me, I hope that the backtrace from uncompiled code can help
point the problem in my emacs setup.

Many thanks!

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Kaushal Modi]

Also, I am on the latest org-mode and emacs builds:

org-mode version: Org-mode version 8.3.2 (release_8.3.2-251-g4ca117 @
/home/kmodi/usr_local/apps/6/emacs/master/share/emacs/site-lisp/org/)
emacs-version:
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=5401bb8645f955b6fde8c0a5e5c8cf5ec1cab626

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Kaushal Modi]

Some more info:

I cannot recreate this error when using
- my emacs config
- the same emacs build from git
- BUT the latest org-plus-contrib from org elpa: Org-mode version 8.3.2
(8.3.2-10-g00dacd-elpaplus @
/home/kmodi/.emacs.d/elpa_25_0/org-plus-contrib-20151005/)

So it is some change between:
- 8.3.2-10-g00dacd-elpaplus, and
- release_8.3.2-251-g4ca117

Now I just need to decode what "g4ca117" means in that version that does
not work for me. It doesn't seem to be any part of the git hash for the
commit I am on (
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4
)

Re: [O] [PATCH] org-babel-execute-src-block-region

[Charles C. Berry]

On Sun, 1 Nov 2015, Carlos Henrique Machado S Esteves wrote:


Hello, I find it useful to be able to execute only a region of a source
code block, so I've implemented a new function for that. I've tested it
with MATLAB and Python, but it should work for any mode, since it calls
org-babel-execute-src-block.



You might want to check that point and mark are both inside the src 
block. Otherwise, the results are unpredictable.


Also note that:

ess-mode, python-mode, sh-mode and octave-mode already provide this 
capability (and a lot more) for R, python, shell scripts, octave/matlab 
and some other languages from the edit buffer.


`org-babel-demarcate-block' gives the user the ability to break up src 
blocks into smaller pieces so they can be run independently.


Best,

Chuck

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Nick Dokos]

Kaushal Modi  writes:

>> Although some people can make sense of a backtrace produced with
> compiled code, it is far more useful to provide a backtrace produced
> with *uncompiled* code.
>
> Apologies, I was unaware of that. I should have read that Info node first.
> Below is a gist link to the full backtrace with uncompiled code.
>
> https://gist.github.com/kaushalmodi/b76de1274b7a7bfe6020
>

I can reproduce it with the latest version too. It may have something to
do with the recent conversion of ox-latex to lexical binding: I see
closures all over the backtrace.

> Here's more info about this issue I am facing:
> - I cannot reproduce this error in emacs -Q with the same git version of 
> org-mode in load-path.
> - But I can reproduce this error consistently even if I "delete/move" my 
> ~/.emacs.d/init.el and ~
> /.emacs.d/elpa. I do not have a ~/.emacs file. While this step should be 
> equivalent to emacs -Q, it
> doesn't seem to work that way for me. Even the load-path var is exact same as 
> with emacs -Q (I install
> org-mode in the share/emacs dir).
>
> While I resolve the mystery of why removing the init.el is not the same as 
> emacs -Q for me, I hope that
> the backtrace from uncompiled code can help point the problem in my emacs 
> setup.
>
> Many thanks!

--
Nick

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Nick Dokos]

Kaushal Modi  writes:

> Some more info:
>
> I cannot recreate this error when using
> - my emacs config
> - the same emacs build from git
> - BUT the latest org-plus-contrib from org elpa: Org-mode version 8.3.2 
> (8.3.2-10-g00dacd-elpaplus @ /
> home/kmodi/.emacs.d/elpa_25_0/org-plus-contrib-20151005/)
>
> So it is some change between:
> - 8.3.2-10-g00dacd-elpaplus, and
> - release_8.3.2-251-g4ca117
>

My guess is that it's this commit:

commit 8bccb2131374bba8c82c2774abb34af488826ce4
Author: Nicolas Goaziou 
Date:   Thu Oct 29 19:03:52 2015 +0100

ox-latex: Use lexical binding

but I haven't reverted it yet to check.

> Now I just need to decode what "g4ca117" means in that version that does not 
> work for me. It doesn't
> seem to be any part of the git hash for the commit I am on ( 
> http://orgmode.org/cgit.cgi/org-mode.git/
> commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4 )

The "g" stands for "git" and it's not part of the SHA1: 4ca117 are
the first six digits of the SHA1 at the HEAD of the branch:

commit 4ca1179c9e9c707267ac3738cc7c8442001b204b
Author: Nicolas Goaziou 
Date:   Sun Nov 1 00:58:57 2015 +0100

ox-odt: Use lexical binding

--
Nick

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Kaushal Modi]

> The "g" stands for "git" and it's not part of the SHA1: 4ca117 are the
first six digits of the SHA1 at the HEAD of the branch

Ah, now that you spell it out, it's obvious. I swear I kept staring at the
git hash to find the "117" in "g4ca117" in
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=4ca1179c9e9c707267ac3738cc7c8442001b204b
but I never saw it! Now it stands out clear.

And of course, I should have realized that "g" can never be part of the hex
hash.

Thanks, and also thanks for confirming that you see this error too.

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Nick Dokos]

Kaushal Modi  writes:

> @Nick Dokos Are you are on a commit before or after this lexical binding 
> change? http://orgmode.org/
> cgit.cgi/org-mode.git/commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4
>
> The failure symtoms in my backtrace look like they could be related to this 
> change.

I think that is right.

The problem seems to be with the search-refs function defined in the
let* in org-latex--delayed-footnotes-definitions and passed down to
org-element-map which tries to find it in the lexical environment and
fails.

--
Nick

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Kaushal Modi]

@Nick Dokos Are you are on a commit before or after this lexical binding
change?
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4

The failure symtoms in my backtrace look like they could be related to this
change.

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Nick Dokos]

Nick Dokos  writes:

> Kaushal Modi  writes:
>
>> @Nick Dokos Are you are on a commit before or after this lexical binding 
>> change? http://orgmode.org/
>> cgit.cgi/org-mode.git/commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4
>>
>> The failure symtoms in my backtrace look like they could be related to this 
>> change.
>
> I think that is right.
>
> The problem seems to be with the search-refs function defined in the
> let* in org-latex--delayed-footnotes-definitions and passed down to
> org-element-map which tries to find it in the lexical environment and
> fails.
>

Brute-forcing search-refs to be a special variable (i.e. dynamically,
rather than lexically, bound) seems to fix the error, although I doubt
it's the ultimate solution:

--8<---cut here---start->8---
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 060f423..3279be7 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -1459,6 +1459,8 @@ INFO is a plist used as a communication channel.  See
   ;; Else use format string.
   (t (format fmt text)
 
+(defvar search-refs)   ; For byte-compiler.
+
 (defun org-latex--delayed-footnotes-definitions (element info)
   "Return footnotes definitions in ELEMENT as a string.
 
@@ -1481,7 +1483,6 @@ just outside of it."
(org-export-get-footnote-definition ref info) info
;; Find every footnote reference in ELEMENT.
(let* (all-refs
- search-refs   ; For byte-compiler.
  (search-refs
   (function
(lambda (data)
--8<---cut here---end--->8---

--
Nick

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Nicolas Goaziou]

Hello,

Nick Dokos  writes:

> Kaushal Modi  writes:
>
>> @Nick Dokos Are you are on a commit before or after this lexical binding 
>> change? http://orgmode.org/
>> cgit.cgi/org-mode.git/commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4
>>
>> The failure symtoms in my backtrace look like they could be related to this 
>> change.
>
> I think that is right.
>
> The problem seems to be with the search-refs function defined in the
> let* in org-latex--delayed-footnotes-definitions and passed down to
> org-element-map which tries to find it in the lexical environment and
> fails.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Kaushal Modi]

Thanks Nick. That patch resolves the issue for now. At least, all my pdf
exports are working fine as before.

Re: [O] Repeated task, every other day, at a specific time, but how?

[Sharon Kimble]

Sharon Kimble  writes:

> I'm trying to schedule a task, which is a habit, for every other day at
> 0900, like this -
>
> ** TODO put slow cooker on for tea
> SCHEDULED: <2015-10-28 Wed 09:00 .+2>
> :PROPERTIES:
> :LAST_REPEAT: [2015-09-09 Wed 07:17]
> :END:
> :LOGBOOK:  
> :STYLE: habit
> :REPEAT_TO_STATE: TODO
> :END:
>
> But it is consistently failing, and refusing to update for the next
> required day.
>
> I can get it working if I omit the time, but I'd rather have it working
> with the time as well.
>
> So where am I going wrong then please?

The simple answer I've found, for the benefit of the archives, is to just
leave out the "." in front of +2d, and it then works as expected.

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.0, fluxbox 1.3.7, emacs 24.5.1


signature.asc
Description: PGP signature

Re: [O] Publishing a Book as PDF and ePub.

[Marcin Borkowski]

On 2015-11-02, at 16:37, Ian Barton  wrote:

> Next year our mountaineering club has its 50th anniversary. On the
> 21st anniversary we published a book of articles written by members of
> the club. Luckily the text was written in WordPerfect and I have
> converted it to a series of org-mode files, one per chapter. For the
> upcoming 50th anniversary we want to make the book available in both
> pdf and ePub or mobi format.
>
> Creating ePub doesn't look too hard by exporting to html and using
> something like Calibre to make the ePub/mobi file. However, as a Latex
> neophyte I was wondering which of the several Latex packages would be
> suitable. The structure of the book is very simple. No tables or
> formulae but has some photos and cartoons, which I have scanned from
> the originals.
>
> All I need is something that will let me format chapter headings,
> author attributions and produce a TOC. Templates like Memoir seem to
> be vast overkill for my needs and have documentation several times
> longer than our book!

I agree that memoir might not be the best idea.  (I had bad experience
with it, probably mainly due to its monolithic design.)

One way would be the koma-script packages.  (I never used them, but many
people are satisfied with them.)

Also, the TeX showcase (https://www.tug.org/texshowcase/) might give you
some inspiration.

And if you are brave enough, you might want to look at ConTeXt:
http://wiki.contextgarden.net/Main_Page .  It is an alternative (i.e.,
not LaTeX-related), TeX-based typesetting engine.  IMHO it is more
advanced (at least typographically) and /much/ better designed than
LaTeX.  It seems there is no ConTeXt exporter for Org-mode (however,
this should not be difficult to fix).  One of he advantages of ConTeXt
is that it supposedly can produce an Epub ebook (though this never
worked for me - OTOH, I tried it some three years ago, and I would guess
the progress might be substantial).  Another is an active and helpful
(albeit small compared to LaTeX's) community.

Also, if/when you have /specific/ questions on how to achieve something
in LaTeX, http://tex.stackexchange.com/ is a good place to ask
questions.  (It is much friendlier and relaxed than SO, btw.)

Hth

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: [O] org-mode git master. ox-latex export errors out due to a table

[Kaushal Modi]

Thanks to you both for the quick solution and the upstream fix.

Re: [O] Org Babel resolution of `:var` value reference inconsistent

[Andreas Leha]

Hi myq,

myq  writes:
> Sometime since Org version 8.3beta and now, the way Org Babel resolves
> the value of the `:var` header argument when assigned to a reference has
> changed.
>
> Previously, the following would work when exporting:
>
> * test
>
> #+BEGIN_SRC R :var dat=table-data
>   print(summary(dat));
> #+END_SRC
>
> ** COMMENT
>
> #+TBLNAME: table-data
> | number | measurement |
> |+-|
> | 1  | 10  |
>
>
> The above /still/ works when manually evaluating the block (C-c C-c whil
> in the block), but when exporting, the following error is thrown:
> `org-babel-ref-resolve: Reference `table-data' not found in this buffer`
>
> Curiously, the following tweak works for both manual evaluation and for
> exporting and produces the same results that the above file used to
> produce:
>
> #+OPTIONS: inline:nil
> * test
>
> #+BEGIN_SRC R :var dat=table-data
>   print(summary(dat));
> #+END_SRC
>
> *** test
> #+TBLNAME: table-data
> | number | measurement |
> |+-|
> | 1  | 10  |
> *** END
>
> This seems to be a bug, but perhaps there is a reason for this new
> behaviour?
>
> Thank you in advance for any insights.

There are two ways to exclude subtrees from export: the COMMENT keyword
and the :noexport: tag.  I think what you want to use here is the
:noexport: tag.

Here is the difference:

- COMMENTing a subtree is meant to be (roughly?) the same as putting '# '
  at the beginning of all the lines from that region.

- The :noexport: tag will simply skip the region from export.

So, to me it is more surprising that the manual execution works.  For
instance, I might have two tables with the same name.  Then, COMMENTing
one of them should ensure that the other one is used.

HTH,
Andreas

Re: [O] Filtering properties in agenda view

[Georg Otto]

On 01/11/2015 21:49, Brenda Butler wrote:
>
>
> On Sun, Nov 1, 2015 at 4:04 PM, Georg Otto  > wrote:
>
> Thanks for your answer! Unfortunately, it does not work for me as
> described in the manual.
>
> For example I have an entry with the Property "Test"
>
> * TODO test
> SCHEDULED: <2015-11-01 Sun>
> :PROPERTIES:
> :CATEGORY: Test
> :END:
>
>
> C-c am
>
> Match: Category=Test
>
>
> Try putting the value in double-quotes:
>
> Match: Category="Test"
>

I should have mentioned that I tried quotes and upper case/ lower case,
but no avail... My impression given the message

> Headlines with TAGS match: Category="Test"
> Press `C-u r' to search again with new search string
is that for some reason it only searches for tags.


G

Re: [O] sh - script: how to control the output.

[Myles English]

Hello Johann,

Johann Spies writes:

> In the normal shell, I can do:
>
>  echo '\d wos.wos_papers_by_subject_mv' | psql -h localhost -p 63334
> book_citation | grep '[+|]'
>
> and get the output:
>
>   Column  |  Type   | Modifiers
> --+-+---
>  id   | integer |
>  subject  | citext  |
>  articles | bigint  |
>
> When I try this in org-mode:
>
>
> #+BEGIN_SRC sh
>
> echo '\d wos.wos_papers_by_subject_mv' | psql -h localhost -p 63334
> book_citation | grep '[+|]'
>
>
> #+END_SRC
>
> #+results:
> | Column   |   |   | Type|   |   | Modifiers |
> | --+-+--- |   |   | |   |   |   |
> | id   |   |   | integer |   |   |   |
> | subject  |   |   | citext  |   |   |   |
> | articles |   |   | bigint  |   |   |   |
>
> What should I do to get the following in org-mode as a result:

You could try out some of the options for the ":results" header
argument, as described here:

http://orgmode.org/manual/results.html#results

Myles

[O] bug in org-habits

[Mark A. Hershberger]

org-habit.el is sensitive to the ordering PROPERTIES and SCHEDULED
and expects them /in only/ the following order:

 * TODO habit name
 SCHEDULED: <2015-11-03 Tue 07:00 .+1d>
 :PROPERTIES:
 :LAST_REPEAT: [2015-11-02 Mon 07:54]
 :STYLE: habit
 :END:

Any other ordering, or doubling of PROPERTIES (e.g. STYLE in one, LAST
REPEAT in another) and the habit will show up as a simple scheduled item
and not a habit in the agenda view.

org-version: 8.3.2
emacs-version: 24.4.1

Let me know if I need to provide any other information.

Thanks!

Mark.


-- 
http://hexmode.com/

Love every man in spite of his falling into sin. Never mind the sins,
but remember that the foundation of the man is the same - the image of
God.  -- St. John of Kronstadt