Re: [O] [PATCH][ox-koma-letter] changed-in-buffer, subject, minor fixes
Hi Rasmus, Rasmus writes: > Quick but unrelated question. I'm updating the Worg page and I > noticed that the customize-group for ox-koma-letter is > org-export-koma-letter. Given that other groups are org-latex and > org-html etc., should the group not be called org-koma-letter? Unless I miss something, other groups are org-export-html org-export-latex etc. so org-export-koma-letter seems right. -- Bastien
Re: [O] [PATCH][ox-koma-letter] changed-in-buffer, subject, minor fixes
Hello, Rasmus writes: > Given that other groups are org-latex and > org-html etc., should the group not be called org-koma-letter? No. Other groups are `org-export-latex', `org-export-html'... Regards, -- Nicolas Goaziou
Re: [O] Quotes for LaTeX export
Nick Dokos writes:
> IIRC, there was support for csquotes in the old exporter[fn:1] but I guess
> it went away when the new exporter came along.
Yes, it'd be good to make it possible again to use
\usepackage{csquotes} and \enquote{something}.
--
Bastien
[O] [babel] shell does not unquote
i don't know why the shell does not unquote here: #+BEGIN_SRC sh :results verbatim output :var how="a 'b' \c \"d\" e" :var dothis="echo \"hi\"" echo $how $dothis #+END_SRC #+RESULTS: #+begin_example a 'b' c "d" e "hi" #+end_example thanks. samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] [babel] cannot comment out noweb references
hi eric, #+BEGIN_SRC org :results verbatim output :noweb yes :noweb-ref whatever a #+END_SRC # #+BEGIN_SRC org :results verbatim output :noweb yes :noweb-ref whatever # b # #+END_SRC #+BEGIN_SRC sh :results output :noweb yes echo <> #+END_SRC it is a bug that babel tries to use b. babel tries to use COMMENT comments also. samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] mis-alignment in org-tables with Tibetan characters
Hi Steffan On Wed, Feb 5, 2014 at 1:00 AM, Steffan Iverson wrote: > Michael, that test case you suggest does indeed cause the same spacing > problem. So this isn't a problem from the vowel stacking in Tibetan, Such combining characters and and also double width characters may still remain as separate issues for Org table alignment and maybe the patches from Eric Abrahamsen are required to resolve one or both. > because of the type of font it is? Sorry, generally new to Emacs so > I'm not sure how to move forward with that insight. Several steps to go with choosing font(s) and probably tweaking set-fontset-font which I don't have much insight neither. Regarding the choice of font: Is there any font that is monospaced even in the Tibetan range at all? What does a "cat" (not "less" or any other ncurses) of your file look like in different terminal emulators like xterm, gnome-terminal etc. on different OSes? What does "locale" from these terminal emulators tell? Regarding a possible first step with Emacs set-fontset-font: How did the glyph for INFINITY from the test look like, was this aligned for you?: xx| ∞∞| Michael
Re: [O] [babel] cannot comment out noweb references
Samuel Wales writes: > This: > > #+BEGIN_SRC org :exports none :noweb-ref whatever > ... > > with "# " or COMMENT still tries to be read by Babel. The latter > works as if not commented. The former errors. > > Hope that's enough to reproduce. > I don't understand. Where are you putting the comment character? Can you provide an example? > > Thanks. > > Samuel -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
[O] [babel] cannot comment out noweb references
This: #+BEGIN_SRC org :exports none :noweb-ref whatever ... with "# " or COMMENT still tries to be read by Babel. The latter works as if not commented. The former errors. Hope that's enough to reproduce. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] [PATCH][ox-koma-letter] changed-in-buffer, subject, minor fixes
Quick but unrelated question. I'm updating the Worg page and I noticed that the customize-group for ox-koma-letter is org-export-koma-letter. Given that other groups are org-latex and org-html etc., should the group not be called org-koma-letter? –Rasmus PS: Sorry for not starting a new thread. -- Dung makes an excellent fertilizer
Re: [O] [PATCH][ox-koma-letter] changed-in-buffer, subject, minor fixes
Alan Schmitt writes:
> Rasmus: do you want to change these, or should I do it and apply the
> patch? (The former would be simpler, I have to say.)
Attached. Sorry about the delay. They should fix Nicholas'
'concerns'.
–Rasmus
--
Vote for proprietary math!
>From 8f3e69f5ca3d0153b6f4c80b74c7aa6f422c86e5 Mon Sep 17 00:00:00 2001
From: Rasmus
Date: Sat, 25 Jan 2014 14:08:15 +0100
Subject: [PATCH 1/2] Documentation fixes for ox-koma-script.el
* ox-koma-letter.el commentary (org-koma-letter-use-backaddress):
Better documentation.
---
contrib/lisp/ox-koma-letter.el | 30 ++
1 file changed, 18 insertions(+), 12 deletions(-)
diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index 7f2cd22..0d15956 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -34,14 +34,14 @@
;; On top of buffer keywords supported by `latex' back-end (see
;; `org-latex-options-alist'), this back-end introduces the following
;; keywords:
-;; - "CLOSING" (see `org-koma-letter-closing'),
-;; - "FROM_ADDRESS" (see `org-koma-letter-from-address'),
-;; - "LCO" (see `org-koma-letter-class-option-file'),
-;; - "OPENING" (see `org-koma-letter-opening'),
-;; - "PHONE_NUMBER" (see `org-koma-letter-phone-number'),
-;; - "SIGNATURE" (see `org-koma-letter-signature')
-;; - "PLACE" (see `org-koma-letter-place')
-;; - and "TO_ADDRESS". If unspecified this is set to "\mbox{}".
+;; - CLOSING: see `org-koma-letter-closing',
+;; - FROM_ADDRESS: see `org-koma-letter-from-address',
+;; - LCO: see `org-koma-letter-class-option-file',
+;; - OPENING: see `org-koma-letter-opening',
+;; - PHONE_NUMBER: see `org-koma-letter-phone-number',
+;; - SIGNATURE: see `org-koma-letter-signature',
+;; - PLACE: see `org-koma-letter-place',
+;; - TO_ADDRESS: If unspecified this is set to "\mbox{}".
;;
;; TO_ADDRESS and FROM_ADDRESS can also be specified using heading
;; with the special tags specified in
@@ -67,8 +67,9 @@
;; (see `org-koma-letter-special-tags-after-letter').
;;
;; The following variables works differently from the main LaTeX class
-;; - "AUTHOR": default to user-full-name but may be disabled. (see org-koma-letter-author),
-;; - "EMAIL": same as AUTHOR, (see org-koma-letter-email),
+;; - AUTHOR: Default to user-full-name but may be disabled.
+;; (See also `org-koma-letter-author'),
+;; - EMAIL: Same as AUTHOR. (see also `org-koma-letter-email'),
;;
;; Headlines are in general ignored. However, headlines with special
;; tags can be used for specified contents like postscript (ps),
@@ -105,11 +106,16 @@
;; \[EXTRA]"))
;;
;; Then, in your Org document, be sure to require the proper class
-;; with :
+;; with:
;;
;;#+LATEX_CLASS: my-letter
;;
;; Or by setting `org-koma-letter-default-class'.
+;;
+;; You may have to load (LaTeX) Babel as well, e.g., by adding
+;; it to `org-latex-packages-alist',
+;;
+;;(add-to-list 'org-latex-packages-alist '("AUTO" "babel" nil))
;;; Code:
@@ -252,7 +258,7 @@ This option can also be set with the OPTIONS keyword, e.g.:
:group 'org-export-koma-letter)
(defcustom org-koma-letter-use-backaddress nil
- "Non-nil prints return address in small line above to address.
+ "Non-nil prints return address in line above to address.
This option can also be set with the OPTIONS keyword, e.g.:
\"backaddress:t\"."
:group 'org-export-koma-letter
--
1.8.5.3
>From a55d3611d5ae6b04c64513490d68a9959672c86f Mon Sep 17 00:00:00 2001
From: Rasmus
Date: Sat, 25 Jan 2014 14:15:03 +0100
Subject: [PATCH 2/2] Allow separate subject and title in ox-koma-letter
* ox-koma-letter.el (org-koma-letter-use-title): New variable.
(org-koma-letter-prefer-subject): New variable.
(org-koma-letter-template): Allow separate subject and title.
---
contrib/lisp/ox-koma-letter.el | 41 +
1 file changed, 37 insertions(+), 4 deletions(-)
diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index 0d15956..8a3054b 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -70,6 +70,8 @@
;; - AUTHOR: Default to user-full-name but may be disabled.
;; (See also `org-koma-letter-author'),
;; - EMAIL: Same as AUTHOR. (see also `org-koma-letter-email'),
+;; - TITLE: May be the letter title or subject depending on
+;; `org-koma-letter-prefer-subject'.
;;
;; Headlines are in general ignored. However, headlines with special
;; tags can be used for specified contents like postscript (ps),
@@ -336,6 +338,16 @@ This option can also be set with the OPTIONS keyword, e.g.:
:group 'org-export-koma-letter
:type 'boolean)
+(defcustom org-koma-letter-use-title t
+ "Non-nil means use a title in the letter if present.
+This option can also be set with the OPTIONS keyword,
+e.g. \"with-title:nil\".
+
+See also `org-koma-letter-prefer-subject' for the handling of
+title versus subject."
+ :gro
Re: [O] mis-alignment in org-tables with Tibetan characters
Michael, that test case you suggest does indeed cause the same spacing problem. So this isn't a problem from the vowel stacking in Tibetan, because of the type of font it is? Sorry, generally new to Emacs so I'm not sure how to move forward with that insight. On Tue, Feb 4, 2014 at 10:13 AM, Michael Brand wrote: > Hi Steffan > > On Mon, Feb 3, 2014 at 6:33 AM, Steffan Iverson > wrote: > > Screenshot: http://oi59.tinypic.com/lz893.jpg > > Judging from e. g. this part > | རྐུས་ | rkus | > | གསོས་ | gsos | > in your screenshot my speculation is that you get glyphs from not only your > default monospace font but also from other (maybe variable width) font(s). > Either because some glyphs are not available in your default monospace font > or are not used due to an incomplete configuration with set-fontset-font. > > For a diagnosis in this direction I would check the alignment of "|" after > some characters just repeated like here: > > xx| > ་་| > གག| > རར| > སས| > ུུ| > ོོ| > ྐྐ| > xx| > ∞∞| > > Michael >
Re: [O] export tables to html and odt, table borders
Hi Uwe, Uwe Brauer writes: > In orgmode 7.8 there was a variable > (org-export-html-table-tag > which allowed my to configure the table boundary to my liking for > example: > > > " frame=\"border\">") > > > Now I installed the latest version available in elpa for GNU emacs24 and > cannot find this variable. What is the corresponding new variable? See org-html-table-default-attributes and org-html-table-header-tags org-html-table-data-tags org-html-table-row-tags > Is there anything similar for the odt exporter? I don't know. HTH, -- Bastien
[O] Moving by block in the block agenda
Hi, I have a block agenda defined which is mostly taken from Bernt Hansen's org-mode.org. Some of the blocks contain many entries. I am trying to find out if there is a simple way to navigate between agenda blocks. The most likely thing I found was org-agenda-goto-block-beginning but it doesn't appear to do that. What am I missing? -- Kind regards Bart
Re: [O] plain lists folded by default
Rémy Abergel writes: > Maybe it is due to the fact I "replied to all" from one of my old > messages, deleting the content and changing the email subject :'-( That would do it :-) > You mean I should have started from a blank email right? > Yes. > Well sorry for that, and thank you again for your answers. > No problem (as long as you don't it again :-) ) Nick
Re: [O] Quotes for LaTeX export
Rasmus writes:
> Hi Laurens,
>
> Laurens Van Houtven <_...@lvh.io> writes:
>
>> I'm writing a book using org-mode. On export, org-mode turns double quotes
>> like "hello" into ``hello''. Some modern LaTeXes no longer support that
>> form, instead preferring semantic markup. (The reasoning being that the
>> markup implies a particular quote style, whereas quotation style is
>> language-dependent.)
>
> This is not true. Quotes depend on your LANGUAGE-cookie. See
> org-export-smart-quotes-alist.
>
>
>> As a result, I get
>>
>> The preferred way to do that these days is, in the preamble:
>>
>> \usepackage{csquotes}
>>
>> ... and then later:
>>
>> \enquote{something}
>
> But this would require us to load an extra package. Org is quite
> capable of handling this on the lisp side (and Org ≠ LaTeX). Clearly,
> we could have a org-export-user-smart-quote-alist taking priority over
> the predefined one.
>
>> I think it would make sense to support this for org, and perhaps eventually
>> make it default behavior. FWIW: I had no idea about this until it bit me
>> when my LaTeX document suddenly had bogus quotes in it.
>
> This has never happened to me, despite extensive usage of LaTeX for
> almost ten years.
>
>> If there is no interest to add this to org, how do I hack org so that this
>> is what it does?
>
> The cleanest way would be a filter, probably
> org-export-filter-quote-block-functions and filter-plain-text.
>
> The easiest way would be a macro or simply redefining
> org-export-smart-quotes-alist to suit your needs.
>
> Hope it helps.
>
IIRC, there was support for csquotes in the old exporter[fn:1] but I guess
it went away when the new exporter came along.
Nick
Footnotes:
[fn:1] e.g. see
http://thread.gmane.org/gmane.emacs.orgmode/21588
and the following commit which applies to the *OLD* latex exporter:
,
| commit 2b9afb9e63d2fd60a3bb09e33c9d4abb01586339
| Author: Bastien Guerry
| Date: Mon Jul 11 15:10:00 2011 +0200
|
| org-latex.el: New defcustom `org-export-latex-quotes' to control quotes.
|
| * org-latex.el (org-export-latex-quotes): New defcustom.
| (org-export-latex-quotation-marks): Use it.
|
| This allows users to define what quotes they want to use as a
| replacement of english double-quotes while exporting to LaTeX.
|
| In particular, if you use the csquote package, you can configure
| Org to output something like \endquote{some quoted text} instead
| of "some quoted text".
|
| Thanks to Frederik for bringing this issue up, and to Thomas S.
| Dye, Nick Dokos and Stefan Nobis for elaborating this solution.
`
although I cannot find the thread of that discussion on gmane.
Re: [O] orgtbl-to-sqlinsert
Aloha Thierry, Thierry Banel writes: > Hi again Thomas > > Probably the issue is not in orgtbl-to-sqlinsert, > because orgtbl-to-sqlinsert does not receive the header of the table. > Here is another fix which just recovers the lost header and passes it to > orgtbl-to-sqlinsert: > > ---8<--->8--- > *** Experiment with orgtbl-sqlinsert > > #+name: test-table > | one | two| > |-+| > | 1 | Buckle | > | 2 | Shoe | > | 3 | Open | > | 4 | Door | > > #+name: test-bed > #+header: :var x=test-table > #+begin_src emacs-lisp > (require 'orgtbl-sqlinsert) > (orgtbl-to-sqlinsert >(cons (cdadr (assoc :colname-names params)) (cons 'hline x)) > '(:sqlname "foo" :fmt (1 "%s"))) > #+end_src > #+RESULTS: test-bed > : BEGIN TRANSACTION; > : INSERT INTO foo( one, two ) VALUES ( 1 , 'Buckle' ); > : INSERT INTO foo( one, two ) VALUES ( 2 , 'Shoe' ); > : INSERT INTO foo( one, two ) VALUES ( 3 , 'Open' ); > : INSERT INTO foo( one, two ) VALUES ( 4 , 'Door' ); > : COMMIT; Yes, of course, babel takes off the table header and optionally reapplies it later. I should have thought of that! Thanks for looking into this and finding the solution. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Accessing #+EMAIL in LaTeX Export
On Feb 4, 2014, at 12:31, Nick Dokos wrote:
> Nick Dokos writes:
>
>> "R. Michael Weylandt" writes:
>>
>>> I want org-mode to export to the "amsart" class by default. In
>>> addition to the regular \title, \author, \date macros, amsart also
>>> allows for "email".
>>>
>>> (add-to-list 'org-latex-classes
>>> '("amsart"
>>> "\\documentclass{amsart}
>>> [DEFAULT-PACKAGES]
>>> [PACKAGES]
>>> [EXTRA]
>>> \\email{ {{{email}}} }"
>>> ("\\section{%s}" . "\\section{%s}")
>>> ("\\subsection{%s}" . "\\subsection{%s}")
>>> ("\\subsubsection{%s}" . "\\subsubsection{%s}")))
>>>
>>> Running this on a document like:
>>>
>>> #+TITLE: Test 1
>>> #+AUTHOR: Michael Weylandt
>>> #+EMAIL: michael.weyla...@gmail.com
>>> #+LATEX_CLASS: amsart
>>> * Header 1
>>> Hello World
>>>
>>> leaves me with "\email{email}" in the resulting LaTeX instead of
>>> "\email{michael.weyla...@mail.com}". Since this is used as part of
>>> \maketitle, doing something in the body (like your example) is too
>>> late.
>>>
>>> The #+EMAIL: value is handled by ox-latex.el, but it's only placed
>>> inside the \author{} macro instead of in a stand alone \email{}.
>>> That's the behavior I'm hoping to tweak.
>>>
>>> Is that clearer?
>>
>> Much - thanks. I haven't thought much about it but my knee-jerk reaction
>> is to use a marker (something like \email{@EMAIL@}) when defining the
>> class and use a filter to replace it at the end. But there are might be
>> more elegant solutions around.
>
> So here's a brute-force solution along the above lines:
>
> --8<---cut here---start->8---
> #+EMAIL: ndo...@gmail.com
> #+LATEX_CLASS: amsart
>
> * foo
> bar
>
> * code :noexport:
> This should probably go in some initialization file - for testing, I just
> executed
> the code blocks by hand:
>
> #+name: email-filter
> #+BEGIN_SRC elisp :results none
> (defun nd-email-filter (contents backend info)
>(let ((email (plist-get info :email)))
> (replace-regexp-in-string "@EMAIL@" email contents t)))
>
> (add-to-list 'org-export-filter-final-output-functions (function
> nd-email-filter))
> #+END_SRC
>
> #+name: amsart
> #+BEGIN_SRC elisp :results none
> (setq amsart-class
>'("amsart"
> "\\documentclass{amsart}
>[DEFAULT-PACKAGES]
>[PACKAGES]
>[EXTRA]
>\\email{@EMAIL@ }"
>("\\section{%s}" . "\\section{%s}")
> ("\\subsection{%s}" . "\\subsection{%s}")
> ("\\subsubsection{%s}" . "\\subsubsection{%s}")))
>
> (add-to-list 'org-latex-classes amsart-class)
> #+END_SRC
>
> This deletes the amsart from the org-latex-classes list:
>
> #+BEGIN_SRC elisp
> (setq org-latex-classes (cdr org-latex-classes))
> #+END_SRC
> --8<---cut here---end--->8---
>
> Nick
Hi Nick,
Thanks for the example; the filter seems to work well. Two possible issues:
1. I only want to use it for some latex classes
2. When using \email{} I want to get rid of the \thanks{} in \author{}.
I came up with the following:
<-->
(require 'cl-lib)
(defun any (x) (cl-reduce (lambda (x y) (if x x y)) x))
;; For certain latex classes, the org-mode default of
\author{NAME\thanks{EMAIL}}
;; isn't what the class wants
(defvar org-latex-classes-with-email '("amsart" "amsbook"))
;; After completing latex export, check if we are in one of the classes listed
in 'org-latex-classes-with-email;
;; if we are, we need to
;; 1) Remove the \thanks{} macro inside \author{}
;; 2) Add an \email{} macro
;; This can be done with a single regex replace using captures.
(defun org-latex-classes-with-email-filter (contents backend info)
(if (any (mapcar (lambda (x) (string-match x contents))
org-latex-classes-with-email))
(replace-regexp-in-string "author{\\(.*\\)thanks{\\(.*\\)}}"
"author{\\1}\nemail{\\2}" contents)))
;; Thanks to Nick Dokos for the filter setup help
--http://lists.gnu.org/archive/html/emacs-orgmode/2014-02/msg00130.html
(add-to-list 'org-export-filter-final-output-functions (function
org-latex-classes-with-email-filter))
<--->
It's regex based so there may be some false positives, but it seems to work
well enough for me.
Michael
Re: [O] how to customize date export
Nick Dokos writes:
> Eric S Fraga writes:
>
>> Mirko Vukovic writes:
>>
>> [...]
>>
>>> Hi Eric,
>>>
>>> Thanks for the note. As it stands now, I cannot
>>> customize these two variables to do what I want, as they accept the
>>> whole time-steamp as argument. I will enter the dates manually
>>> in the org file for now.
>>
>> I thought as much.
>>
>> Looking through the code, some of the functions for outputting the time
>> stamps make use of org-translate-time which does allow some
>> customisation of how the dates and times are written out, along the
>> lines of what you were looking at for DATE entries. Check the
>> documentation for that function. But it could be I've misunderstood the
>> code...
>
> Based on Eric's hint, I followed org-translate-time's docstring (and
> references therein) and I came up with this which seems to work (in the
> sense that the dates look like <2014/02/03 Monday> when exported,
> which agrees with the specified format):
>
> #+STARTUP: customtime
>
> * foo
> <2014-02-03 Mon>
>
> # Local Variables:
> # org-time-stamp-custom-formats: ("<%Y/%m/%d %A>" . "<%Y/%m/%d %A %H:%M>")
> # End:
>
> However, the angle brackets seem to be required.
You could use a filter to get rid of the angle brackets for instance
org-export-filter-timestamp-functions. There's also parse-time-string
together with the relevant DATE-formatting variables that can be used
to recast the appearance of time.
—Rasmus
--
Dung makes an excellent fertilizer
Re: [O] Quotes for LaTeX export
Hi Laurens,
Laurens Van Houtven <_...@lvh.io> writes:
> I'm writing a book using org-mode. On export, org-mode turns double quotes
> like "hello" into ``hello''. Some modern LaTeXes no longer support that
> form, instead preferring semantic markup. (The reasoning being that the
> markup implies a particular quote style, whereas quotation style is
> language-dependent.)
This is not true. Quotes depend on your LANGUAGE-cookie. See
org-export-smart-quotes-alist.
> As a result, I get
>
> The preferred way to do that these days is, in the preamble:
>
> \usepackage{csquotes}
>
> ... and then later:
>
> \enquote{something}
But this would require us to load an extra package. Org is quite
capable of handling this on the lisp side (and Org ≠ LaTeX). Clearly,
we could have a org-export-user-smart-quote-alist taking priority over
the predefined one.
> I think it would make sense to support this for org, and perhaps eventually
> make it default behavior. FWIW: I had no idea about this until it bit me
> when my LaTeX document suddenly had bogus quotes in it.
This has never happened to me, despite extensive usage of LaTeX for
almost ten years.
> If there is no interest to add this to org, how do I hack org so that this
> is what it does?
The cleanest way would be a filter, probably
org-export-filter-quote-block-functions and filter-plain-text.
The easiest way would be a macro or simply redefining
org-export-smart-quotes-alist to suit your needs.
Hope it helps.
—Rasmus
--
Er du tosset for noge' lårt!
Re: [O] plain lists folded by default
Hi Nick, I am not sure to understand why today's post has been subsumed to my previous one (entitled indeed "auto-fill-mode for text changes (plain-lists) indentation") on the archive page http://lists.gnu.org/archive/html/emacs-orgmode/2014-02/threads.html today post appears in a single thread "[O] plain lists folded by default". Maybe it is due to the fact I "replied to all" from one of my old messages, deleting the content and changing the email subject :'-( You mean I should have started from a blank email right? Well sorry for that, and thank you again for your answers. Regards, Rémy. Le 04/02/2014 21:41, Nick Dokos a écrit : So I was looking for this article using gmane's web interface and I couldn't see it. Turns out that you followed up on a different article (subject line was "auto-fill-mode for text changes (plain-lists) indentation"), so this thread got subsumed under that name. Please don't do that: if it is a different question, start a different thread. And conversely, although this is not the case here, if it is the same subject, stay on the same thread: don't start another. Violating either of these principles makes it harder to search the ML for answers. [And I should make it clear that these comments are not directed exclusively at Rémy: in particular, I have been guilty of the second transgression numerous times, so I am included in the target. AFAIK, I have not transgressed against the first principle - although it is arguable that this very note is indeed such a transgression :-)]
Re: [O] orgtbl-to-sqlinsert
Le 03/02/2014 00:47, Thomas S. Dye a écrit : > Aloha Thierry, > > Thierry Banel writes: > >> Hi Thomas. >> >> I don't understand this behavior yet. >> But here is a workaround: >> try the #+ORGTBL: SEND feature: >> 1- Add a #+ORGTBL: SEND line >> 2- Add a BEGIN RECEIVE ORGTBL block >> 3- Type C-c C-c with cursor on the first pipe of the table >> >> --8<--->8-- >> #+ORGTBL: SEND faraway orgtbl-to-sqlinsert :sqlname "foo" :fmt (1 "%s") >> | one | two| >> |-+| >> | 1 | Buckle | >> | 2 | Shoe | >> | 3 | Open | >> | 4 | Door | >> >> ;; BEGIN RECEIVE ORGTBL faraway >> BEGIN TRANSACTION; >> INSERT INTO foo( one, two ) VALUES ( 1 , 'Buckle' ); >> INSERT INTO foo( one, two ) VALUES ( 2 , 'Shoe' ); >> INSERT INTO foo( one, two ) VALUES ( 3 , 'Open' ); >> INSERT INTO foo( one, two ) VALUES ( 4 , 'Door' ); >> COMMIT; >> ;; END RECEIVE ORGTBL faraway > Yes, this works. > > Perhaps the table needs to be processed before it is passed to > orgtbl-to-sqlinsert? > > Note that =orgtbl-to-sqlinsert= takes advantage of org-mode's applying > the formatting to each cell /before/ checking for a line-formatting > function. The header line itself and sectioning line are suppressed > with the settings > > : :hlfmt (lambda (lst) (setq firstheader nil)) > : :hline nil > : :remove-nil-lines t > > I don't fully understand what this means, but it appears to address the > table header. > > All the best, > Tom > Hi again Thomas Probably the issue is not in orgtbl-to-sqlinsert, because orgtbl-to-sqlinsert does not receive the header of the table. Here is another fix which just recovers the lost header and passes it to orgtbl-to-sqlinsert: ---8<--->8--- *** Experiment with orgtbl-sqlinsert #+name: test-table | one | two| |-+| | 1 | Buckle | | 2 | Shoe | | 3 | Open | | 4 | Door | #+name: test-bed #+header: :var x=test-table #+begin_src emacs-lisp (require 'orgtbl-sqlinsert) (orgtbl-to-sqlinsert (cons (cdadr (assoc :colname-names params)) (cons 'hline x)) '(:sqlname "foo" :fmt (1 "%s"))) #+end_src #+RESULTS: test-bed : BEGIN TRANSACTION; : INSERT INTO foo( one, two ) VALUES ( 1 , 'Buckle' ); : INSERT INTO foo( one, two ) VALUES ( 2 , 'Shoe' ); : INSERT INTO foo( one, two ) VALUES ( 3 , 'Open' ); : INSERT INTO foo( one, two ) VALUES ( 4 , 'Door' ); : COMMIT; ---8<--->8---
[O] Quotes for LaTeX export
Hi,
I'm writing a book using org-mode. On export, org-mode turns double quotes
like "hello" into ``hello''. Some modern LaTeXes no longer support that
form, instead preferring semantic markup. (The reasoning being that the
markup implies a particular quote style, whereas quotation style is
language-dependent.)
As a result, I get
The preferred way to do that these days is, in the preamble:
\usepackage{csquotes}
... and then later:
\enquote{something}
I think it would make sense to support this for org, and perhaps eventually
make it default behavior. FWIW: I had no idea about this until it bit me
when my LaTeX document suddenly had bogus quotes in it.
If there is no interest to add this to org, how do I hack org so that this
is what it does?
hth
lvh
Re: [O] plain lists folded by default
So I was looking for this article using gmane's web interface and I couldn't see it. Turns out that you followed up on a different article (subject line was "auto-fill-mode for text changes (plain-lists) indentation"), so this thread got subsumed under that name. Please don't do that: if it is a different question, start a different thread. And conversely, although this is not the case here, if it is the same subject, stay on the same thread: don't start another. Violating either of these principles makes it harder to search the ML for answers. [And I should make it clear that these comments are not directed exclusively at Rémy: in particular, I have been guilty of the second transgression numerous times, so I am included in the target. AFAIK, I have not transgressed against the first principle - although it is arguable that this very note is indeed such a transgression :-)] -- Nick
Re: [O] how to customize date export
Nick Dokos writes:
[...]
> Based on Eric's hint, I followed org-translate-time's docstring (and
> references therein) and I came up with this which seems to work (in the
> sense that the dates look like <2014/02/03 Monday> when exported,
> which agrees with the specified format):
>
> #+STARTUP: customtime
>
> * foo
> <2014-02-03 Mon>
>
> # Local Variables:
> # org-time-stamp-custom-formats: ("<%Y/%m/%d %A>" . "<%Y/%m/%d %A %H:%M>")
> # End:
>
> However, the angle brackets seem to be required.
>
> Nick
I'm glad my hint was helpful. Interestingly, the angle brackets are not
required per se. However, there does have to be some character there,
in both places, and that character is replaced by an angle bracket on
export (and probably on display as well but I am using BIND instead of
local variable settings to set the custom format).
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.1, Org release_8.2.5h-585-g5f0ca0
Re: [O] any way how to look on what was done on particular day?
On Tue, Feb 4, 2014 at 9:33 AM, David Belohrad wrote: > > Hi all, > > the question is simple: I'd like to look into the past, into particular > day, and I'd like to see what TODOs have been modified at that day and > how they have been modified, e.g. showing that on this/that time the > TODO changed state from NEXT to WAITING. Most of those TODOs I have > already archived, hence an archive needs to be searched as well. My > current situation is, that if I mark the thing done, it disappears from > my agenda, which I consider OK for 'general' agenda. The type of agenda > I'm trying to construct is sort of archive search, which permits me to > return into a specific date and to be able to tell what I did the entire > day. > > is this possible? Based on your description, I believe so. See this list of agenda commands for reference: - http://orgmode.org/manual/Agenda-commands.html Could a combination of the following suit your needs? - `C-c a` to start agenda - `v A` to add archived trees and files to the search scope - Possibly `[` to add inactive timestamps to the search scope - `j` to enter a date you want to look at This seemed to work for me. I searched for 2013-01-07 and found a note to check and make sure a credit card payment had gone through with the process above: *** done check that cc payment went through CLOSED: [2013-01-07 Mon 17:52] DEADLINE: <2013-01-03 Thu> :PROPERTIES: :ARCHIVE_TIME: 2013-01-07 Mon 17:52 :END: It's in an archive sub-heading of my main todo/tracking file. If that works, I'm sure you could make a custom agenda view somehow incorporating some of the above (inactive time stamps tracked, all archived trees/files included, and perhaps even an auto-prompt for date you'd like to look at). I *didn't* have success getting an entry to populate where the timestamp was just inside a drawer, so I'm not sure how to do that. For example, the above has an inactive stamp for CLOSED, but I have another entry like this: ** todo note down month's accomplishments/contributions SCHEDULED: <2013-01-28 Mon +1m> :LOGBOOK: - State "cancelled" from "todo" [2013-01-07 Mon 10:00] \\ Dec included in yearly review - State "done" from "todo" [2012-11-06 Tue 12:54] - ...[snipped, lots more of these]... :END: :PROPERTIES: :LAST_REPEAT: [2013-01-07 Mon 10:00] :ID: 41f7debd-743b-4c1c-bc0f-69fc95ee7fab :END: So, that was a recurring todo with an inactive timestamp matching my search date, but it didn't get pulled. I'm thinking this is more what you're looking for, so someone else will have to chime in on whether or not agenda can check the logbook notes. Hope that helps a bit! John > > thanks > .d. > > > (now, I could use Python or something to parse all information and > generate it, but it would not be so attractive solution :) > >
[O] export tables to html and odt, table borders
Hi In orgmode 7.8 there was a variable (org-export-html-table-tag which allowed my to configure the table boundary to my liking for example: "") Now I installed the latest version available in elpa for GNU emacs24 and cannot find this variable. What is the corresponding new variable? Is there anything similar for the odt exporter? thanks Uwe Brauer
Re: [O] plain lists folded by default
Rémy Abergel writes: > Hi Org users, > > do you know how to make plain lists folded by default? > ... > Currently I need to manually fold the item one by one. Try this (but do read the doc for org-cycle-include-plain-lists for some caveats): --8<---cut here---start->8--- #+STARTUP: overview * Section 1 A paragraph here. + item 1 :: description some long text here + item 1.1 :: description comes here let us say that a long text comes here + item 1.2 :: description again let us say that a long text comes here. + item 2 :: some text Another paragraph here. * Section 2 when I unfold Section 1, I get what you can see above (plain lists are unfolded), but I would like to get (by default) something like * My section A paragraph here. + item 1 :: description... + item 2 :: some text Another paragraph here. * Another section Currently I need to manually fold the item one by one. # Local Variables: # org-cycle-include-plain-lists: integrate # End: --8<---cut here---end--->8--- > Eventually being able to do cycling (by pressing [TAB] several time on > section 1 in order to fold/unfold the items) would also be nice. > I think you get that for free. -- Nick
[O] plain lists folded by default
Hi Org users, do you know how to make plain lists folded by default? Let us consider the following example : * Section 1 A paragraph here. + item 1 :: description some long text here + item 1.1 :: description comes here let us say that a long text comes here + item 1.2 :: description again let us say that a long text comes here. + item 2 :: some text Another paragraph here. * Section 2 when I unfold Section 1, I get what you can see above (plain lists are unfolded), but I would like to get (by default) something like * My section A paragraph here. + item 1 :: description... + item 2 :: some text Another paragraph here. * Another section Currently I need to manually fold the item one by one. Eventually being able to do cycling (by pressing [TAB] several time on section 1 in order to fold/unfold the items) would also be nice. Thanks, Rémy.
Re: [O] any way how to look on what was done on particular day?
Have you tried "v l" or "v L" from within the agenda view on the particular day? It should show some of the activities you want. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.3.1, Org release_8.2.5h-585-g5f0ca0
Re: [O] mis-alignment in org-tables with Tibetan characters
Hi Steffan On Mon, Feb 3, 2014 at 6:33 AM, Steffan Iverson wrote: > Screenshot: http://oi59.tinypic.com/lz893.jpg Judging from e. g. this part | རྐུས་ | rkus | | གསོས་ | gsos | in your screenshot my speculation is that you get glyphs from not only your default monospace font but also from other (maybe variable width) font(s). Either because some glyphs are not available in your default monospace font or are not used due to an incomplete configuration with set-fontset-font. For a diagnosis in this direction I would check the alignment of "|" after some characters just repeated like here: xx| ་་| གག| རར| སས| ུུ| ོོ| ྐྐ| xx| ∞∞| Michael
Re: [O] any way how to look on what was done on particular day?
In Agenda view, v A for view archive files v L for view Log then you can view day, week, month or year (press v and it'll prompt you), and then f,b moves forward and backward in time. -k. On Tue, 4 Feb 2014, David Belohrad wrote: Hi all, the question is simple: I'd like to look into the past, into particular day, and I'd like to see what TODOs have been modified at that day and how they have been modified, e.g. showing that on this/that time the TODO changed state from NEXT to WAITING. Most of those TODOs I have already archived, hence an archive needs to be searched as well. My current situation is, that if I mark the thing done, it disappears from my agenda, which I consider OK for 'general' agenda. The type of agenda I'm trying to construct is sort of archive search, which permits me to return into a specific date and to be able to tell what I did the entire day. is this possible? thanks .d. (now, I could use Python or something to parse all information and generate it, but it would not be so attractive solution :)
Re: [O] [PATCH][ox-koma-letter] changed-in-buffer, subject, minor fixes
>>> Would you give the attached patches a spin? I think they work nicely;
>>> only the second patch is non-trivial. Basically, one can ignore
>>> subject and title differences as now by setting
>>> org-koma-letter-prefer-subject to t and not use the SUBJECT keyword.
>>>
>>> I have set the default of -prefer-subject to nil per the discussion
>>> with Alan and Michael Strey.
>>>
>>> It should apply against master.
>>
>> It looks good. Thank you.
>>
>> A few minor remarks below.
>>
>>> +(defcustom org-koma-letter-use-title t
>>> + "Non-nil means use a title in the letter if present.
>>> +
>>> +See also `org-koma-letter-prefer-subject' for the handling of
>>> +title versus subject."
>>> + :group 'org-export-koma-letter
>>> + :type 'boolean)
>>
>> You should also talk about the OPTIONS item, i.e., "title:nil", as in
>> other defcustoms.
>>
>>> +(defcustom org-koma-letter-prefer-subject nil
>>> + "Non-nil means title should be interpret as subject if subject is
>>> missing.
>>> +
>>> +This may be useful for older documents where the SUBJECT keyword
>>> +was not present."
>>> +:group 'org-export-koma-letter
>>> +:type 'boolean)
>>
>> Ditto.
>>
>>> - ;; Subject
>>> - (let ((with-subject (plist-get info :with-subject)))
>>> + ;; Subject and title
>>> + (let ((with-subject (plist-get info :with-subject))
>>> +(title-as-subject (plist-get info :with-title-as-subject))
>>> +(subject (org-string-nw-p (org-export-data (plist-get info :subject)
>>> info)))
>>> +(title (org-string-nw-p (org-export-data (plist-get info :title)
>>> info
>>
>> `title-as-subject', `subject' and `title' belong to the `let' below, not
>> this one.
>>
>>> (when with-subject
>>> (concat
>>> (unless (eq with-subject t)
>>> (format "\\KOMAoption{subject}{%s}\n"
>>> (if (symbolp with-subject) with-subject
>>> (mapconcat #'symbol-name with-subject ","
>>> - (let ((subject (org-export-data (plist-get info :title) info)))
>>> - (and (org-string-nw-p subject)
>>> - (format "\\setkomavar{subject}{%s}\n\n" subject))
>>> + (let ((subject (if title-as-subject (or subject title) subject))
>>> + (title (if title-as-subject (and subject title) title)))
>>> + (concat
>>> + (and (org-string-nw-p subject)
>>> + (format "\\setkomavar{subject}{%s}\n" subject))
>>> + (and (org-string-nw-p title)
>>> + (format "\\setkomavar{title}{%s}\n" title))
>>> + (when (or (org-string-nw-p title) (org-string-nw-p subject))
>>> "\n"))
>
> Rasmus: do you want to change these, or should I do it and apply the
> patch? (The former would be simpler, I have to say.)
Yes, but I didn't manged to do it in the weekend. I'll try to find
time during the week. My apology.
–Rasmus
--
When the facts change, I change my mind. What do you do, sir?
Re: [O] Accessing #+EMAIL in LaTeX Export
Nick Dokos writes:
> "R. Michael Weylandt" writes:
>
>> I want org-mode to export to the "amsart" class by default. In
>> addition to the regular \title, \author, \date macros, amsart also
>> allows for "email".
>>
>> (add-to-list 'org-latex-classes
>>'("amsart"
>> "\\documentclass{amsart}
>> [DEFAULT-PACKAGES]
>> [PACKAGES]
>> [EXTRA]
>> \\email{ {{{email}}} }"
>> ("\\section{%s}" . "\\section{%s}")
>>("\\subsection{%s}" . "\\subsection{%s}")
>>("\\subsubsection{%s}" . "\\subsubsection{%s}")))
>>
>> Running this on a document like:
>>
>> #+TITLE: Test 1
>> #+AUTHOR: Michael Weylandt
>> #+EMAIL: michael.weyla...@gmail.com
>> #+LATEX_CLASS: amsart
>> * Header 1
>> Hello World
>>
>> leaves me with "\email{email}" in the resulting LaTeX instead of
>> "\email{michael.weyla...@mail.com}". Since this is used as part of
>> \maketitle, doing something in the body (like your example) is too
>> late.
>>
>> The #+EMAIL: value is handled by ox-latex.el, but it's only placed
>> inside the \author{} macro instead of in a stand alone \email{}.
>> That's the behavior I'm hoping to tweak.
>>
>> Is that clearer?
>>
>
> Much - thanks. I haven't thought much about it but my knee-jerk reaction
> is to use a marker (something like \email{@EMAIL@}) when defining the
> class and use a filter to replace it at the end. But there are might be
> more elegant solutions around.
So here's a brute-force solution along the above lines:
--8<---cut here---start->8---
#+EMAIL: ndo...@gmail.com
#+LATEX_CLASS: amsart
* foo
bar
* code
:noexport:
This should probably go in some initialization file - for testing, I just
executed
the code blocks by hand:
#+name: email-filter
#+BEGIN_SRC elisp :results none
(defun nd-email-filter (contents backend info)
(let ((email (plist-get info :email)))
(replace-regexp-in-string "@EMAIL@" email contents t)))
(add-to-list 'org-export-filter-final-output-functions (function
nd-email-filter))
#+END_SRC
#+name: amsart
#+BEGIN_SRC elisp :results none
(setq amsart-class
'("amsart"
"\\documentclass{amsart}
[DEFAULT-PACKAGES]
[PACKAGES]
[EXTRA]
\\email{@EMAIL@ }"
("\\section{%s}" . "\\section{%s}")
("\\subsection{%s}" . "\\subsection{%s}")
("\\subsubsection{%s}" . "\\subsubsection{%s}")))
(add-to-list 'org-latex-classes amsart-class)
#+END_SRC
This deletes the amsart from the org-latex-classes list:
#+BEGIN_SRC elisp
(setq org-latex-classes (cdr org-latex-classes))
#+END_SRC
--8<---cut here---end--->8---
Nick
[O] unexpected link behavior in headlines - maybe bug
I discovered an unexpected behavior with two links in a headline. The simplest example to reproduce it is here: * file:dft-course-mode.el [[file:my-theme.el][another file]] If I click on the first link, the second file opens. It seems specific to that format, because these links work as expected: * file:dft-course-mode.el file:my-theme.el interestingly, with this: * [[file:dft-course-mode.el][a file]] file:my-theme.el clicking on the second link launches a web browser that cannot find http://www.my-theme.el/ Anyway, not sure if those are bugs, or not. definitely was unexpected for me! This came up from having a link to an assignment and a solution in a headline. John --- John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu
Re: [O] mis-alignment in org-tables with Tibetan characters
Eric Abrahamsen writes: > I've been using that patch or something like it for nearly a year now, > with no adverse effects. I'm on the road right now, give me a day and > I'll take a closer look at what I've got... Great -- thanks in advance! I'll then wait before releasing a new minor version and merging it into Emacs for Emacs 24.4. To other core maintainers: if you see important issues that needs to be fixed in maint, let me know. -- Bastien
[O] any way how to look on what was done on particular day?
Hi all, the question is simple: I'd like to look into the past, into particular day, and I'd like to see what TODOs have been modified at that day and how they have been modified, e.g. showing that on this/that time the TODO changed state from NEXT to WAITING. Most of those TODOs I have already archived, hence an archive needs to be searched as well. My current situation is, that if I mark the thing done, it disappears from my agenda, which I consider OK for 'general' agenda. The type of agenda I'm trying to construct is sort of archive search, which permits me to return into a specific date and to be able to tell what I did the entire day. is this possible? thanks .d. (now, I could use Python or something to parse all information and generate it, but it would not be so attractive solution :)
Re: [O] Accessing #+EMAIL in LaTeX Export
"R. Michael Weylandt" writes:
> On Tue, Feb 4, 2014 at 12:54 AM, Nick Dokos wrote:
>> "R. Michael Weylandt" writes:
>>
>>> HI,
>>>
>>> I'm writing a latex export class which has an \email macro.
>>>
>>> Is it possible to autofill this macro using the #+EMAIL: property?
>>> Looking at ox-latex.el, it seems that email is hardcoded to be placed
>>> in \thanks{} but there might be a hook I'm missing.
>>>
>>> I thought that using a {{{ email }}} macro might work, but I keep
>>> winding up with
>>> \email{ {{{email}}} } in the produced LaTeX.
>>>
>>
>> Not sure what your \email macro is supposed to look like or what
>> it is supposed to do, but the {{{email}}} works for me, e.g. the
>> following produces my italicized email in the output:
>>
>> --8<---cut here---start->8---
>> #+EMAIL: ndo...@gmail.com
>>
>> * foo
>>
>> This is my email: \emph{ {{{email}}} }.
>> --8<---cut here---end--->8---
>>
>
> Hi Nick,
>
> Thanks for taking a look at this. Let me say a bit more about what I'm
> trying to do:
>
> I want org-mode to export to the "amsart" class by default. In
> addition to the regular \title, \author, \date macros, amsart also
> allows for "email".
>
> (add-to-list 'org-latex-classes
>'("amsart"
> "\\documentclass{amsart}
> [DEFAULT-PACKAGES]
> [PACKAGES]
> [EXTRA]
> \\email{ {{{email}}} }"
> ("\\section{%s}" . "\\section{%s}")
>("\\subsection{%s}" . "\\subsection{%s}")
>("\\subsubsection{%s}" . "\\subsubsection{%s}")))
>
> Running this on a document like:
>
> #+TITLE: Test 1
> #+AUTHOR: Michael Weylandt
> #+EMAIL: michael.weyla...@gmail.com
> #+LATEX_CLASS: amsart
> * Header 1
> Hello World
>
> leaves me with "\email{email}" in the resulting LaTeX instead of
> "\email{michael.weyla...@mail.com}". Since this is used as part of
> \maketitle, doing something in the body (like your example) is too
> late.
>
> The #+EMAIL: value is handled by ox-latex.el, but it's only placed
> inside the \author{} macro instead of in a stand alone \email{}.
> That's the behavior I'm hoping to tweak.
>
> Is that clearer?
>
Much - thanks. I haven't thought much about it but my knee-jerk reaction
is to use a marker (something like \email{@EMAIL@}) when defining the
class and use a filter to replace it at the end. But there are might be
more elegant solutions around.
--
Nick
Re: [O] mis-alignment in org-tables with Tibetan characters
Bastien writes: > Hi Steffan, > > thanks for reporting this. > > Steffan Iverson writes: > >> Any way to solve this problem? > > This is a recurring problem, and Eric is the one who tried > to solve it. > > Eric, I don't remember why we didn't follow-up on your patch > here: > > http://lists.gnu.org/archive/html/emacs-orgmode/2013-02/msg00664.html > > Would that help in this situation? I've been using that patch or something like it for nearly a year now, with no adverse effects. I'm on the road right now, give me a day and I'll take a closer look at what I've got... E
Re: [O] Accessing #+EMAIL in LaTeX Export
On Tue, Feb 4, 2014 at 12:54 AM, Nick Dokos wrote:
> "R. Michael Weylandt" writes:
>
>> HI,
>>
>> I'm writing a latex export class which has an \email macro.
>>
>> Is it possible to autofill this macro using the #+EMAIL: property?
>> Looking at ox-latex.el, it seems that email is hardcoded to be placed
>> in \thanks{} but there might be a hook I'm missing.
>>
>> I thought that using a {{{ email }}} macro might work, but I keep
>> winding up with
>> \email{ {{{email}}} } in the produced LaTeX.
>>
>
> Not sure what your \email macro is supposed to look like or what
> it is supposed to do, but the {{{email}}} works for me, e.g. the
> following produces my italicized email in the output:
>
> --8<---cut here---start->8---
> #+EMAIL: ndo...@gmail.com
>
> * foo
>
> This is my email: \emph{ {{{email}}} }.
> --8<---cut here---end--->8---
>
Hi Nick,
Thanks for taking a look at this. Let me say a bit more about what I'm
trying to do:
I want org-mode to export to the "amsart" class by default. In
addition to the regular \title, \author, \date macros, amsart also
allows for "email".
--8<---cut here-start--->8---
(add-to-list 'org-latex-classes
'("amsart"
"\\documentclass{amsart}
[DEFAULT-PACKAGES]
[PACKAGES]
[EXTRA]
\\email{ {{{email}}} }"
("\\section{%s}" . "\\section{%s}")
("\\subsection{%s}" . "\\subsection{%s}")
("\\subsubsection{%s}" . "\\subsubsection{%s}")))
--8<---cut here---end--->8---
Running this on a document like:
--8<---cut here-start--->8---
#+TITLE: Test 1
#+AUTHOR: Michael Weylandt
#+EMAIL: michael.weyla...@gmail.com
#+LATEX_CLASS: amsart
* Header 1
Hello World
--8<---cut here---end--->8---
leaves me with "\email{email}" in the resulting LaTeX instead of
"\email{michael.weyla...@mail.com}". Since this is used as part of
\maketitle, doing something in the body (like your example) is too
late.
The #+EMAIL: value is handled by ox-latex.el, but it's only placed
inside the \author{} macro instead of in a stand alone \email{}.
That's the behavior I'm hoping to tweak.
Is that clearer?
Thanks again,
Michael
Re: [O] [PATCH][ox-koma-letter] changed-in-buffer, subject, minor fixes
Hello,
Sorry for not replying earlier, I've been swamped by traveling and work.
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Would you give the attached patches a spin? I think they work nicely;
>> only the second patch is non-trivial. Basically, one can ignore
>> subject and title differences as now by setting
>> org-koma-letter-prefer-subject to t and not use the SUBJECT keyword.
>>
>> I have set the default of -prefer-subject to nil per the discussion
>> with Alan and Michael Strey.
>>
>> It should apply against master.
>
> It looks good. Thank you.
>
> A few minor remarks below.
>
>> +(defcustom org-koma-letter-use-title t
>> + "Non-nil means use a title in the letter if present.
>> +
>> +See also `org-koma-letter-prefer-subject' for the handling of
>> +title versus subject."
>> + :group 'org-export-koma-letter
>> + :type 'boolean)
>
> You should also talk about the OPTIONS item, i.e., "title:nil", as in
> other defcustoms.
>
>> +(defcustom org-koma-letter-prefer-subject nil
>> + "Non-nil means title should be interpret as subject if subject is missing.
>> +
>> +This may be useful for older documents where the SUBJECT keyword
>> +was not present."
>> +:group 'org-export-koma-letter
>> +:type 'boolean)
>
> Ditto.
>
>> - ;; Subject
>> - (let ((with-subject (plist-get info :with-subject)))
>> + ;; Subject and title
>> + (let ((with-subject (plist-get info :with-subject))
>> + (title-as-subject (plist-get info :with-title-as-subject))
>> + (subject (org-string-nw-p (org-export-data (plist-get info :subject)
>> info)))
>> + (title (org-string-nw-p (org-export-data (plist-get info :title)
>> info
>
> `title-as-subject', `subject' and `title' belong to the `let' below, not
> this one.
>
>> (when with-subject
>> (concat
>> (unless (eq with-subject t)
>>(format "\\KOMAoption{subject}{%s}\n"
>>(if (symbolp with-subject) with-subject
>> (mapconcat #'symbol-name with-subject ","
>> -(let ((subject (org-export-data (plist-get info :title) info)))
>> - (and (org-string-nw-p subject)
>> - (format "\\setkomavar{subject}{%s}\n\n" subject))
>> +(let ((subject (if title-as-subject (or subject title) subject))
>> + (title (if title-as-subject (and subject title) title)))
>> + (concat
>> + (and (org-string-nw-p subject)
>> +(format "\\setkomavar{subject}{%s}\n" subject))
>> + (and (org-string-nw-p title)
>> +(format "\\setkomavar{title}{%s}\n" title))
>> + (when (or (org-string-nw-p title) (org-string-nw-p subject))
>> "\n"))
Rasmus: do you want to change these, or should I do it and apply the
patch? (The former would be simpler, I have to say.)
Thanks,
Alan
Re: [O] Bug: dragging a line in agenda moves following hidden lines
Hi Thomas, Thomas Morgan writes: > I think it would be more useful and intuitive for hidden lines not to be > affected by dragging. I agree to some extent, but this is difficult to achieve. The agenda is read-only. Dragging lines in agenda, although permitted, is convenient for temporary views only. Any re-display is likely to remove the re-ordering: `g' will do; maybe re-displaying hidden lines (through `/ /') should do so, too, if the current behavior is too confusing. What do you think? -- Bastien
Re: [O] patch for ob-sql and postgresql for supporting :colnames
Bastien, OK, I understand. regards, Joost > "bzg" == bzg writes: > From: b...@gnu.org > To: jo...@snow.nl > Cc: schulte.e...@gmail.com, emacs-orgmode@gnu.org > Subject: Re: patch for ob-sql and postgresql for supporting :colnames > Date: 03-Feb-14 15:54 > Hi Joost, > Joost Helberg writes: >> it's not in org-plus-contrib-20140203. Was it lost somehow (also my fix >> for stopping on error is not in)? > The change you suggested is in the master branch, not in the maint > branch, which is for bugfixes only. IMO the change is more a feature > enhancement than a bugfix, hence the fact it's in master. Also, we > are more strict with "bugfixes" right now because all our fixes > will go into Emacs 24.4, which is in feature freeze right now. > -- > Bastien -- Snow B.V.
Re: [O] Need extra text in ODT export of headers
Hi, Jambunathan, I was going to tell Dan the same thing, but for some reason, the below doesn't work for me with outline numbering. Can you confirm that it works for you? When I try, the paragraph styles from the template *do* get applied (tested by coloring some headings), but the custom outline numbering does not. To see if it ought to, I also tried to "load styles" from the OTT into an ODT document, but again, custom outline numbering did not follow along, so I'm not sure if it should be expected to work with Org ODT export either. Yours, Christian Jambunathan K writes: > The following message is a courtesy copy of an article > that has been posted to gmane.emacs.orgmode as well. > > Dan Griswold writes: > >> The only downside right now seems to be that I have to do the outline >> numbering for each file in the manuscript. But there are only 9 of >> them. > > You just need to create a opendocument template file and have all the > org file use it. > > See > >(info "(org) Applying custom styles") > > 1. Export ONE document. > 2. Fix outline numbering > 3. Save the file as say custom-style.ott (Note: It is OTT and not ODT) > 4. Add a directive to ALL THE OTHER org file as below. > >M-x org-export-insert-default-template odt > >and modify the ODT_STYLES_FILE directive as below. > > #+ODT_STYLES_FILE: "~/a/b/custom-style.ott" > > 5. Now if I export the org files with (4), you will get the outline >numbering that you desire.
Re: [O] [PATCH] Change to org-src-preserve-indentation documentation
John Hendy wrote:
>> It should be Org, not org. And two spaces are required.
>
> Got it. I thought the same thing, but swear I just ran into that
> ("org" vs. "Org") recently and followed the convention. Grepping files
> in org.git and worg.git revealed only a handful of instances where
> lower case "org" is used, so I must have been imagining or recalling
> something from the mailing list vs. official docs.
If we follow the convention of Emacs manuals [1], we should write "Org
mode" (first letter in upper case, no dash between Org and mode).
Best regards,
Seb
[1] "Dired buffer", "Shell mode", etc.
--
Sebastien Vauban
