Re: [O] [ox, patch] #+SUBTITLE
Rasmus writes: >> Could you elaborate a bit in the comment? > > Consider if title is nil. With format-spec I'll get an empty . > As I remember, the W3 checker dislike these. I have never used these > html5 slides, so I don't really know how to fix it. You probably should add this to the comments in the file. > But de facto KEYWORDS and DESCRIPTION were also only supported in some > backends. I think it's more convenient to have these type of keywords in > one place. But I don't feel strongly about this. I would like to keep a clear and somewhat future-proof rule about this: 1. A keyword a user can expect to find in all back-ends where it makes sense should be defined in "ox.el". To put it differently, it can be considered as a bug if a back-end could /simply/ support a keyword in this category but doesn't. Keywords in this category are to be documented in (info "(org)Export settings"). 2. Other keywords are defined in their respective back-end, and documented in their respective chapter in the manual. As a non-trivial example, consider :email. You can expect it to produce something sensible in any back-end. Yet, "ox-icalendar" doesn't use it. It still belongs to first category. If we support SUBTITLE everywhere it makes sense, it might be worth adding it to the first category. Actually, considering the rule above, I even lean towards adding it to that category. WDYT? Also, I'm going to implement the `parse-object' and `parse-element' behaviour we discussed in another thread, and remove `org-element-document-properties' (and the relative `org-export-document-properties') altogether. This will remove a useless distinction among keywords: two categories are enough. As a side-effect, however, `org-element-context' will not show objects when called on TITLE and al, but that might be a good thing actually (there are objects in there only during export and only if considered export back-end makes use of them). >> Nitpick: >> >> (and formatted-subtitle ...) > > Can you explain why (and ⋯) should be used here? It makes more obvious you are expecting a return value. `when' is preferred for side effects. However, this is not a hard rule, since (and test ... some very long computation) is less clear than (when test ... some very long computation) However, it doesn't apply in this case. As I warned, this is all about nitpicking anyway. Regards,
Re: [O] Updating to the current org-mode in emacs trunk, and Org stable
Bastien writes: >> AFAIK, Bastien (Cc'ed) is working on a 8.3 release, but also needs to >> catch-up with all the traffic on the ML. > > Yes, this is it. I am slowly getting out of the black hole that > swallowed my life for the last six month, catching up with emails > on this mailing list. I'm happy to know. > I'll be able to release 8.3 next week. Fåk. Better get to work then :) Thanks! Let us know if you have well-defied tasks that can be outsourced. > Thanks for your patience, No worries. —Rasmus -- The Kids call him Billy the Saint
Re: [O] [ox, patch] #+SUBTITLE
Nicolas Goaziou writes:
> Also, assuming you keep :subtitle instead of :BACKEND-subtitle, these
> should also be documented in Publishing options.
So I *still* don't see this. I assume you want me to add something do you
want me to add lines like this:
@item @code{:subtitle} @tab ""
To the tables akin to the one in @subsubheading Beamer specific
properties?
Note that there's no mapping to a variable, only to an buffer-keyword.
Thanks,
Rasmus
--
Hooray!
Re: [O] [Feature Request] Configure timing format
Hi Nicolas, Thanks for your reply. But do you think it's possible to integrate it with other org-mode features that make use of the time stamps (such as the automatic overlays, calculation of total-time etc.)? If you want to know how I want to use it, this is my use-case: Use cases: -Using org-mode in a sports setting, often sets of an exercise take not more than for example 30 seconds. Rounding to minutes makes the registration useless. -Work efficiency improvement: sometimes it is handy to time minor small supporting tasks for a while (how much time does it take me to start an application and set everything ready to do major task X, etc), that you have to very often. Winning 30 seconds may not seem to be that much, but for a task you carry out in average lets say 2 times a day, this amounts to 365 minutes a year = 6 hours a year less work. If you can optimize 10 more of those tasks, well it is clear that you can add over a week of additional holiday that year. Regards, Koen van der Kruk 2015-03-15 9:20 GMT+01:00 Nicolas Goaziou : > Hello, > > Koen van der Kruk writes: > > > I am planning to add a new feature to orgmode, but I don't know if there > is > > already something like I described below. I am also wondering if someone > > could tell me how much time this is going to take. > > I have a little experience with orgmode and emacs, but still have to > learn > > a lot. > > > > Feature description: > > > > It currently is not possible to configure the timing format to the > > resolution you want. This project is about adding this feature to > org-mode. > > After implementation, it should be possible to chose any timing > resolution > > you want, ranging from precision to hours, quarters of an hour, seconds, > > milliseconds, etc. The only limitation should be the internal timing > > resolution of the operating system on which emacs runs. Moreover, all > > functions associated with time (such as automatic calculation of > durations > > etc. etc. overlays, should also continue to work correctly). Milliseconds > > may be overkill, but the point of this project is that it makes org-mode > > abstract from a fixed timing resolution, it should be fully > > configurable. > > I don't think timestamps to the millisecond or even the second belong to > the scope of this application. If you need this, I suggest to add > another syntax for it (e.g., like timers do), but I'm not convinced it > should go in core anyway. > > Real improvements over current timestamps would be to remove the limit > of internal timing resolution (e.g., be able to use time stamps before > 1970) and, even more importantly, support time zones. > > > Regards, > > -- > Nicolas Goaziou > -- Groeten, Koen
Re: [O] [ox, patch] #+SUBTITLE
Hi,
I've added a patch that address the code problems, but not the
documentation issues, as the solution is still unclear.
Nicolas Goaziou writes:
>> But de facto KEYWORDS and DESCRIPTION were also only supported in some
>> backends. I think it's more convenient to have these type of keywords in
>> one place. But I don't feel strongly about this.
>
> I would like to keep a clear and somewhat future-proof rule about this:
>
> 1. A keyword a user can expect to find in all back-ends where it makes
> sense should be defined in "ox.el". To put it differently, it can be
> considered as a bug if a back-end could /simply/ support a keyword
> in this category but doesn't. Keywords in this category are to be
> documented in (info "(org)Export settings").
>
> 2. Other keywords are defined in their respective back-end, and
> documented in their respective chapter in the manual.
>
> As a non-trivial example, consider :email. You can expect it to produce
> something sensible in any back-end. Yet, "ox-icalendar" doesn't use it.
> It still belongs to first category.
>
> If we support SUBTITLE everywhere it makes sense, it might be worth
> adding it to the first category. Actually, considering the rule above,
> I even lean towards adding it to that category. WDYT?
I think it's hard to make a clear-cut rule. I think keywords that are
well-supported by Org-core should be there. From a user perspective, I
think it should be close to TITLE. Further, putting it there also signal
to external writers, e.g. ox-reveal, that they should now try to support
it. I think SUBTITLE, KEYWORD, and DESCRIPTION is within the same
category and should be treated the same.
We could add a subsection with "text document properties" which are
keywords that are supported by the set: {ox-html, ox-ascii, ox-odt,
ox-latex}. These would be sort of 1½ class citizens.
We can't support SUBTITLE everywhere, 'cause it simply does not make sense
(only in "text document producers" IMO).
The support of SUBTITLE is:
W/Emacs: support is 6/9
W/Contrib: support is 8/20
- BTW: ox-groff seems to have some support for subtitles, but
I'm not sure how this works, so I haven't tried to unify
it.
- I guess it could be added to ox-rss could support it. Atom
seems to support subtitle, but it does not seem rss 2.0 has
it in its definition... I don't know the details of RSS
well.
W/"the wild": for all I know the limit of the fraction is zero.
> Also, I'm going to implement the `parse-object' and `parse-element'
> behaviour we discussed in another thread, and remove
> `org-element-document-properties' (and the relative
> `org-export-document-properties') altogether. This will remove a useless
> distinction among keywords: two categories are enough.
I think this sounds very cool. It will allow us to remove a lot of
"low-level" details from file with additional parsed keywords.
> As a side-effect, however, `org-element-context' will not show objects
> when called on TITLE and al, but that might be a good thing actually
> (there are objects in there only during export and only if considered
> export back-end makes use of them).
As mentioned, it's fine with me and nobody else complained so I think
there's no need to worry.
>>> (and formatted-subtitle ...)
>>
>> Can you explain why (and ⋯) should be used here?
>
> It makes more obvious you are expecting a return value. `when' is
> preferred for side effects. However, this is not a hard rule, since
Thanks for the example.
—Rasmus
--
Don't panic!!!
>From 1c2241e4d39a619b6123cb4e69c60dcec42534ee Mon Sep 17 00:00:00 2001
From: Rasmus
Date: Sun, 1 Mar 2015 22:09:19 +0100
Subject: [PATCH] ox: Add SUBTITLE property in some backends
* ox-ascii.el (org-ascii-template--document-title)
(org-ascii-template--document-title)
ox-deck.el (org-deck-title-slide-template)
ox-s5.el (org-s5-title-slide-template)
ox-html.el (org-html--build-meta-info, org-html-format-spec)
(org-html--build-meta-info, org-html-format-spec)
(org-html--build-meta-info, org-html-format-spec)
ox-org.el (org), (org-org-keyword): Use SUBTITLE.
* ox-beamer.el (org-beamer-template)
ox-html (org-html-template)
ox-latex.el (org-latex-template)
ox-org (org-org-template): Insert SUBTITLE.
* ox-html (org-html-preamble-format) (org-html-postamble-format):
Update docstring.
* ox-html (org-html-style-default): Add .subtitle style and
change .title style.
* ox-texinfo.el (org-texinfo-template): Interpret subtitle.
* org.texi (Export settings): Document SUBTITLE.
* ORG-NEWS: Add entry on SUBTITLE.
The patch adds a #+SUBTITLE keyword to ox-ascii, ox-latex, ox-html and
ox-odt.
---
contrib/lisp/ox-deck.el | 7 +++
contrib/lisp/ox-s5.el | 7 +++
doc/org.texi| 11 ++-
etc/ORG-NEWS| 3 +++
lisp/ox-ascii.el| 22 +-
lisp/ox-beamer.el |
Re: [O] [bug] orgstruct++-mode breaks backward-sentence
Rasmus writes: > Forget about fill-paragraph. Try this with test-org as nil and non-nil: > > (let ((test-org nil)) > (switch-to-buffer "test.org") > (if test-org (org-mode) (text-mode)) > (erase-buffer) > (insert "1. foo bar\n baz") > (backward-sentence)) > > When the buffer is in org-mode backward sentence behaves differently from > when it's in text-mode. I think text-mode behaves correctly. This should be fixed in 98ec17e204689f415200a2930fc148bf6a4dfe49. Thank you. Regards,
Re: [O] [ox, patch] Keywords & what should go in ox?
Nicolas Goaziou writes: > Rasmus writes: > >> By this logic we'd have to add *every* "global" keyword, no? Does it make >> sense? > > Every global (as in "ox.el") keyword should be documented there, indeed. For now I have not moved the documentation as I'm not sure we know where to put it yet. >> So should I go ahead a kill KEYWORD and DESCRIPTION in ox? > > IIUC, this is what we agreed on in the related thread. This is pushed now in 79c0aa21ca2657f2ea7272040bce3ff4754bab1b. —Rasmus -- Evidence suggests Snowden used a powerful tool called monospaced fonts
Re: [O] [ox, patch] #+SUBTITLE
Rasmus writes:
> Nicolas Goaziou writes:
>
>> I would like to keep a clear and somewhat future-proof rule about this:
>>
>> 1. A keyword a user can expect to find in all back-ends where it makes
>> sense should be defined in "ox.el". To put it differently, it can be
>> considered as a bug if a back-end could /simply/ support a keyword
>> in this category but doesn't. Keywords in this category are to be
>> documented in (info "(org)Export settings").
I would add that, to be in that category, a keyword needs to be
supported by at least 3 major back-ends (among ASCII, HTML, ODT and
LaTeX).
>> 2. Other keywords are defined in their respective back-end, and
>> documented in their respective chapter in the manual.
>>
>> As a non-trivial example, consider :email. You can expect it to produce
>> something sensible in any back-end. Yet, "ox-icalendar" doesn't use it.
>> It still belongs to first category.
>>
>> If we support SUBTITLE everywhere it makes sense, it might be worth
>> adding it to the first category. Actually, considering the rule above,
>> I even lean towards adding it to that category. WDYT?
>
> I think it's hard to make a clear-cut rule.
The rule above is good enough to make a decision in most cases, IMO.
> I think keywords that are well-supported by Org-core should be there.
That doesn't contradict category 1.
> From a user perspective, I think it should be close to TITLE. Further,
> putting it there also signal to external writers, e.g. ox-reveal, that
> they should now try to support it. I think SUBTITLE, KEYWORD, and
> DESCRIPTION is within the same category and should be treated the
> same.
Do you mean KEYWORD and DESCRIPTION should also belong to category 1?
I'm not against it, but then, back-ends are required to support them
whenever possible.
> We could add a subsection with "text document properties" which are
> keywords that are supported by the set: {ox-html, ox-ascii, ox-odt,
> ox-latex}. These would be sort of 1½ class citizens.
I don't want to create a third category (à la
`org-element-document-properties', which I'm trying to remove).
> We can't support SUBTITLE everywhere, 'cause it simply does not make sense
> (only in "text document producers" IMO).
That doesn't contradict category 1 either, as shown by EMAIL example.
> The support of SUBTITLE is:
>
> W/Emacs: support is 6/9
That's fine as there is no simple way to support SUBTITLE in the
3 back-ends left. Also, the "big four" support it.
> W/Contrib: support is 8/20
> - BTW: ox-groff seems to have some support for subtitles, but
>I'm not sure how this works, so I haven't tried to unify
>it.
> - I guess it could be added to ox-rss could support it. Atom
>seems to support subtitle, but it does not seem rss 2.0 has
>it in its definition... I don't know the details of RSS
>well.
>
> W/"the wild": for all I know the limit of the fraction is zero.
We are not maintaining the former and have no control over the latter,
so it doesn't matter.
Regards,
Re: [O] [ox, patch] #+SUBTITLE
Nicolas Goaziou writes:
>>> I would like to keep a clear and somewhat future-proof rule about this:
>>>
>>> 1. A keyword a user can expect to find in all back-ends where it makes
>>> sense should be defined in "ox.el". To put it differently, it can be
>>> considered as a bug if a back-end could /simply/ support a keyword
>>> in this category but doesn't. Keywords in this category are to be
>>> documented in (info "(org)Export settings").
>
> I would add that, to be in that category, a keyword needs to be
> supported by at least 3 major back-ends (among ASCII, HTML, ODT and
> LaTeX).
That's simple enough and easy to test.
>> From a user perspective, I think it should be close to TITLE. Further,
>> putting it there also signal to external writers, e.g. ox-reveal, that
>> they should now try to support it. I think SUBTITLE, KEYWORD, and
>> DESCRIPTION is within the same category and should be treated the
>> same.
>
> Do you mean KEYWORD and DESCRIPTION should also belong to category 1?
> I'm not against it, but then, back-ends are required to support them
> whenever possible.
At the moment they are. They lack ascii support, but at least keywords
should be supported in ascii eventually IMO (but that's another thread).
So I would keep them. The documentation explicitly states which backend
these keywords are supported by.
>> We could add a subsection with "text document properties" which are
>> keywords that are supported by the set: {ox-html, ox-ascii, ox-odt,
>> ox-latex}. These would be sort of 1½ class citizens.
>
> I don't want to create a third category (à la
> `org-element-document-properties', which I'm trying to remove).
This category would not exists in the code. It would simply be a
classification that exists in the manual. I would be a hack to not
maintain "no. of backend that support SOME_KEYWORD" different places to
maintain documentation for SOME_KEYWORD.
Anyway, the above is fine so let's use that.
—Rasmus
--
Summon the Mothership!
[O] position option of tabular in latex export
Is it possible to specify a pos option to the tabular environment used
when exporting a table in latex. Some problems I have with tabular in
block environments (when exporting to beamer) would be fixed with:
--8<---cut here---start->8---
\begin{tabular}[t]{ll}
\hline
item & item
\hline
\end{tabular}--8<---cut here---end--->8---
instead of:
--8<---cut here---start->8---
\begin{tabular}{ll}
\hline
item & item
\hline
\end{tabular}
--8<---cut here---end--->8---
Julien.
[O] patch for BIDI support for org-mime.el
Hello
Attached you find a very small patch which adds BIDI support to org-mime.el
basically it adds
"\n
"
instead of simply
"")
To the htmlized message.
A new variable is introduced, namely:
org-mime-bidi-support which is per default set to nil.
I turn it on when switching to a BIDI language, as in the following function.
(defun my-turn-bidi-on ()
"Just start with to R2L and turn the hebrew (qwerty) keyboard on"
(interactive)
(setq bidi-paragraph-direction 'right-to-left)
(set-face-font 'default "-etl-*-*-*-*-*-*-240-*-*-*-*-ISO8859-8")
(setq org-mime-bidi-support t)
(set-input-method "hebrew-phonetic-qwerty" t)
(message "R2L on and the hebrew qwerty keyboard!"))
On off when switching back.
Regards
Uwe Brauer
diff -u /home/oub/.emacs.d/elpa/org-plus-contrib-20130703/org-mime-org.el /home/oub/.emacs.d/elpa/org-plus-contrib-20130703/org-mime.el
--- /home/oub/.emacs.d/elpa/org-plus-contrib-20130703/org-mime-org.el 2015-03-13 20:14:17.0 +0100
+++ /home/oub/.emacs.d/elpa/org-plus-contrib-20130703/org-mime.el 2015-03-29 18:55:08.733572911 +0200
@@ -147,6 +147,12 @@
(buffer-string)
('vm "?")))
+(defvar org-mime-bidi-support nil
+ "*Variable which controls the support for RTL BIDI. Default is
+ nil. It is recommendable to change this variable, once you
+ change, via `set-input-method' to a BIDI language.")
+
+
(defun org-mime-multipart (plain html &optional images)
"Markup a multipart/alternative with text/plain and text/html alternatives.
If the html portion of the message includes images wrap the html
@@ -155,10 +161,12 @@
('mml (concat "<#multipart type=alternative><#part type=text/plain>"
plain
(when images "<#multipart type=related>")
- "<#part type=text/html>"
+ (if org-mime-bidi-support ;add BIDI support
+ "<#part type=text/html>\n"
+ "<#part type=text/html>")
html
images
- (when images "<#/multipart>\n")
+ (when images "\n<#/multipart>\n")
"<#/multipart>\n"))
('semi (concat
"--" "<>-{\n"
Diff finished. Sun Mar 29 18:55:27 2015
Re: [O] org-drill problem: questions are blank
Peter Westlake writes: > On Thu, 26 Mar 2015, at 17:26, J. David Boyd wrote: >> Peter Westlake writes: >> >> > From time to time Org-drill shows me a blank window instead of a >> > question. The frame, mode line and prompt to answer are visible, but >> > there's nothing in the window at all. As a workaround I can type "t" to >> > edit the tags, and the question will appear. >> > >> > A sample file is enclosed. It's a new file without any of the org-drill >> > property drawers just to keep the example short and to avoid having to >> > wait for the question to be scheduled to be shown again, but the problem >> > *does* still happen when the drawers are present. >> > >> > To reproduce the bug, run org-drill in drillbug.org; the question "MC" >> > gives a blank screen. >> > >> > I'm using org-drill with the latest version of Org-mode, git commit >> > 2f58e3c011ec84f621905332d8df68b83da580d9, on Emacs 24.3.1, 2014-09-30. >> > >> > Peter. >> >> There's no attached file... > > Ugh! There is now, sorry. Thanks! I can reproduce your issue with a relatively fresh emacs 25 and org from git. AFAICS the window gets blanked sometimes in function org-toggle-latex-fragment of org.el in line --8<---cut here---start->8--- ;; Work around a bug that doesn't restore window's start ;; when widening back the buffer. (set-window-start nil window-start) --8<---cut here---end--->8--- A workaround would be to comment out just this line. I don't know if this is a reliable fix though. HTH -- http://www.wahlzone.de GPG: 0x49010A040A3AE6F2
Re: [O] patch for BIDI support for org-mime.el
Thank you Uwe. I've actually settled on vimwiki but I glance at orgmode every now and then. This might get me to switch. Have a great week! On Sun, Mar 29, 2015 at 8:00 PM, Uwe Brauer wrote: > Hello > > Attached you find a very small patch which adds BIDI support to org-mime.el > basically it adds > " > \n " instead of simply " > ") To the htmlized message. A new variable is introduced, namely: > org-mime-bidi-support which is per default set to nil. I turn it on when > switching to a BIDI language, as in the following function. (defun > my-turn-bidi-on () "Just start with to R2L and turn the hebrew (qwerty) > keyboard on" (interactive) (setq bidi-paragraph-direction 'right-to-left) > (set-face-font 'default "-etl-*-*-*-*-*-*-240-*-*-*-*-ISO8859-8") (setq > org-mime-bidi-support t) (set-input-method "hebrew-phonetic-qwerty" t) > (message "R2L on and the hebrew qwerty keyboard!")) On off when switching > back. Regards Uwe Brauer -- Dotan Cohen http://gibberish.co.il http://what-is-what.com
[O] [RFC] Repeat Heading movement commands
Hi List, I often find myself wanting to move up by several headings: C-c C-p, C-c C-p, C-c C-p... (I don't usually know ahead of time how many I want to move, so I can't use a numeric prefix arg) I like how `set-mark-command' works with non-nil `set-mark-repeat-pop' to avoid the need to repeat a prefix key and wanted to try something similar for C-p. I came up with the following: (define-key org-mode-map (kbd "C-p") (lambda (arg) (interactive "p") (if (not (eq last-command 'org-previous-visible-heading)) (previous-line arg) (org-previous-visible-heading arg) (setq this-command 'org-previous-visible-heading So now I can do: C-c C-p, C-p, C-p... And repeatedly move by headlines. This (with a similar definition for C-n) is working well for me. If I fleshed this out into a patch with a defcustom to control the behavior, might it be applied? Or is this too far in the weeds of individual user preference to warrant modifying org.el? Thanks for any comments. Regards, Jake
[O] Bug: Proposed new version of ob-C.el [8.3beta (release_8.3beta-944-g830cf3 @ /Users/snapp/.emacs.d/vendor/org/)]
I must admit I am not a fan of the proposed changes to ob-C.el which seem to
insert
#include
#include
#include
during a tangle operation, without option. Currently, I am using C mode to
tangle source written in GLSL (OpenGL shading language), which is syntactically
similar to C. However the inclusion of the three includes triggers an error
when the tangled GLSL files are compiled by OpenGL. I would appreciate if you
either required users to specify each included header file in the #+src_begin
line, or provide an option to suppress the three include statements described
above. Alternatively, one could tangle GLSL files with the extensions (.glsl,
.vert, and .frag) like C files without inserting any unrequested "#include"
statements.
Thank you for your consideration.
Robert Snapp
==
Emacs : GNU Emacs 24.4.1 (x86_64-apple-darwin14.0.0)
of 2014-11-19 on tenten-slave.macports.org
Package: Org-mode version 8.3beta (release_8.3beta-944-g830cf3 @
/Users/snapp/.emacs.d/vendor/org/)
current state:
==
(setq
org-hide-leading-stars t
org-tab-first-hook '(org-hide-block-toggle-maybe
org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-mobile-files '("~/org/journal.org" "~/org/dates.org" "~/org/todo.org"
"~/org/projects/")
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-log-done 'time
org-latex-minted-options '(("frame" "lines") ("fontsize" "\\scriptsize")
("bgcolor" "WhiteSmoke"))
org-src-window-setup 'current-window
org-latex-format-inlinetask-function
'org-latex-format-inlinetask-default-function
org-confirm-shell-link-function 'yes-or-no-p
org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
org-latex-pdf-process '("pdflatex -shell-escape -interaction nonstopmode
-output-directory %o %f" "bibtex %b" "pdflatex -shell-escape -interaction
nonstopmode -output-directory %o\
%f" "pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f")
org-latex-format-headline-function 'org-latex-format-headline-default-function
org-default-notes-file "~/org//notes.org"
org-todo-keyword-faces '(("TODO" :foreground "red" :weight bold)
("WAITING" :foreground "orange" :weight bold)
("CANCELLED" :foreground "purple" :weight bold)
("DONE" :foreground "forest green" :weight bold)
("FIXME" :foreground "red" :weight bold)
("FIXED" :foreground "forest green" :weight bold))
org-capture-templates '(("t" "Todo" entry (file+headline "~/org/todo.org"
"Tasks")
"* TODO %?\n %i\n %a")
("j" "Journal" entry (file+datetree
"~/org/journal.org")
"* %U %? %^g\n %i\n %a")
("n" "Notes" entry (file+headline "~/org/notes.org"
"Unfiled")
"* %?\n %i\n %a")
("p" "Password" entry (file "~/org/sites.gpg")
"* %^{Account Name}\n %i\n
%[~/org/templates/password.txt]")
)
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 "\\"
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 before-save-hook org-encrypt-entries nil t] 5]
turn-on-visual-line-mode er/add-org-mode-expansions
#[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
#[nil "\300\301!\207" [run-hooks prelude-org-mode-hook] 2]
org-journal-update-auto-mode-alist)
org-refile-targets '((nil :maxlevel . 1) (org-agenda-files :maxlevel . 1))
org-archive-hook '(org-attach-archive-delete-maybe)
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 "~/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-a
Re: [O] ob-lilypond
Hey all,
looks like I’m having quite a few problems with ob-lilypond (Org-mode version
8.2.7b). To ensure that my setup is correct I ran the tests mentioned on
http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html#sec-9:
M-x load-file RET
~/path/to/current/org-mode-git-repository/testing/lisp/test-ob-lilypond.el
M-x ert RET RET
And this is what I got (short version):
Selector: t
Passed: 6
Failed: 36 (36 unexpected)
Total: 42/42
Started at: 2015-03-25 13:32:19+0100
Finished.
Finished at: 2015-03-25 13:32:19+0100
...FFF…F
Am I missing something? How can I get this to work?
Thanks for any help!
patrick
Error message (long version):
Selector: t
Passed: 6
Failed: 36 (36 unexpected)
Total: 42/42
Started at: 2015-03-25 13:32:19+0100
Finished.
Finished at: 2015-03-25 13:32:19+0100
...FFF...F
F ob-lilypond/ly-arrange-mode
(ert-test-failed
((should
(boundp 'org-babel-lilypond-arrange-mode))
:form
(boundp org-babel-lilypond-arrange-mode)
:value nil))
F ob-lilypond/ly-attempt-to-open-pdf
(void-variable org-babel-lilypond-display-pdf-post-tangle)
F ob-lilypond/ly-attempt-to-play-midi
(void-variable org-babel-lilypond-play-midi-post-tangle)
F ob-lilypond/ly-check-for-compile-error
(void-function org-babel-lilypond-check-for-compile-error)
F ob-lilypond/ly-command-ly/bound
(ert-test-failed
((should
(boundp 'org-babel-lilypond-ly-command))
:form
(boundp org-babel-lilypond-ly-command)
:value nil))
F ob-lilypond/ly-command-ly/stringp
(void-variable org-babel-lilypond-ly-command)
F ob-lilypond/ly-command-midi/bound
(ert-test-failed
((should
(boundp 'org-babel-lilypond-midi-command))
:form
(boundp org-babel-lilypond-midi-command)
:value nil))
F ob-lilypond/ly-command-midi/stringp
(void-variable org-babel-lilypond-midi-command)
F ob-lilypond/ly-command-pdf/bound
(ert-test-failed
((should
(boundp 'org-babel-lilypond-pdf-command))
:form
(boundp org-babel-lilypond-pdf-command)
:value nil))
F ob-lilypond/ly-command-pdf/stringp
(void-variable org-babel-lilypond-pdf-command)
F ob-lilypond/ly-commands/customize
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "nonsense" "bla" "fasel")))
:form
(equal
(nil nil nil)
("nonsense" "bla" "fasel"))
:value nil :explanation
(list-elt 0
(different-types nil "nonsense"
F ob-lilypond/ly-commands/darwin
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "/Applications/lilypond.app/Contents/Resources/bin/lilypond"
"open" "open")))
:form
(equal
(nil nil nil)
("/Applications/lilypond.app/Contents/Resources/bin/lilypond" "open"
"open"))
:value nil :explanation
(list-elt 0
(different-types nil
"/Applications/lilypond.app/Contents/Resources/bin/lilypond"
F ob-lilypond/ly-commands/other
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "lilypond" "xdg-open" "xdg-open")))
:form
(equal
(nil nil nil)
("lilypond" "xdg-open" "xdg-open"))
:value nil :explanation
(list-elt 0
(different-types nil "lilypond"
F ob-lilypond/ly-commands/windows-nt
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "lilypond" "" "")))
:form
(equal
(nil nil nil)
("lilypond" "" ""))
:value nil :explanation
(list-elt 0
(different-types nil "lilypond"
F ob-lilypond/ly-compile-lilyfile
(void-variable org-babel-lilypond-ly-command)
F ob-lilypond/ly-compile-post-tangle
(ert-test-failed
((should
(boundp 'org-babel-lilypond-compile-post-tangle))
:form
(boundp org-babel-lilypond-compile-post-tangle)
:value nil))
F ob-lilypond/ly-display-pdf-post-tangle
(ert-test-failed
((should
(boundp 'org-babel-lilypond-display-pdf-post-tangle))
:form
(boundp org-babel-lilypond-display-pdf-post-tangle)
:value nil))
F ob-lilypond/ly-gen-html
(ert-test-failed
((should
(boundp 'org-babel-lilypond-gen-pdf))
:form
(boundp org-babel-lilypond-gen-pdf)
:value nil))
F ob-lilypond/ly-gen-png
(ert-test-failed
((should
(boundp 'org-babel-lilypond-gen-png))
:form
(boundp org-babel-lilypond-gen-png)
:value nil))
F ob-lilypond/ly-gen-svg
(ert-t
[O] ob-lilypond
Hey all,
looks like I’m having quite a few problems with ob-lilypond (Org-mode version
8.2.7b). To ensure that my setup is correct I ran the tests mentioned on
http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html#sec-9:
M-x load-file RET
~/path/to/current/org-mode-git-repository/testing/lisp/test-ob-lilypond.el
M-x ert RET RET
And this is what I got (short version):
Selector: t
Passed: 6
Failed: 36 (36 unexpected)
Total: 42/42
Started at: 2015-03-25 13:32:19+0100
Finished.
Finished at: 2015-03-25 13:32:19+0100
...FFF…F
Am I missing something?
Thanks for any help!
patrick
Error message (long version):
Selector: t
Passed: 6
Failed: 36 (36 unexpected)
Total: 42/42
Started at: 2015-03-25 13:32:19+0100
Finished.
Finished at: 2015-03-25 13:32:19+0100
...FFF...F
F ob-lilypond/ly-arrange-mode
(ert-test-failed
((should
(boundp 'org-babel-lilypond-arrange-mode))
:form
(boundp org-babel-lilypond-arrange-mode)
:value nil))
F ob-lilypond/ly-attempt-to-open-pdf
(void-variable org-babel-lilypond-display-pdf-post-tangle)
F ob-lilypond/ly-attempt-to-play-midi
(void-variable org-babel-lilypond-play-midi-post-tangle)
F ob-lilypond/ly-check-for-compile-error
(void-function org-babel-lilypond-check-for-compile-error)
F ob-lilypond/ly-command-ly/bound
(ert-test-failed
((should
(boundp 'org-babel-lilypond-ly-command))
:form
(boundp org-babel-lilypond-ly-command)
:value nil))
F ob-lilypond/ly-command-ly/stringp
(void-variable org-babel-lilypond-ly-command)
F ob-lilypond/ly-command-midi/bound
(ert-test-failed
((should
(boundp 'org-babel-lilypond-midi-command))
:form
(boundp org-babel-lilypond-midi-command)
:value nil))
F ob-lilypond/ly-command-midi/stringp
(void-variable org-babel-lilypond-midi-command)
F ob-lilypond/ly-command-pdf/bound
(ert-test-failed
((should
(boundp 'org-babel-lilypond-pdf-command))
:form
(boundp org-babel-lilypond-pdf-command)
:value nil))
F ob-lilypond/ly-command-pdf/stringp
(void-variable org-babel-lilypond-pdf-command)
F ob-lilypond/ly-commands/customize
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "nonsense" "bla" "fasel")))
:form
(equal
(nil nil nil)
("nonsense" "bla" "fasel"))
:value nil :explanation
(list-elt 0
(different-types nil "nonsense"
F ob-lilypond/ly-commands/darwin
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "/Applications/lilypond.app/Contents/Resources/bin/lilypond"
"open" "open")))
:form
(equal
(nil nil nil)
("/Applications/lilypond.app/Contents/Resources/bin/lilypond" "open"
"open"))
:value nil :explanation
(list-elt 0
(different-types nil
"/Applications/lilypond.app/Contents/Resources/bin/lilypond"
F ob-lilypond/ly-commands/other
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "lilypond" "xdg-open" "xdg-open")))
:form
(equal
(nil nil nil)
("lilypond" "xdg-open" "xdg-open"))
:value nil :explanation
(list-elt 0
(different-types nil "lilypond"
F ob-lilypond/ly-commands/windows-nt
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "lilypond" "" "")))
:form
(equal
(nil nil nil)
("lilypond" "" ""))
:value nil :explanation
(list-elt 0
(different-types nil "lilypond"
F ob-lilypond/ly-compile-lilyfile
(void-variable org-babel-lilypond-ly-command)
F ob-lilypond/ly-compile-post-tangle
(ert-test-failed
((should
(boundp 'org-babel-lilypond-compile-post-tangle))
:form
(boundp org-babel-lilypond-compile-post-tangle)
:value nil))
F ob-lilypond/ly-display-pdf-post-tangle
(ert-test-failed
((should
(boundp 'org-babel-lilypond-display-pdf-post-tangle))
:form
(boundp org-babel-lilypond-display-pdf-post-tangle)
:value nil))
F ob-lilypond/ly-gen-html
(ert-test-failed
((should
(boundp 'org-babel-lilypond-gen-pdf))
:form
(boundp org-babel-lilypond-gen-pdf)
:value nil))
F ob-lilypond/ly-gen-png
(ert-test-failed
((should
(boundp 'org-babel-lilypond-gen-png))
:form
(boundp org-babel-lilypond-gen-png)
:value nil))
F ob-lilypond/ly-gen-svg
(ert-test-failed
((should
Re: [O] [RFC] Repeat Heading movement commands
Jacob Gerlach wrote: > Hi List, > > I often find myself wanting to move up by several headings: > > C-c C-p, C-c C-p, C-c C-p... > (I don't usually know ahead of time how many I want to move, so I > can't use a numeric prefix arg) > > I like how `set-mark-command' works with non-nil `set-mark-repeat-pop' > to avoid the need to repeat a prefix key and wanted to try something > similar for C-p. I came up with the following: > > (define-key org-mode-map > (kbd "C-p") > (lambda (arg) >(interactive "p") >(if (not (eq last-command 'org-previous-visible-heading)) >(previous-line arg) > (org-previous-visible-heading arg) > (setq this-command 'org-previous-visible-heading > > So now I can do: > C-c C-p, C-p, C-p... > And repeatedly move by headlines. With org-use-speed-commands set to t, this could be "C-c C-p p p". -- Kyle
[O] statistical operations with org-mode?
After having read through the org-mode info on spreadsheets several times and having also read through the calc info a few times I have not ben able to get pstdev() to produce anything but errors. Having checked over the data in a table, I found a couple instances where data values were missing so I expect this could account for the errors by itself. In column 3 I put the formula =pstdev(@<..@>) and also tried with =pstdev($3). What is the correct syntax? I wasn't sure which if any would work after having done all of that reading. -- Twitter: JudeDaShiell
Re: [O] [RFC] Repeat Heading movement commands
This kind of repeated command seems to be a good application for hydra. On Sunday, March 29, 2015, Kyle Meyer wrote: > Jacob Gerlach > wrote: > > Hi List, > > > > I often find myself wanting to move up by several headings: > > > > C-c C-p, C-c C-p, C-c C-p... > > (I don't usually know ahead of time how many I want to move, so I > > can't use a numeric prefix arg) > > > > I like how `set-mark-command' works with non-nil `set-mark-repeat-pop' > > to avoid the need to repeat a prefix key and wanted to try something > > similar for C-p. I came up with the following: > > > > (define-key org-mode-map > > (kbd "C-p") > > (lambda (arg) > >(interactive "p") > >(if (not (eq last-command 'org-previous-visible-heading)) > >(previous-line arg) > > (org-previous-visible-heading arg) > > (setq this-command 'org-previous-visible-heading > > > > So now I can do: > > C-c C-p, C-p, C-p... > > And repeatedly move by headlines. > > With org-use-speed-commands set to t, this could be "C-c C-p p p". > > -- > Kyle > > -- John --- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] [RFC] Repeat Heading movement commands
John Kitchin wrote:
> This kind of repeated command seems to be a good application for
> hydra.
True. Basic navigation could be set up with something like this:
#+begin_src elisp
(defhydra hydra-org-navigation ()
"Org navigation"
("p" org-previous-visible-heading "previous heading")
("n" org-next-visible-heading "next heading")
("f" org-forward-heading-same-level "forward heading")
("b" org-backward-heading-same-level "backward heading")
("u" outline-up-heading "up heading")
("q" nil "cancel"))
#+end_src
--
Kyle
Re: [O] Bug: Proposed new version of ob-C.el [8.3beta (release_8.3beta-944-g830cf3 @ /Users/snapp/.emacs.d/vendor/org/)]
Hi Robert Those #includes were a proposal I did long ago. The purpose was to make short scripts even shorter with default #includes that everybody uses. Your use-case is worth considering. If this cause trouble, it is easy to remove the includes. To keep existing scripts working, an :includes parameter would be required, like this: #+BEGIN_SRC C++ :includes // C++ script #+END_SRC Does everyone agree with this change? Regards Thierry Le 25/03/2015 03:28, Robert Snapp a écrit : > I must admit I am not a fan of the proposed changes to ob-C.el which seem to > insert > > #include > #include > #include > > during a tangle operation, without option. Currently, I am using C mode to > tangle source written in GLSL (OpenGL shading language), which is > syntactically similar to C. However the inclusion of the three includes > triggers an error when the tangled GLSL files are compiled by OpenGL. I would > appreciate if you either required users to specify each included header file > in the #+src_begin line, or provide an option to suppress the three include > statements described above. Alternatively, one could tangle GLSL files with > the extensions (.glsl, .vert, and .frag) like C files without inserting any > unrequested "#include" statements. > > Thank you for your consideration. > Robert Snapp > >
Re: [O] statistical operations with org-mode?
Jude DaShiell writes: > After having read through the org-mode info on spreadsheets several > times and having also read through the calc info a few times I have > not ben able to get pstdev() to produce anything but errors. Having > checked over the data in a table, I found a couple instances where > data values were missing so I expect this could account for the errors > by itself. In column 3 I put the formula =pstdev(@<..@>) and also > tried with =pstdev($3). What is the correct syntax? I wasn't sure > which if any would work after having done all of that reading. > AFAIK, the sample standard deviation calc function for a vector is called vsdev and the population standard deviation is called vpsdev. Here is an example of calling them (as well as the vmean and vmedian functions): --8<---cut here---start->8--- * Calculate stats on a column | seqno | value || |---++| | 1 | 0.34437004 | 0.49622740 | | 2 | 0.65321163 | 0.49569043 | | 3 | 0.17841555 | 0.22716774 | | 4 | 0.28259230 || | 5 | 0.88476454 || | 6 | 0.65279340 || | 7 | 0.12817118 || | 8 | 0.50326488 || | 9 | 0.34985056 || |10 | 0.78586253 || |11 | 0.49569043 || |12 | 0.46154064 || |13 | 0.65004499 || |14 | 0.74102345 || |15 | 0.33181485 || #+TBLFM: @2$3 = vmean(@2$2..@>$2) :: @3$3 = vmedian(@2$2..@>$2) :: @4$3 = vsdev(@2$2..@>$2) :: @5$3 = vpsdev(@2$2..@>$2) --8<---cut here---end--->8--- HTH. -- Nick
Re: [O] ob-lilypond
pls writes: > Hey all, > > looks like I’m having quite a few problems with ob-lilypond (Org-mode version > 8.2.7b). > To ensure that my setup is correct I ran the tests mentioned on > http://orgmode.org/worg > /org-contrib/babel/languages/ob-doc-lilypond.html#sec-9: > > M-x load-file RET ~/path/to/current/org-mode-git-repository/testing/lisp/ > test-ob-lilypond.el > M-x ert RET RET > > And this is what I got (short version): > > Selector: t > Passed: 6 > Failed: 36 (36 unexpected) > Total: 42/42 > > Started at: 2015-03-25 13:32:19+0100 > Finished. > Finished at: 2015-03-25 13:32:19+0100 > > ...FFF…F > > Am I missing something? How can I get this to work? > Probably missing a load-file: in addition to ob-lilypond.el and test-ob-lilypond.el, you need to load org-test.el (which is in the testing subdir of the git repo). With those three loaded (in addition to org-mode itself of course), all 42 tests pass in my setup: Org-mode version 8.3beta (release_8.3beta-882-gf8731e @ /home/nick/elisp/org-mode/lisp/) HTH, Nick
Re: [O] [RFC] Repeat Heading movement commands
John Kitchin writes: > This kind of repeated command seems to be a good application for hydra. Excuse me if this is a FAQ but: what's hydra ? -- Xavier.
Re: [O] [RFC] Repeat Heading movement commands
On 29 March 2015 at 23:43, Xavier Maillard wrote: > > John Kitchin writes: > >> This kind of repeated command seems to be a good application for hydra. > > Excuse me if this is a FAQ but: what's hydra ? https://github.com/abo-abo/hydra/ -- Suvayu Open source is the future. It sets us free.
Re: [O] [RFC] Repeat Heading movement commands
Xavier Maillard wrote: > John Kitchin writes: > >> This kind of repeated command seems to be a good application for hydra. > > Excuse me if this is a FAQ but: what's hydra ? Hydra [1] is a really nice package for creating keymaps that are similar to keymaps under a prefix key. Hydra has lots of little features, but two main advantages of using a hydra over a standard prefix key are that commands are repeatable with a single key and that a menu displays the key/command information. Have a look at hydra-examples.el [2] for some use cases. [1] https://github.com/abo-abo/hydra [2] https://github.com/abo-abo/hydra/blob/master/hydra-examples.el -- Kyle
Re: [O] [RFC] Repeat Heading movement commands
On Sun, Mar 29, 2015 at 4:05 PM, Kyle Meyer wrote: > With org-use-speed-commands set to t, this could be "C-c C-p p p". Well, this is much better. Should have thought to check the info, of course there's already something like this built in... On Sun, Mar 29, 2015 at 4:09 PM, John Kitchin wrote: > This kind of repeated command seems to be a good application for hydra. I suppose I'll stick with speed commands for org-mode, but hydra looks interesting. Thanks for the tips. Regards, Jake
[O] Capture Template Menus
What would be required to have Org-Mode support Capture Template
Menus? In Custom Agenda Views, it is possible to have a prefix
according to an example in the documentation:
https://www.gnu.org/software/emacs/manual/html_node/org/Storing-searches.html#Storing-searches
("hl" tags "+home+Lisa")
("hp" tags "+home+Peter")
("hk" tags "+home+Kim")))
But configuring custom capture templates with two-letter prefixes like
that doesn't work.
[O] Define org-capture-templates with variables via customize
Hello,
Given the fact I defvar'ed a custom variable holding a template of my
own:
#+BEGIN_SRC emacs-lisp
(defvar xma/org-task-with-effort-template "* TODO %^{Task}
%U
SCHEDULED: %^t
:PROPERTIES:
:Effort: %^{effort|1:00|0:30|0:05|0:15|2:00|3:00|4:00}
:END:
%?
%a
" "Une tache avec une duree d'effort")
#+END_SRC
How would you use that in a template declared via the customize UI ?
How to do the equivalent of this:
#+BEGIN_SRC emacs-lisp
(setq org-capture-templates `(("e" "Task with effort" entry
(file "~/Dropbox/refile.org")
,xma/org-task-with-effort-template)))
#+END_SRC
?
Thank you
-- Xavier.
[O] How to get inline python code to work with :session option?
:session doesn't seem to play well with inline code blocks. For example, if I
press C-c C-c with the cursor in the middle of the following inline code,
src_python[]{return 2+3}
it gets expanded to
src_python[]{return 2+3} {{{results(=5=)}}}
However, if I do the same with this code block,
src_python[:session]{return 2+3}
no results appear in the text buffer, and the mini-buffer displays the message
"Code block produced no output."
How can I get inline code to work with :session?
Thanks.
Richard Stanton
