Re: [O] Get a list of tasks completed today
Sebastien Vauban sva-n...@mygooglest.com writes: Sebastien Vauban wrote: To get a list of tasks which I've completed today, I guess we must have: (setq org-log-done t) ; default I mean: I guess it's more dangerous to try and play with the state changes information stored in the LOGBOOK drawer as people can easily modify them (see `org-log-note-headings'). Under the above assumption, the request becomes: (add-to-list 'org-agenda-custom-commands '(. Completed today ((todo DONE|CANX ((org-agenda-skip-function '(org-agenda-skip-entry-if 'notregexp CLOSED: \\[2014-02-13)) (org-agenda-sorting-strategy '(priority-down)) t) ... for today. But how can I include today's date in a programmatic way (so that it continues to work tomorrow ;-))? That one is solved by doing this: #+begin_src emacs-lisp (add-to-list 'org-agenda-custom-commands '(. Completed today ((todo ((org-agenda-skip-function '(org-agenda-skip-entry-if 'notregexp (format-time-string CLOSED: \\[%Y-%m-%d) (org-agenda-sorting-strategy '(priority-down)) t) #+end_src Best regards, Seb I don't really understand the lisp, but I'm guessing that %Y, %m, and %d hold the current year, month, and day, respectively, so I can see how the regex could be modified to deal with last year and last month. However, more useful to me would be last week, so what approach should I take for that? Cheers, Loris -- This signature is currently under construction.
Re: [O] simple way to call `C-c a v' or a way to bind it to a key?
Marc Ihm m...@ihm.name writes: (global-set-key (kbd f12) (lambda () (interactive) (execute-kbd-macro (kbd C-c a v (global-set-key (kbd f12) (kbd C-c a v)) might be a little easier to read and type. Explanation is : global-set-key can take any command as argument, and the definition of what a command is includes keyboard macros. That is vaguely explained at (info (elisp) What Is a Function) -- 2nd paragraph after the term command. P.s.: In my opinion, the name execute-kbd-macro of this builtin function is somewhat misleading; replay-keys describes this usage closer ... I think I wouldn't look for replay-keys if I did not know about the function. My own problem is that I usually look for call-kbd-macro, which doesn't exist, instead of execute- I guess everyone can't be pleased ! -- Nico.
[O] orc-contacts contacting ww.gravatar.com! -- How to switch off?
Hi, I'm exploring the org-contacts. When I do M-x org-contacts, Emacs tries to contact www.gravatar.com:80 How can I switch that off? Besides that, what I really miss is a comprehensive manual on org-contact. OK, I can search for a name as described above, I can add a new contact with M-x org-capture, but what else? Thank you, Regards, Alexander
Re: [O] orc-contacts contacting ww.gravatar.com! -- How to switch off?
AW alexander.will...@t-online.de writes: Hi, I'm exploring the org-contacts. When I do M-x org-contacts, Emacs tries to contact www.gravatar.com:80 How can I switch that off? You can set `org-contacts-icon-use-gravatar' to nil. Besides that, what I really miss is a comprehensive manual on org-contact. OK, I can search for a name as described above, I can add a new contact with M-x org-capture, but what else? Thank you, Regards, Alexander -- Daimrod/Greg signature.asc Description: PGP signature
Re: [O] orc-contacts contacting ww.gravatar.com! -- How to switch off?
Am Montag, 17. Februar 2014, 13:02:46 schrieb Daimrod: AW alexander.will...@t-online.de writes: Hi, I'm exploring the org-contacts. When I do M-x org-contacts, Emacs tries to contact www.gravatar.com:80 How can I switch that off? You can set `org-contacts-icon-use-gravatar' to nil. Thanx. Worx! Besides that, what I really miss is a comprehensive manual on org-contact. OK, I can search for a name as described above, I can add a new contact with M-x org-capture, but what else? Thank you, Regards, Alexander signature.asc Description: This is a digitally signed message part.
[O] Screencast of lispy.el with org-mode code base
Hi all, I'm developing an Emacs minor mode called lispy (available at https://github.com/abo-abo/lispy and as lispy in MELPA). It combines vi-style Paredit and IDE-like features for Elisp, Clojure, Scheme and Common Lisp (leveraging CEDET, CIDER, Geiser, and SLIME respectively). To show-off the package a bit, here's a screencast where I navigate org-mode code: https://vimeo.com/86894158 . Some cool features (I'll list a shortcut and what it does, starting position should be anywhere in org source tree with point at ( or behind ) or at ^;): 1. With g I know that there are currently 7276 tags in org-mode's code base. 2. With G I know that there are 1761 tags in org.el. 3. With g obs I know that there are 24 tags declared obsolete in org-mode's code base. 4. With g cloj I know that there are 18 tags related to Clojure, all of them in ob-clojure.el. 5. With g heading ext here are the candidates that match: declare-function outline-next-heading org-list.el declare-function outline-next-heading org-footnote.el org-extract-archive-heading org-archive.el org-mouse-next-heading org-mouse.el 6. With g defk I know that org-defkey is called 306 times. 7. With g shifttab here's the info I get (last one is the definition): org-defkey org-mode-map [(shift tab)]'org-shifttaborg.el define-key org-mode-map [backtab] 'org-shifttab org.el org-shifttab org.el 8. And of course RET will jump to any candidate selected, e.g. g python exe RET will jump to file ob-python.el to the definition of `org-babel-execute:python'. I'm using CEDET to parse the files, so the first time you call `lispy-goto` there will be a few second parse. The parse happens only once, it saves tags to the database and no parsing is done further unless some files have changed. I also demonstrate near the end of the video how to customize the info you get for the top-level tags. So initially `eval-after-load` tags were plain and didn't show what they were doing. But then I added `(eval-after-load . 1)` to `lispy-tag-arity` and after a call to `lispy-build-semanticdb` the `eval-after-load` tags include one more sexp, which is the file argument of the form. I hope you like the package and feedback is welcome. regards, Oleh
Re: [O] Get a list of tasks completed today
Loris Bennett loris.benn...@fu-berlin.de writes: #+begin_src emacs-lisp (add-to-list 'org-agenda-custom-commands '(. Completed today ((todo ((org-agenda-skip-function '(org-agenda-skip-entry-if 'notregexp (format-time-string CLOSED: \\[%Y-%m-%d) (org-agenda-sorting-strategy '(priority-down)) t) #+end_src However, more useful to me would be last week, so what approach should I take for that? I get pretty decent mileage out of this command (note that it's a tags search, not a todo keyword search.) (add-to-list 'org-agenda-custom-commands '(. Closed this week. tags CLOSED\-1w\ ((org-agenda-sorting-strategy '(priority-down) Though now I've got a related question. One thing I'd like to do is run a function over every item that was closed this past week. For sake of example, let's say I've added a property :mood: 5 to several closed items and I'd like to delete it (but only from the closed items; I'm not necessarily deleting the property globally.) To do this I tried pulling all the closed items, visiting them in turn, and calling (org-delete-property mood). But I got stuck pulling all the closed items, because `org-tags-view' and friends all build an agenda as a side effect. Is my best bet simply re-implementing the parts of `org-tags-view' that I need? Or is there a more common way to use the org machinery to work with items in lisp code? Thanks! -- Trevor Murphy GnuPG Key: 0x83881C0A
Re: [O] Get a list of tasks completed today
Loris Bennett wrote: Sebastien Vauban sva-n...@mygooglest.com writes: Sebastien Vauban wrote: To get a list of tasks which I've completed today, I guess we must have: (setq org-log-done t) ; default I mean: I guess it's more dangerous to try and play with the state changes information stored in the LOGBOOK drawer as people can easily modify them (see `org-log-note-headings'). Under the above assumption, the request becomes: (add-to-list 'org-agenda-custom-commands '(. Completed today ((todo DONE|CANX ((org-agenda-skip-function '(org-agenda-skip-entry-if 'notregexp CLOSED: \\[2014-02-13)) (org-agenda-sorting-strategy '(priority-down)) t) ... for today. But how can I include today's date in a programmatic way (so that it continues to work tomorrow ;-))? That one is solved by doing this: #+begin_src emacs-lisp (add-to-list 'org-agenda-custom-commands '(. Completed today ((todo ((org-agenda-skip-function '(org-agenda-skip-entry-if 'notregexp (format-time-string CLOSED: \\[%Y-%m-%d) (org-agenda-sorting-strategy '(priority-down)) t) #+end_src Note that the above DOES NOT WORK if you don't specify TODO states such as: --8---cut here---start-8--- ((todo DONE|CANX --8---cut here---end---8--- I have the impression this is a bug. Moreover, you should even add active states such as TODO for repeatable actions which do go back to the TODO state; hence, it becomes: --8---cut here---start-8--- ((todo TODO|DONE|CANX --8---cut here---end---8--- I don't really understand the lisp, but I'm guessing that %Y, %m, and %d hold the current year, month, and day, respectively, so I can see how the regex could be modified to deal with last year and last month. However, more useful to me would be last week, so what approach should I take for that? I guess you should begin playing with things such as: --8---cut here---start-8--- (time-add (current-time) (seconds-to-time -86400)) --8---cut here---end---8--- to point to yesterday, etc. But I'm not sure this is the right approach... Best regards, Seb -- Sebastien Vauban
Re: [O] Get a list of tasks completed today
Boo, reflowed text or some nonsense. Let's see if this works better: (add-to-list 'org-agenda-custom-commands '(. Closed this week. tags CLOSED\-1w\ ((org-agenda-sorting-strategy '(priority-down) -- Trevor Murphy GnuPG Key: 0x83881C0A
Re: [O] Get a list of tasks completed today
Trevor Murphy trevor.m.mur...@gmail.com writes: ... One thing I'd like to do is run a function over every item that was closed this past week. For sake of example, let's say I've added a property :mood: 5 to several closed items and I'd like to delete it (but only from the closed items; I'm not necessarily deleting the property globally.) To do this I tried pulling all the closed items, visiting them in turn, and calling (org-delete-property mood). But I got stuck pulling all the closed items, because `org-tags-view' and friends all build an agenda as a side effect. Is my best bet simply re-implementing the parts of `org-tags-view' that I need? Or is there a more common way to use the org machinery to work with items in lisp code? You should be able to do this with the mapping and property APIs: (info (org) Using the mapping API) (info (org) Using the property API) -- Nick
[O] Suggestion/bug: Parse inlinetask END with level sensitivity
Hi. I recently started using inlinetasks to be able to tag and comment long texts (a kind of simple qualitative data analysis). I thought that I would be able to use both tasks with and without an END line interchangeably: *** inlinetask without end some text *** inlinetask with end text inside inlinetask *** END The problem (not so surprising really) is that the parser finds the END of the second inlinetask and makes them nested in an export. I thought this could be solved with using different numbers of stars for tasks with and without END, judging from these lines in org-inlinetask.el: ;; If you need to have a time planning line (DEADLINE etc), drawers, ;; for example LOGBOOK of PROPERTIES, or even normal text as part of ;; the inline task, you must add an END headline with the same ;; number of stars. But the search for END in the parser is actually star-insensitive so this didn't solve my problem either. I suggest requiring the END-line to contain as many stars as it's beginning line by doing something like this (there is certainly a cleaner way doing it) to org-element-inlinetask-parser: @@ -972,7 +972,9 @@ plist (task-end (save-excursion (end-of-line) - (and (re-search-forward ^\\*+ END limit t) + (and (re-search-forward + (concat ^ (mapconcat 'identity (make-list (nth 1 components) \\*) ) END) + limit t) (match-beginning 0 (contents-begin (progn (forward-line) (and task-end ( (point) task-end) (point But perhaps this is too unstable? (Although it could be expected from the comments above). Cheers, Anders Johansson
[O] ox-bibtex: How to use Bib file in a different directory?
I've just discovered ox-bibtex, which is great for generating bibliographies in both PDF and HTML documents. I have it working fine when the Bib file is in the current directory, but how do I get it to use a Bib file in a different directory (for HTML output - PDF is fine)? Thanks a lot. Richard Stanton
Re: [O] [RFC] Move ox-koma-letter into core?
Hi everybody, sorry for replying so late to this discussion. I stopped following the list a while ago. Rasmus was so kind and tracked me down. Am 18.01.14 19:10, schrieb Carsten Dominik: On 18 Jan 2014, at 00:08, Nicolas Goaziou n.goaz...@gmail.com wrote: There is one thing to consider, though: Viktor Rosenfeld (Cc'ed) contributed a significant number of lines of code to the file but hasn't signed FSF papers, AFAIK. Viktor, what is your positions on this? I had actually started the copyright assignment process in September but did not follow through with it because I did not fully understand the document and did not like some of the language. However, I'm willing to give it another shot and have sent my questions to the FSF. FWIW, I think that the copyright assignment process creates a huge barrier of entry to contribute to Orgmode and that it's unfortunate that one has to jump through hoops like this to contribute actual code (whereas other contributions, e.g., documentation, have no such obligation attached). Also, my view of the document, as I understand it, is that it's very one-sided and unfair to the developer, specifically the future works and indemnification clauses. For the record, I will not sign a document containing the indemnification clause as it currently stands. Cheers, Viktor
[O] [BUG] Problem with org-mobile.el
In the past (http://article.gmane.org/gmane.emacs.orgmode/79803/) I had a problem with pushing using org-mobile, and it was solved as detailed in (http://thread.gmane.org/gmane.emacs.orgmode/79856/focus=79876). Indeed now the patch can be found in ELPA, but it still introduces the same problem as reported above. My setting is: Emacs : GNU Emacs 24.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2013-03-13 on bob.porkrind.org Package: Org-mode version 8.2.4 (8.2.4-3-g7fe99a-elpa @ /Users/drorata/.emacs.d/elpa/org-plus-contrib-20140217/) Line #463 in org-mobile.el is: ((eq (car x) :grouptags) nil) which should be the fix. I could fix the issue by moving this line after the following one, have: ((eq (car x) :newline) nil) ((eq (car x) :grouptags) nil) for lines #463-464 instead of ((eq (car x) :grouptags) nil) ((eq (car x) :newline) nil) which is the current state. Can someone verify this? Best, Dror
[O] org-export-latex-hyperref-options-format
Hello. I recently upgraded to org 8 from the builtin org (7.x) of Emacs
24.3 and lost the ability to customize the \hypersetup block via the custom
var org-export-latex-hyperref-options-format. Platform is OSX, Emacs
installed via homebrew and org-mode updated via package.el.
Org 7.x defines the var in org-latex.el. Because it's a builtin, the custom
var still displays in the 'org-latex-export group when configuring options.
However, the new export logic from ox-latex.el does not define this custom
var, nor does it respect the value if it is set. This is doubly confusing
because it appears the var is available, but it actually unused.
I found this thread from September which describes the same issue, but the
patch did not address adding the custom var back and seems to have died.
http://lists.gnu.org/archive/html/emacs-orgmode/2013-09/msg01364.html
I've created a patch via git format-patch which adds the custom var to
ox-latex.el and makes use of it. Thanks for considering it.
rom 0df51396b04bd785948032055e48b40787c15d98 Mon Sep 17 00:00:00 2001
From: Joe Hirn joseph.h...@gmail.com
Date: Mon, 17 Feb 2014 14:39:35 -0600
Subject: [PATCH] add org-export-latex-hyperref-options-format custom var
back
to latex exporter
---
ox-latex.el | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/ox-latex.el b/ox-latex.el
index 19f055e..9724def 100644
--- a/ox-latex.el
+++ b/ox-latex.el
@@ -186,6 +186,17 @@
:group 'org-export-latex
:type '(string :tag LaTeX class))
+(defcustom org-export-latex-hyperref-options-format
+ \\hypersetup{\n pdfkeywords={%s},\n pdfsubject={%s},\n
pdfcreator={Emacs Org-mode version %s}}\n
+ A format string for hyperref options.
+When non-nil, it must contain three %s format specifications
+which will respectively be replaced by the document's keywords,
+its description and the Org's version number, as a string. Set
+this option to the empty string if you don't want to include
+hyperref options altogether.
+ :type 'string
+ :group 'org-export-latex)
+
(defcustom org-latex-classes
'((article
\\documentclass[11pt]{article}
@@ -1119,7 +1130,7 @@ holding export options.
(format \\title{%s}\n title)
;; Hyperref options.
(when (plist-get info :latex-hyperref-p)
- (format \\hypersetup{\n pdfkeywords={%s},\n pdfsubject={%s},\n
pdfcreator={%s}}\n
+ (format org-export-latex-hyperref-options-format
(or (plist-get info :keywords) )
(or (plist-get info :description) )
(if (not (plist-get info :with-creator))
--
1.8.5.4
Re: [O] [RFC] Move ox-koma-letter into core?
Aloha Viktor, Viktor Rosenfeld listuse...@gmail.com writes: Also, my view of the document, as I understand it, is that it's very one-sided and unfair to the developer, specifically the future works and indemnification clauses. For the record, I will not sign a document containing the indemnification clause as it currently stands. FWIW, as a small businessman, the indemnification clause looks fairly standard to me. The contracts for archaeological services that we routinely sign typically have a clause like this, usually coupled with a request for a certificate of insurance that specifies the levels of liability insurance that the business carries. As I read the clause, FSF is in the position of accepting 1) a code contribution from a developer, and 2) the developer's assurance that the contributed code can't be claimed as property by a third party. It seems prudent that, in the event of a successful property claim by a third party to a piece of code contributed by a developer, the developer who gave the false assurance should be held responsible. Otherwise, FSF might be brought down by copyleft opponents who knowingly contribute code to which others have property rights in order to create a basis for lawsuits. From my point of view, the problem is the extent to which property rights structure relationships in our society--an extent unprecedented in history. I applaud FSF for its efforts to create computer software to which we all have a claim not to be excluded from its use or enjoyment. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Suggestion/bug: Parse inlinetask END with level sensitivity
Hello, Anders Johansson mejlaande...@gmail.com writes: I thought that I would be able to use both tasks with and without an END line interchangeably: *** inlinetask without end some text *** inlinetask with end text inside inlinetask *** END The problem (not so surprising really) is that the parser finds the END of the second inlinetask and makes them nested in an export. This should be fixed in maint. Thank you for reporting it. For the record, inlinetasks cannot be nested, and the number of stars is not meaningful, as long as it is greater than `org-inlinetask-min-level'. Regards, -- Nicolas Goaziou
Re: [O] org-export-latex-hyperref-options-format
Hello, Joe Hirn joseph.h...@gmail.com writes: Hello. I recently upgraded to org 8 from the builtin org (7.x) of Emacs 24.3 and lost the ability to customize the \hypersetup block via the custom var org-export-latex-hyperref-options-format. Platform is OSX, Emacs installed via homebrew and org-mode updated via package.el. Org 7.x defines the var in org-latex.el. Because it's a builtin, the custom var still displays in the 'org-latex-export group when configuring options. However, the new export logic from ox-latex.el does not define this custom var, nor does it respect the value if it is set. This is doubly confusing because it appears the var is available, but it actually unused. The problem will go with the next Emacs release. I found this thread from September which describes the same issue, but the patch did not address adding the custom var back and seems to have died. http://lists.gnu.org/archive/html/emacs-orgmode/2013-09/msg01364.html Actually, there is a way to ignore hypersetup block. See `org-latex-with-hyperref'. If you really want a custom command, I think it is better to first disable it with the variable aforementioned, then include your own with #+latex_header or in a custom latex class (see `org-latex-classes'). You can also use a filter to change it on the fly, but that would be less straightforward. Regards, -- Nicolas Goaziou
Re: [O] [RFC] Move ox-koma-letter into core?
Viktor Rosenfeld listuse...@gmail.com writes: sorry for replying so late to this discussion. I stopped following the list a while ago. Rasmus was so kind and tracked me down. Am 18.01.14 19:10, schrieb Carsten Dominik: On 18 Jan 2014, at 00:08, Nicolas Goaziou n.goaz...@gmail.com wrote: There is one thing to consider, though: Viktor Rosenfeld (Cc'ed) contributed a significant number of lines of code to the file but hasn't signed FSF papers, AFAIK. Viktor, what is your positions on this? I had actually started the copyright assignment process in September but did not follow through with it because I did not fully understand the document and did not like some of the language. However, I'm willing to give it another shot and have sent my questions to the FSF. Thanks Viktor; let us know how it goes. Bastien and Carsten(?), before Viktor goes through too many hoops, perhaps you could indicate where you minds settled on the—potential—inclusion of ox-koma-letter.el. Cheers, Rasmus -- C is for Cookie
Re: [O] ox-bibtex: How to use Bib file in a different directory?
Might the symbolic link would do the trick?
Re: [O] org-export-latex-hyperref-options-format
Hm. That's disappointing. I really prefer the original behavior. I don't want to copy #+latex_header to get this default behavior into each of my org-mode files. I guess I'll just have to maintain this by redefining the entire org-latex-template function to look at my variable instead of the hard coded string. A pain but apparently my own option. Thanks. On Mon, Feb 17, 2014 at 4:13 PM, Nicolas Goaziou n.goaz...@gmail.comwrote: Hello, Joe Hirn joseph.h...@gmail.com writes: Hello. I recently upgraded to org 8 from the builtin org (7.x) of Emacs 24.3 and lost the ability to customize the \hypersetup block via the custom var org-export-latex-hyperref-options-format. Platform is OSX, Emacs installed via homebrew and org-mode updated via package.el. Org 7.x defines the var in org-latex.el. Because it's a builtin, the custom var still displays in the 'org-latex-export group when configuring options. However, the new export logic from ox-latex.el does not define this custom var, nor does it respect the value if it is set. This is doubly confusing because it appears the var is available, but it actually unused. The problem will go with the next Emacs release. I found this thread from September which describes the same issue, but the patch did not address adding the custom var back and seems to have died. http://lists.gnu.org/archive/html/emacs-orgmode/2013-09/msg01364.html Actually, there is a way to ignore hypersetup block. See `org-latex-with-hyperref'. If you really want a custom command, I think it is better to first disable it with the variable aforementioned, then include your own with #+latex_header or in a custom latex class (see `org-latex-classes'). You can also use a filter to change it on the fly, but that would be less straightforward. Regards, -- Nicolas Goaziou
Re: [O] org-export-latex-hyperref-options-format
Joe Hirn joseph.h...@gmail.com writes: Hm. That's disappointing. I really prefer the original behavior. I don't want to copy #+latex_header to get this default behavior into each of my org-mode files. I suggested other ways to handle it. Anyway your patch has two drawbacks: 1. It is partly redundant with `org-latex-with-hyperref'. 2. A mere format string doesn't provide real flexibility (e.g., what if I don't want the pdfkeywords part?) when you want some. Perhaps something based on `format-spec' would be better. Regards, -- Nicolas Goaziou
Re: [O] Suggestion/bug: Parse inlinetask END with level sensitivity
Great! Taking a look at your solution I realize where the bug lay as well. Level is unimportant, it just scanned too long previously (it should only look if the next headline contains END, not look for the next headline with END). Regards, Anders Johansson Den mån 17 feb 2014 23:05:02 skrev Nicolas Goaziou: Hello, Anders Johansson mejlaande...@gmail.com writes: I thought that I would be able to use both tasks with and without an END line interchangeably: *** inlinetask without end some text *** inlinetask with end text inside inlinetask *** END The problem (not so surprising really) is that the parser finds the END of the second inlinetask and makes them nested in an export. This should be fixed in maint. Thank you for reporting it. For the record, inlinetasks cannot be nested, and the number of stars is not meaningful, as long as it is greater than `org-inlinetask-min-level'. Regards,
Re: [O] org-export-latex-hyperref-options-format
Joe Hirn joseph.h...@gmail.com writes: Hm. That's disappointing. I really prefer the original behavior. I don't want to copy #+latex_header to get this default behavior into each of my org-mode files. I guess I'll just have to maintain this by redefining the entire org-latex-template function to look at my variable instead of the hard coded string. A pain but apparently my own option. Before doing so reread Nicholas' suggestion. I.e.: Set org-latex-with-hyperref to nil. Look at org-latex-classes and add your preferred hypersetup to a new class (note an Org LaTeX class is a predefined preamble in LaTeX terms). Set org-latex-default-class to your new class. If this is not flexible enough use a filter. Several filter examples modifying the preamble have been posted on this list. —Rasmus On Mon, Feb 17, 2014 at 4:13 PM, Nicolas Goaziou n.goaz...@gmail.comwrote: Hello, Joe Hirn joseph.h...@gmail.com writes: Hello. I recently upgraded to org 8 from the builtin org (7.x) of Emacs 24.3 and lost the ability to customize the \hypersetup block via the custom var org-export-latex-hyperref-options-format. Platform is OSX, Emacs installed via homebrew and org-mode updated via package.el. Org 7.x defines the var in org-latex.el. Because it's a builtin, the custom var still displays in the 'org-latex-export group when configuring options. However, the new export logic from ox-latex.el does not define this custom var, nor does it respect the value if it is set. This is doubly confusing because it appears the var is available, but it actually unused. The problem will go with the next Emacs release. I found this thread from September which describes the same issue, but the patch did not address adding the custom var back and seems to have died. http://lists.gnu.org/archive/html/emacs-orgmode/2013-09/msg01364.html Actually, there is a way to ignore hypersetup block. See `org-latex-with-hyperref'. If you really want a custom command, I think it is better to first disable it with the variable aforementioned, then include your own with #+latex_header or in a custom latex class (see `org-latex-classes'). You can also use a filter to change it on the fly, but that would be less straightforward. Regards, -- Nicolas Goaziou -- El Rey ha muerto. ¡Larga vida al Rey!
Re: [O] org-export-latex-hyperref-options-format
I'm sorry man. That may have came off wrong. Did not mean to sound ungrateful. Thanks for offering the workarounds and thanks for responding. I definitely agree with drawback #2. So I understand, you're recommending I disable org-latex-with-hyperref and then add my own \\hypersetup. My goal would be to avoid placing a #+ entry into every .org file I compose. Which var would be the easiest to to adjust so I can emit \\hypersetup by default and still access the info map that is passed to org-latex-template. I'd like to get the keywords, subject and creator variables that are emitted right now. On Mon, Feb 17, 2014 at 5:23 PM, Nicolas Goaziou n.goaz...@gmail.comwrote: Joe Hirn joseph.h...@gmail.com writes: Hm. That's disappointing. I really prefer the original behavior. I don't want to copy #+latex_header to get this default behavior into each of my org-mode files. I suggested other ways to handle it. Anyway your patch has two drawbacks: 1. It is partly redundant with `org-latex-with-hyperref'. 2. A mere format string doesn't provide real flexibility (e.g., what if I don't want the pdfkeywords part?) when you want some. Perhaps something based on `format-spec' would be better. Regards, -- Nicolas Goaziou
[O] Not a standard Org-mode time string
I'm trying to set up the org-publish system to publish my personal notes in HTML. My org configuration consists only of (add-to-list 'load-path ~/src/org-mode/lisp) (add-to-list 'load-path ~/src/org-mode/contrib/lisp) (require 'org-publish) (setq org-publish-project-alist '((notes :base-directory ~/Documents/Notes :publishing-directory ~/Documents/published_notes :base-extension org :publishing-function org-html-publish-to-html :preserve-breaks t :with-email nil :recursive t :auto-sitemap t :sitemap-title Charles' Notes :makeindex t) (notes-static :base-directory ~/Documents/Notes :base-extension css\\|js\\|jpg\\|gif\\|png\\|svg :publishing-directory ~/Documents/published_notes :publishing-function org-publish-attachment) (charles-notes :components (notes notes-static Whilst visiting an org file in my Notes directory, I type M-x org-publish RET charles-notes and I receive the follow messages in my *Messages* buffer: Generating tree-style sitemap for Charles' Notes [6 times] condition-case: Bad timestamp `Saturday, 28.05.2011 ' Error was: (Not a standard Org-mode time string: Saturday, 28.05.2011 ) I don't understand the time-stamp messages. Can anyone help me debug this problem? The system specifics are: Emacs : GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.8.2) of 2013-07-27 on roseapple, modified by Debian Package: Org-mode version 8.2.5h (release_8.2.5h-636-g03514a @ /home/charles/src/org-mode/lisp/) I'm running from the master branch in git. Thanks in advance, Charles.
Re: [O] Not a standard Org-mode time string
Charles Turner chtu...@gmail.com writes: ... Generating tree-style sitemap for Charles' Notes [6 times] condition-case: Bad timestamp `Saturday, 28.05.2011 ' Error was: (Not a standard Org-mode time string: Saturday, 28.05.2011 ) I don't understand the time-stamp messages. Can anyone help me debug this problem? I don't think Org likes the format 28.05.2011 - try changing it to 2011-05-28 and see if the error goes away - although I don't really know where tha timestamp came from: please provide a backtrace. Read the org manual, section 1.4, Feedback, to find out how to produce a useful backtrace. -- Nick
Re: [O] simple way to call `C-c a v' or a way to bind it to a key?
At Mon, 17 Feb 2014 10:43:48 +0100, Nicolas Richard wrote: Marc Ihm m...@ihm.name writes: (global-set-key (kbd f12) (lambda () (interactive) (execute-kbd-macro (kbd C-c a v (global-set-key (kbd f12) (kbd C-c a v)) Ah, these are nice to know. Thanks, guys. -- yashi
Re: [O] parser: verbatim or code?
Hi Nicolas, At Sun, 16 Feb 2014 10:20:55 +0100, Nicolas Goaziou wrote: If we do change them, it should only happen in org-element.el. I don't think that would break existing documents, as code and verbatim are really close to each other. I don't care either way. Though, I lean towards the first option, as I like = as verbatim (which may be the source of the initial confusion). I'd suggest to keep documentation, and fix the code. Because, our document serves our _user_ as the interface definition and it's already been widely accepted. Users expect to have marked up code segment if they have =code= in their document. ;; It might be just me but I've been seen =code= in this mailing list ;; many times but never noticed ~code~, for example. -- yashi
Re: [O] orgtble and flyspell interaction causing mem exhaustion error?
I am seeing similar behavior with tables: if I type a bar and some text, then as soon as I enter second bar emacs freezes. Turning flyspell off seems to fix the problem. I actually see this both on Windows 7 with hunspell and on linux with aspell. I use org-mode from git on both but I haven't used tables in a while so I don't really know when the problem began. In non-org buffers flyspell doesn't seem to care about bars. Alex On Fri, Nov 29, 2013 at 12:10 AM, Sivaram Neelakantan nsivaram@gmail.com wrote: On Fri, Nov 29 2013,Nick Dokos wrote: Sivaram Neelakantan nsivaram@gmail.com writes: When I try to create an table using org-table-create, the table outline shows up and upon writing any word in any cell, it causes Emacs to freeze up with an error like 95% physical mem used. When I disable flyspell mode and try it again, the issue does not happen. Anyone else experiencing this or is it only me? Worked fine here. sorry, forgot to mention, mine is win32 Emacs 24.3 on win 7 with aspell from cygwin and the latest git snapshot of org. sivaram --
