Re: [O] Bug: Failure in `org-store-link'
This is not a tangling bug, this is actually a bug in org-store-link, which throws an error when called in an Org-mode file outside of any heading. Thanks for pointing this out. Best, Sean Allred seall...@smcm.edu writes: Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. With the following file: #+BEGIN_SRC org ,#+BEGIN_SRC sh :tangle test.sh ./test ,#+END_SRC ,* header #+END_SRC calling `org-babel-tangle` fails with stack trace: string-match(... nil) org-store-link(nil) org-babel-tangle-single-block(1) org-babel-tangle-collect-blocks(nil nil) org-babel-tangle(nil) call-interactively(org-babel-tangle nil nil) The problem is fixable by adding a dummy heading that `org-babel-tangle` can give an ID to. (Note my `org-id-link-to-org-use-id` is set to `t`.) I'm unsure on what correct behavior here would be; it seems the variable must be honored in any case, so perhaps it would be best to give a better error message along the lines of 'cannot give identification to a null heading' or somesuch. All the best, Sean 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.5h (8.2.5h-30-gdd810b-elpa @ /Users/sean/Dropbox/.emacs.d/elpa/org-20140303/) current state: == (setq org-export-preprocess-final-hook '((lambda nil (replace-string --\n -- \n))) org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe org-babel-header-arg-expand) org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook) org-occur-hook '(org-first-headline-recenter) org-metaup-hook '(org-babel-load-in-session-maybe) org-html-format-drawer-function '(lambda (name contents) contents) org-latex-format-inlinetask-function 'ignore org-confirm-shell-link-function 'yes-or-no-p org-id-link-to-org-use-id t org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default org-latex-format-headline-function 'org-latex-format-headline-default-function org-default-notes-file ~/Dropbox/org/notes.org org-after-todo-state-change-hook '(org-clock-out-if-current) org-latex-format-drawer-function '(lambda (name contents) contents) org-from-is-user-regexp \\Sean Allred\\ org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-babel-pre-tangle-hook '(save-buffer) org-mode-hook '(#[nil \300\301\302\303\304$\207 [org-add-hook change-major-mode-hook org-show-block-all append local] 5] #[nil \300\301\302\303\304$\207 [org-add-hook change-major-mode-hook org-babel-show-result-all append local] 5] org-babel-result-hide-spec org-babel-hide-all-hashes) org-ascii-format-drawer-function '(lambda (name contents width) contents) org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe) org-directory ~/Dropbox/org org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-hide-inline-tasks org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-babel-tangle-lang-exts '((perl . pl) (ruby . rb) (python . py) (emacs-lisp . el)) org-confirm-elisp-link-function 'yes-or-no-p org-metadown-hook '(org-babel-pop-to-session-maybe) org-html-format-headline-function 'ignore org-structure-template-alist '((nt #+name: ?\n#+begin_src emacs-lisp :tangle \\\n\n#+end_src) (n #+name: ?\n#+begin_src \n\n#+end_src) (es #+begin_src emacs-lisp\n?\n#+end_src) (esf #+begin_src emacs-lisp :tangle %file\n?\n#+end_src) (s #+BEGIN_SRC ?\n\n#+END_SRC src lang=\?\\n\n/src) (e #+BEGIN_EXAMPLE\n?\n#+END_EXAMPLE example\n?\n/example) (q #+BEGIN_QUOTE\n?\n#+END_QUOTE quote\n?\n/quote) (v #+BEGIN_VERSE\n?\n#+END_VERSE verse\n?\n/verse) (V #+BEGIN_VERBATIM\n?\n#+END_VERBATIM verbatim\n?\n/verbatim) (c #+BEGIN_CENTER\n?\n#+END_CENTER center\n?\n/center) (l #+BEGIN_LaTeX\n?\n#+END_LaTeX literal style=\latex\\n?\n/literal) (L
Re: [O] mobileorg capture todo's
Chris Henderson henders...@gmail.com writes: The org file on my computer has * Tasks * Projects * Someday/ Maybe. If I capture on mobileorg, is there a way for the captured items to be listed on my computer's org file under the * Tasks section when I sync it? I think at the moment they are added to the flagged.org file and I'm not sure how to move items from that to my mail org file. I never open the flagged.org file. The name of this file is customizable but here's what I do. I have: (setq org-mobile-inbox-for-pull ~/org/inbox.org) then the value for org-agenda-files contains this file. Next I set refile targets[0] simply like: (setq org-refile-targets '((org-agenda-files :maxlevel . 2))) which allows me to visit inbox.org and use C-c C-w to move items to where I want them. [0]: http://orgmode.org/manual/Refile-and-copy.html#Refile-and-copy -- -sean
[O] small koma bug
Hello Rasmus and all,
I think I have found a small bug in ox-koma-letter, but to fix it I
would like your input.
The bug: if from-address is not specified in the file, then it will be
set unconditionally to the empty string, even if it is specified in an
lco file.
The reason of the bug is as follows.
To set up the from address, we call this:
#+begin_src emacs-lisp
(let ((from-address (org-koma-letter--determine-to-and-from info 'from)))
(and from-address (format \\setkomavar{fromaddress}{%s}\n from-address)))
#+end_src
This uses this function:
#+begin_src emacs-lisp
(defun org-koma-letter--determine-to-and-from (info key)
Given INFO determine KEY for the letter.
KEY should be `to' or `from'.
`ox-koma-letter' allows two ways to specify TO and FROM. If both
are present return the preferred one as determined by
`org-koma-letter-prefer-special-headings'.
(let ((option (plist-get info (if (eq key 'to) :to-address :from-address)))
(headline (org-koma-letter--get-tagged-contents key)))
(replace-regexp-in-string
\n \n
(org-trim
(or (if (plist-get info :special-headings) (or headline option)
(or option headline))
;; Fallback values.
(if (eq key 'to) \\mbox{} org-koma-letter-from-address))
#+end_src
Note that in the default case we return org-koma-letter-from-address,
which is set to the empty string by default:
#+begin_src emacs-lisp
(defcustom org-koma-letter-from-address
Sender's address, as a string.
This option can also be set with one or more FROM_ADDRESS
keywords.
:group 'org-export-koma-letter
:type 'string)
#+end_src
As the empty string is considered as true, we apply the format
function in the first code block.
I would suggest to have org-koma-letter-from-address begin nil as
default. My question is: is it an allowed value for a string?
Thanks,
Alan
Re: [O] verbatim/code text and line breaks with auto fill mode
Alan Schmitt wrote: I've continued looking into this, and it seems that what I want is use `fill-nobreak-predicate'. This is what I ended up doing: #+begin_src emacs-lisp (add-hook 'org-mode-hook (lambda () (add-hook 'fill-nobreak-predicate 'org-in-verbatim-emphasis))) #+end_src All the pieces were already there, it just took me a while to put them together ;-) Shouldn't this be standard in Org, as it breaks LaTeX compilation otherwise? Best regards, Seb -- Sebastien Vauban
[O] Howto: different faces for begin_src and results
Hi I was wondering if it's possible to have different faces for #+begin_src/#+end_src and results so distinguishing the blocks is easier. TIA. Protect your computer files with professional cloud backup. Get PCRx Backup and upload unlimited files automatically. Learn more at http://backup.pcrx.com/mail
Re: [O] verbatim/code text and line breaks with auto fill mode
Hello, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Alan Schmitt wrote: I've continued looking into this, and it seems that what I want is use `fill-nobreak-predicate'. This is what I ended up doing: #+begin_src emacs-lisp (add-hook 'org-mode-hook (lambda () (add-hook 'fill-nobreak-predicate 'org-in-verbatim-emphasis))) #+end_src All the pieces were already there, it just took me a while to put them together ;-) Shouldn't this be standard in Org, as it breaks LaTeX compilation otherwise? This is not an Org problem, as verbatim objects can span over lines. OTOH, `latex' back-end could remove newline characters from verbatim and code contents. Regards, -- Nicolas Goaziou
Re: [O] Bug in export of call lines
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I've been dusting off a draft paper written when the new export
framework was still in contrib. Now that I've brought the file
up-to-date so that it exports asynchronously again, I'm getting an error
that wasn't there before.
[...]
Note the new line after each call result and the premature termination
of the {description} environment.
It would help to see the source of axe-x-section and axe-wt. Do they
insert spurious newline characters?
Also, you can call (org-export-execute-babel-code) to get what is really
parsed once Babel code is expanded.
Regards,
--
Nicolas Goaziou
[O] Inactive timestamps in planning types?
Hi List, can inactive timestamps appear in - title-stamps (the timestamps attached to headlines) - planning types like deadline, scheduled and closed ? It does not seem to make much sense to me, but maybe I'm overlooking something. -- cheers, Thorsten
Re: [O] Using sideways table with :placement in Org 8.0?
On Mar 10, 2014 12:22 AM, Nick Dokos ndo...@gmail.com wrote:
John Hendy jw.he...@gmail.com writes:
I was just playing around with the new syntax for accessing
sidewaystable in Org 8.0, but it doesn't seem to be working. The
manual /seems/ pretty straightforward:
- http://orgmode.org/manual/LaTeX-specific-attributes.html
:placement
Float environment for the table. Possible values are sidewaystable,
multicolumn, t and nil. When unspecified, a table with a caption will
have atable environment. Moreover, :placement attribute can specify
the positioning of the float.
Actually it says:
,
| `:float'
| `:placement'
| Float environment for the table. Possible values are
| `sidewaystable', `multicolumn', `t' and `nil'. When unspecified,
| a table with a caption will have a `table' environment. Moreover,
| `:placement' attribute can specify the positioning of the float.
`
Try
#+attr_latex: :float sidewaystable
instead. The doc does need clarification.
Blast. I was close! I thought :float was standalone so I tried this combo
last night as well.
:float :placement sidewaystsble
Now it makes sense I think. Is placement just for things like [htb], then?
If so, perhaps those should be split into separate line items.
Thanks!
John
Here's a test document:
* Heading
#+attr_latex: :placement sidewaystable
| *alpha* | *beta* | *gamma* | *delta* |
|-++-+-|
| 100 |200 | 300 | 400 |
| 200 |100 | 17.321 | 133.3 |
| 400 | 50 | 4.162 |44.4 |
| 800 | 25 | 2.040 |14.8 |
Minimal config loaded with `emacs -Q`:
(add-to-list 'load-path ~/.elisp/org.git/lisp/)
(add-to-list 'load-path ~/.elisp/org.git/contrib/lisp/)
(require 'ox-latex)
The resultant table is not inside of \begin/end{sidewaystable}:
\begin{center}
\begin{tabular}{}
\textbf{alpha} \textbf{beta} \textbf{gamma} \textbf{delta}\\
\hline
100 200 300 400\\
200 100 17.321 133.3\\
400 50 4.162 44.4\\
800 25 2.040 14.8\\
\end{tabular}
\end{center}
The heading contains \usepackage{rotating}, but it's not calling for
sidewaystable anyway, so that shouldn't matter.
Thanks for any suggestions.
John
--
Nick
Re: [O] small koma bug
Hi Alan,
Alan Schmitt alan.schm...@polytechnique.org writes:
I think I have found a small bug in ox-koma-letter, but to fix it I
would like your input.
The bug: if from-address is not specified in the file, then it will be
set unconditionally to the empty string, even if it is specified in an
lco file.
OK. AFAIK it's OK to leave out the fromaddress and fromname.
The reason of the bug is as follows.
To set up the from address, we call this:
#+begin_src emacs-lisp
(let ((from-address (org-koma-letter--determine-to-and-from info 'from)))
(and from-address (format \\setkomavar{fromaddress}{%s}\n
from-address)))
#+end_src
How about:
(let ((from-address (org-koma-letter--determine-to-and-from info 'from)))
(and (org-string-nw-p from-address) (format
\\setkomavar{fromaddress}{%s}\n from-address)))
Or more explicitly
(let ((from-address (org-koma-letter--determine-to-and-from info 'from)))
(when (org-string-nw-p from-address) (format
\\setkomavar{fromaddress}{%s}\n from-address)))
This uses this function:
#+begin_src emacs-lisp
(defun org-koma-letter--determine-to-and-from (info key)
Given INFO determine KEY for the letter.
KEY should be `to' or `from'.
`ox-koma-letter' allows two ways to specify TO and FROM. If both
are present return the preferred one as determined by
`org-koma-letter-prefer-special-headings'.
(let ((option (plist-get info (if (eq key 'to) :to-address :from-address)))
(headline (org-koma-letter--get-tagged-contents key)))
(replace-regexp-in-string
\n \n
(org-trim
(or (if (plist-get info :special-headings) (or headline option)
(or option headline))
;; Fallback values.
(if (eq key 'to) \\mbox{} org-koma-letter-from-address))
#+end_src
I guess org-koma-letter-from-address can be left empty, but for
instance 'to must have a value different from the empty string to not
create a LaTeX error. As I said above, quick testing suggest this is
not necessary for fromaddress.
As the empty string is considered as true, we apply the format
function in the first code block.
See below.
I would suggest to have org-koma-letter-from-address begin nil as
default. My question is: is it an allowed value for a string?
You can use org-string-nw-p to test is S is only white-space. When
Nicolas cleaned the file he made all (or most?) defaults into strings,
so let's stick with that.
Let me know if your happy with this.
—Rasmus
--
Summon the Mothership!
Re: [O] exporter for latex g-brief - extending \begin{document}
LanX, LanX lanx.p...@googlemail.com writes: Have you tried ox-koma-letter.el? not yet, I just started recently switching back to latex and g-brief did what I needed for a formal german letter and I just need it once per month so far. KOMA-Script has build in support for DIM. #+TITLE: title #+BEGIN_g-brief ... here comes text #+END_g-brief OK thanks, I take it as indication that the exporter can't be configured to do this implicitely... Sure, you can make a derived class, use a filter or something else. Ox-koma-letter is an example of a derived class for letters. There is also a letter exporter using groff as backend. Note that the special heading keywords (see the wiki) are not compatible across the two exporters. could you please be more specific? It's a new and in all dimension superior export engine. On this list we'll generally assume you're using a recent version of Org. Currently, this implies a version ≥ 8. Hope it helps, Rasmus -- This space is left intentionally blank
[O] How to detect latex subscripts with org-element?
Hi,
I want to detect if my point is inside a super/subscript irrespective
of whether I'm in a latex-fragment/environment or in plain text. If
| is my point, I can easily detect the subscript here
x_{z|}
using `org-element-context`. However, I have found no good way of
detecting if I'm in the subscript in this example
$x^{3}_{z|}$
Can I somehow ask org-element to tread a latex-fragment or a
latex-environment as-if it was a plain paragraph?
The motivation is that I'm writing a function to escape fontified
subscripts, such as those of the second example, using double space,
but I cannot find a way to detect if I'm in a subscript when I have
several sup/superscritps.
Thanks,
Rasmus
--
Hooray!
Re: [O] small koma bug
Rasmus ras...@gmx.us writes:
How about:
(let ((from-address (org-koma-letter--determine-to-and-from info 'from)))
(and (org-string-nw-p from-address) (format
\\setkomavar{fromaddress}{%s}\n from-address)))
Or more explicitly
(let ((from-address (org-koma-letter--determine-to-and-from info 'from)))
(when (org-string-nw-p from-address) (format
\\setkomavar{fromaddress}{%s}\n from-address)))
It sounds good. I'll commit this change.
Thanks,
Alan
[O] Localized time-stamps irritate calc
Hi! I work on different systems with basically the same Emacs config. However, on my Linux box I get time-stamps like [2014-03-10 Mon] and [2014-03-04 Tue] but on my Windows box I get [2014-03-10 Mo] and [2014-03-04 Di]. Obviously, my Windows box is having some German set-up (Di = Dienstag) I don't really need. I have no idea where Emacs is getting this information. Most probably environment settings I do not know of. Org-mode is doing fine with those German time-stamps. Unfortunately, when I use time-stamps in tables and calculate their difference (duration in days), I get #ERROR. When I manually change Di to Tue, it works. 1) How am I able to change to English time-stamps on my Windows box. 2) Is this a calc-bug? Thanks! -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: get Memacs from https://github.com/novoid/Memacs https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] org-element-context doesn't parse consistently link with spaces
Hello, Bastien b...@gnu.org writes: Please do ~$ git fetch --tags to update all your tags, and make again. That worked. Thank you. Tags are on commits, not on branches, and commmits can belong to multiple branches. Since the tagged commit is both on the maint and the master branch, make autoloads will use the same tag to generate Org's version in both case. Ah, right. Oddly, I was pretty sure that some tags were identifying master branch only, e.g, I can't remember seeing 8.2.5c on master. Regards, -- Nicolas Goaziou
Re: [O] words starting with call_ confuse C-c C-c and export
Hello, Eric Schulte schulte.e...@gmail.com writes: Nicolas Goaziou n.goaz...@gmail.com writes: We're talking about function names, not free-form text, so limitations are understandable. For example, macro names only allow alphanumeric characters or hyphens and have to start with an alphabetic character. Having considered this, unless there are user objections I'd be happy limiting function names to the same restricted alphabet as macro names. This would be a breaking change though, and should be mentioned as such in the notes. Once you have settled for a regexp (do you want to include / character?), please let me know, I'll update org-element accordingly. Regards, -- Nicolas Goaziou
Re: [O] words starting with call_ confuse C-c C-c and export
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Eric Schulte schulte.e...@gmail.com writes: Nicolas Goaziou n.goaz...@gmail.com writes: We're talking about function names, not free-form text, so limitations are understandable. For example, macro names only allow alphanumeric characters or hyphens and have to start with an alphabetic character. Having considered this, unless there are user objections I'd be happy limiting function names to the same restricted alphabet as macro names. This would be a breaking change though, and should be mentioned as such in the notes. Once you have settled for a regexp (do you want to include / character?), please let me know, I'll update org-element accordingly. Is / allowed in macro names? I think the biggest benefit here is unification between macro and function names. Is there a macro name regexp which could be used directly (to ensure that these two stay unified)? I don't see one, so I expect we'll want to add an org-babel-function-name regexp along the lines of [a-zA-Z0-9\-\/]+. This would then be used in the following variables. - org-babel-src-block-regexp - org-babel-src-name-w-name-regexp And the following functions should be updated to ensure that the name only includes the allowed characters. - org-babel-named-data-regexp-for-name - org-babel-named-src-block-regexp-for-name Does this sound about right? Regards, -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] Howto: different faces for begin_src and results
Hi Miguel, Miguel Ruiz rbeni...@inbox.com writes: I was wondering if it's possible to have different faces for #+begin_src/#+end_src and results so distinguishing the blocks is easier. Yes: M-x customize-face RET org-block-begin-line RET M-x customize-face RET org-meta-line RET HTH, -- Bastien
[O] `org-attach-file-list' doesn't allow dotfiles
Hi all, I recently investigated why `org-open-at-point` uses smplayer to open *.mp4 links, although the system's default is vlc. The solution was to create ~/.mailcap with video/mp4; vlc %s I wanted to store this file as an attachment in an org document, so I don't forget about it, but this attachment can't be opened due to `org-attach-file-list` ignoring all files that start with a dot. I would modify it like this to ignore just . and ..: --- a/lisp/org-attach.el +++ b/lisp/org-attach.el @@ -425,7 +425,7 @@ This can be used after files have been added externally. Return a list of files in the attachment directory. This ignores files starting with a \.\, and files ending in \~\. (delq nil - (mapcar (lambda (x) (if (string-match ^\\. x) nil x)) + (mapcar (lambda (x) (if (string-match ^\\.\\.?$ x) nil x)) (directory-files dir nil [^~]\\' Is there a reason behind this dot file restriction? Would anything break if the proposed change was made? regards, Oleh
Re: [O] Bug in export of call lines
Aloha Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I've been dusting off a draft paper written when the new export
framework was still in contrib. Now that I've brought the file
up-to-date so that it exports asynchronously again, I'm getting an error
that wasn't there before.
[...]
Note the new line after each call result and the premature termination
of the {description} environment.
It would help to see the source of axe-x-section and axe-wt. Do they
insert spurious newline characters?
Also, you can call (org-export-execute-babel-code) to get what is really
parsed once Babel code is expanded.
That's a big help. Thanks.
It appears that executing the R code block does insert a newline. This
must be the behavior that changed.
executing R code block (axe-x-section)...
Wrote
/var/folders/fp/mgkcqpy17clb6dzh3_xgs0n8gn/T/babel-78240Cke/ob-input-78240NlJ
3.7 \\texttimes 2
executing Emacs-Lisp code block...
(results (quote 3.7 \\texttimes 2
))
Here is the source code:
*** Cross-section of a particular tool, in cm
#+name: axe-x-section
#+header: :var t=final-axe-table
#+header: :var a=3141
#+header: :results raw
#+BEGIN_SRC R
w - t[t[,2]==a,16]/10
th - t[t[,2]==a,18]/10
paste0(w, ' \\texttimes ', th)
#+END_SRC
#+results: axe-x-section
3.9 \texttimes 2
All the best,
Tom
--
T.S. Dye Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
Re: [O] Bug in export of call lines
t...@tsdye.com (Thomas S. Dye) writes:
Aloha Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I've been dusting off a draft paper written when the new export
framework was still in contrib. Now that I've brought the file
up-to-date so that it exports asynchronously again, I'm getting an error
that wasn't there before.
[...]
Note the new line after each call result and the premature termination
of the {description} environment.
It would help to see the source of axe-x-section and axe-wt. Do they
insert spurious newline characters?
Also, you can call (org-export-execute-babel-code) to get what is really
parsed once Babel code is expanded.
That's a big help. Thanks.
It appears that executing the R code block does insert a newline. This
must be the behavior that changed.
executing R code block (axe-x-section)...
Wrote
/var/folders/fp/mgkcqpy17clb6dzh3_xgs0n8gn/T/babel-78240Cke/ob-input-78240NlJ
3.7 \\texttimes 2
executing Emacs-Lisp code block...
(results (quote 3.7 \\texttimes 2
))
Here is the source code:
*** Cross-section of a particular tool, in cm
#+name: axe-x-section
#+header: :var t=final-axe-table
#+header: :var a=3141
#+header: :results raw
#+BEGIN_SRC R
w - t[t[,2]==a,16]/10
th - t[t[,2]==a,18]/10
paste0(w, '\\texttimes', th)
#+END_SRC
#+results: axe-x-section
3.9\texttimes2
I believe this issue of newlines returned from inline code blocks
(specifically with R) came up on the list recently, but unfortunately I
can't find the conversation.
Somehow this doesn't seem to be a problem with other languages, so I
believe the necessary fix may be R specific.
Sorry I can't be of more help,
All the best,
Tom
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
[O] [PATCH] org-plot: Handle explicit date/time index
* lisp/org-plot.el (org-plot-quote-tsv-field): Dump data as is when `timeind' is set. * lisp/org-plot.el (org-plot/gnuplot): By-pass type checking when either `textind' or `timeind' is set. The current org-plot relies on `org-table-number-regexp' and `org-ts-regexp3' to check the index type. However, we already have `timeind' to indicate that the index is the datatype of date/time. By-pass the type checking in `org-plot/gnuplot' when either `textind' or `timeind' is set. The whole point of the check is to determine the type. We do not need that when we already know. Also dump the date/time data with `org-plot-quote-tsv-field' as is, without double quotes, when `timeind' is set. So that we can use `timefmt' to read what we have. Currently we do not have a good way to specify `timefmt' with the double quotes. --- Hi, It seems to me that dates with slash (ie. 2014/03/11) does not work with the current org-plot.el, even if you set `timeind' and `timefmt'. That's because the current org-plot treat 2014/03/11 as string instead of data/time. Here is an ECM: #+PLOT: ind:1 #+PLOT: timeind:t timefmt:%Y/%m/%d #+PLOT: set:format x '%y-%m' #+PLOT: set:xtics rotate by -45 | 2014/03/11 | 0 | | 2014/03/12 | 1 | | 2014/03/13 | 2 | This patch fixes my itch but I'm not sure it doesn't break others. Could you please test it? and tell me how it works. BTW, do we have any test for org-plot? Let me know if there is any. Thanks, -- yashi lisp/org-plot.el | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/lisp/org-plot.el b/lisp/org-plot.el index 556b9ef..b5000ea 100644 --- a/lisp/org-plot.el +++ b/lisp/org-plot.el @@ -109,7 +109,8 @@ will be added. Returns the resulting property list. (defun org-plot-quote-tsv-field (s) Quote field S for export to gnuplot. - (if (string-match org-table-number-regexp s) s + (if (or (string-match org-table-number-regexp s) + (plist-get params :timeind)) s (if (string-match org-ts-regexp3 s) (org-plot-quote-timestamp-field s) (concat \ (mapconcat 'identity (split-string s \) \\) \ @@ -312,7 +313,9 @@ line directly before or after the table. (when y-labels (plist-put params :ylabels y-labels) ;; check for timestamp ind column (let ((ind (- (plist-get params :ind) 1))) - (when (and (= ind 0) (equal '2d (plist-get params :plot-type))) +(when (and (= ind 0) (equal '2d (plist-get params :plot-type)) + (not (or (plist-get params :timeind) +(plist-get params :textind (if (= (length (delq 0 (mapcar (lambda (el) -- 1.9.0
Re: [O] [RFC] Proposal for rebindings in Org 8.3
Bastien b...@gnu.org writes: | Key | Command | Proposal | Status | |---+---+--+| | C-c # | Checkboxes| C-c x| Free | | C-c ~ | Cooperation | C-c C-~ | Free | | C-c , | Priorities| C-c C-, | Free | | C-c ? | Editing and debugging formulas| C-c C-? | Free | | C-c ! | Creating timestamps | C-c C-! | Free | I tried C-c C-! in my environment, and it fails, no noticing the C-! (which involves shift) keypress (with ^H k; I get it that this is proposed). I have C-1 bound in my window manager to switch desktops, since that binding doesn't take away the ability to generate any ASCII character. I'm running emacs -nw under tmux on one machine (netbsd), connected via ssh from a mac using Terminal. While one can argue that various emulations are broken, org should be fully usable with a 7-bit terminal connection, and non-kludgy with an 8-bit connection. In general, I find that emacs works fine with that, although one has to prefix with ESC instead of the meta key. I've always been bothered by keybindings like C-S-left, which while useful, cause there to be no available keystroke sequence to perform the function. I find this surprising; I'd expect within emacs/org culture there to be more people using terminal-mode emacs. pgpRrqLT8J8a0.pgp Description: PGP signature
Re: [O] [RFC] Move ox-koma-letter into core?
Viktor Rosenfeld listuse...@gmail.com writes: 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. I agree that the assignment process is a big barrier; it's personally kept me from starting down the path to contributing to several projects. In particular indemnification is problematic. But, org-mode is the tail, and it's unlikely emacs will decide to stop requiring assignment because of anyone here. pgpvPkHTOryMK.pgp Description: PGP signature
Re: [O] Howto: different faces for begin_src and results
Miguel Ruiz rbeni...@inbox.com writes: I was wondering if it's possible to have different faces for #+begin_src/#+end_src and results so distinguishing the blocks is easier. Put cursor on the character whose colour you want to change and do M-x cusotmize-face
[O] Org-Mode and Task Dependencies
Simple question -- does org-mode handle task dependencies? And, if so, how well? In the outline form, I see you could setup parent-child relationships between tasks. I'm looking for more of tasks that aren't related, but are dependent on each other. In particular, in a parent-child relationship, you might say THIS task is done when all of THOSE tasks are done whereas I'm looking for more of a THIS task can be started when all of THOSE tasks are done. How would you set this up in Org-Mode? -- David Masterson
Re: [O] Org-Mode and Task Dependencies
David Masterson dsmaster...@gmail.com writes: Simple question -- does org-mode handle task dependencies? And, if so, how well? In the outline form, I see you could setup parent-child relationships between tasks. I'm looking for more of tasks that aren't related, but are dependent on each other. In particular, in a parent-child relationship, you might say THIS task is done when all of THOSE tasks are done whereas I'm looking for more of a THIS task can be started when all of THOSE tasks are done. How would you set this up in Org-Mode? Maybe what you are looking for is this section (info (org) TODO dependencies) in the manual. -- Nick
Re: [O] Org-Mode and Task Dependencies
David Masterson dsmaster...@gmail.com writes: Simple question -- does org-mode handle task dependencies? And, if so, how well? In the outline form, I see you could setup parent-child relationships between tasks. I'm looking for more of tasks that aren't related, but are dependent on each other. In particular, in a parent-child relationship, you might say THIS task is done when all of THOSE tasks are done whereas I'm looking for more of a THIS task can be started when all of THOSE tasks are done. How would you set this up in Org-Mode? have a look here: http://orgmode.org/manual/TODO-dependencies.html -- cheers, Thorsten
[O] [Patch] don't add indent for empty line when exiting, a code edit
Hi I started using org babel for python, but when using C-c ' I always ended up with white space added to the empty lines in the source code when returning into the org buffer. This especially shows up (setq-default show-trailing-whitespace t). I tried to fix this in org. It seems to work over here, but my elisp as well as my understanding of org-mode is not perfect ;) Let me know if it needs more work. Arun From e393fed9dbb132fdefff66d304f67f7def643140 Mon Sep 17 00:00:00 2001 From: Arun Persaud a...@nubati.net Date: Mon, 10 Mar 2014 17:09:12 -0700 Subject: [PATCH] lisp/org-src.el: don't add indent for empty line when exiting a code edit Using C-c ' to edit code blocks adds an indent to all lines when exiting from the code edit. This leaves trailing whitespace in the buffer, which can be especially annoying when using show-trailing-whitespace. --- lisp/org-src.el | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/lisp/org-src.el b/lisp/org-src.el index d1f6879..ef09bd6 100644 --- a/lisp/org-src.el +++ b/lisp/org-src.el @@ -737,8 +737,10 @@ with \,*\, \,#+\, \,,*\ and \,,#+\. (unless (or single preserve-indentation (= total-nindent 0)) (setq indent (make-string total-nindent ?\ )) (goto-char (point-min)) - (while (re-search-forward ^ nil t) - (replace-match indent))) +(while (re-search-forward ^ nil t) + (if (not (looking-at $)) + (replace-match indent) + (forward-char 1 (if (org-bound-and-true-p org-edit-src-picture) (setq total-nindent (+ total-nindent 2))) (setq code (buffer-string)) -- 1.9.0
[O] babel: using empty lines in python code while using session
Hi I started using python in org babel. The manual, for example [1], points to the fact that in session mode you can't have empty lines, since they will be interpreted differently. However, if you use ipython you can get around this, by using the following in your .emacs: ; use ipython in org mode (setq org-babel-python-command ipython3 --no-banner --classic --no-confirm-exit) ; use %cpaste to paste code into ipython in org mode (defadvice org-babel-python-evaluate-session (around org-python-use-cpaste (session body optional result-type result-params) activate) Add a %cpaste and '--' to the body, so that ipython does the right thing. (setq body (concat %cpaste\n body \n--)) ad-do-it (if (stringp ad-return-value) (setq ad-return-value (replace-regexp-in-string \\(^Pasting code; enter '--' alone on the line to stop or use Ctrl-D\.[\r\n]:*\\) ad-return-value - I found it much easier, if I don't have to worry about the empty lines when writing python code. Might be useful for someone else, so I thought I post it here. Also, in ipython 2.0 you will be able to use %cpaste -q to suppress cpaste output, which will simplify the above a bit. thanks again for org-mode, it's getting more useful all the time ;) Arun [1] http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-python.html
Re: [O] Org-Mode and Task Dependencies
Nick Dokos ndo...@gmail.com writes: David Masterson dsmaster...@gmail.com writes: Simple question -- does org-mode handle task dependencies? And, if so, how well? In the outline form, I see you could setup parent-child relationships between tasks. I'm looking for more of tasks that aren't related, but are dependent on each other. In particular, in a parent-child relationship, you might say THIS task is done when all of THOSE tasks are done whereas I'm looking for more of a THIS task can be started when all of THOSE tasks are done. How would you set this up in Org-Mode? Maybe what you are looking for is this section (info (org) TODO dependencies) in the manual. Oh! Didn't see that before. It will take me some time to understand org-depend.el which, I think, is what I'm looking for. Thanks. Hmmm. That does bring up a question. Will MobileOrg handle dependencies in the org-depend sense? -- David Masterson
Re: [O] Bug in export of call lines
Eric Schulte schulte.e...@gmail.com writes: Somehow this doesn't seem to be a problem with other languages, so I believe the necessary fix may be R specific. Following is a small test that appears to indicate that the bug is R specific and only bites when the source code block has :results raw. #+DATE: \today #+LATEX_CLASS: article #+LATEX_CLASS_OPTIONS: #+LATEX_HEADER: #+LATEX_HEADER_EXTRA: * Export this subtree to LaTeX :PROPERTIES: :results: raw :END: Will lisp-2 export call_lisp-2() with a newline? Will python-2 export call_python-2() with a newline? Will r-2 export call_r-2() with a newline? Will lisp-2-raw export call_lisp-2-raw() with a newline? Will python-2-raw export call_python-2-raw() with a newline? Will r-2-raw export call_r-2-raw() with a newline? * Similar code in three languages #+name: lisp-2 #+begin_src lisp (+ 1 1) #+end_src #+name: python-2 #+begin_src python return(1 + 1) #+end_src #+name: r-2 #+begin_src R 1 + 1 #+end_src #+name: lisp-2-raw #+begin_src lisp :results raw (+ 1 1) #+end_src #+name: python-2-raw #+begin_src python :results raw return(1 + 1) #+end_src #+name: r-2-raw #+begin_src R :results raw 1 + 1 #+end_src Here is the relevant portion of the LaTeX export: Will lisp-2 export 2 with a newline? Will python-2 export 2 with a newline? Will r-2 export 2 with a newline? Will lisp-2-raw export 2 with a newline? Will python-2-raw export 2 with a newline? Will r-2-raw export 2 with a newline? % Emacs 24.3.1 (Org mode 8.2.5h) All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] Some links not working anymore for me
Hi, Org people. For a little while, I've not been able to follow links to Org files, when the link contains a search to some header, and the searched header itself contains white space or non-ASCII characters. I just made this patch that apparently helps me out of this new little misery :-). The patch is only indicative: I'm not sure it is the proper way to solve the difficulty, as I do not really understand all the code surrounding it! diff --git a/lisp/org.el b/lisp/org.el index a0ed137..5c41b52 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -10555,7 +10555,8 @@ is used internally by `org-open-link-from-string'. (cond ((not option) nil) ((org-string-match-p \\`[0-9]+\\' option) (list (string-to-number option))) - (t (list nil option + (t (list nil + (org-link-unescape option) ((assoc type org-link-protocols) (funcall (nth 1 (assoc type org-link-protocols)) path)) ((equal type help) François
Re: [O] Some links not working anymore for me
François Pinard pin...@iro.umontreal.ca writes: Hi, Org people. Hello, For a little while, I've not been able to follow links to Org files, when the link contains a search to some header, and the searched header itself contains white space or non-ASCII characters. I just made this patch that apparently helps me out of this new little misery :-). The patch is only indicative: I'm not sure it is the proper way to solve the difficulty, as I do not really understand all the code surrounding it! See this commit 8 days ago: 567ec87 * | Unescape links before opening them diff --git a/lisp/org.el b/lisp/org.el index a0ed137..5c41b52 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -10555,7 +10555,8 @@ is used internally by `org-open-link-from-string'. (cond ((not option) nil) ((org-string-match-p \\`[0-9]+\\' option) (list (string-to-number option))) -(t (list nil option +(t (list nil + (org-link-unescape option) ((assoc type org-link-protocols) (funcall (nth 1 (assoc type org-link-protocols)) path)) ((equal type help) François -- Daimrod/Greg
