Re: [O] imaxima babel
Hello Johnny, yggdra...@gmx.co.uk writes: > Many thanks for all the help! I have now figured out how to use maxima > from org-mode source blocks and display the results as pretty printed > equations online. To remember, I made a small summarising example file, > attached below for posteriority. This is very useful, thanks a lot. A couple comments and questions on your example file (which would be a nice addition to worg). It would be useful to know more about maxima and how to enable it with babel (a link to existing documentation, if there is any, would be great). In my setup, the previewing latex fragment keybinding is "C-c C-x C-l", not "C-c C-x C-x". I tried previewing the fragment, but I got the error: , | Failed to create dvi file from /var/folders/68/fvntfrw92y50gkk_67rkhsfwgn/T/orgtex16220cbr.tex ` Looking at the tex file and the log file, it seems that the tex files is to be processed by xelatex, but the command called seems to be pdfTeX. I probably have something misconfigured, but I don't know what it is. Any suggestion? Finally, and it's a nitpick: breaking lines in the middle of (info ...) links prevents following them using "C-x C-e". Thanks again, Alan
Re: [O] Opening an Org file slowed down
Hi Nicolas On Tue, Nov 26, 2013 at 11:19 PM, Nicolas Goaziou wrote: > So, it is a linear increase here. Have you disabled cache? No, but in the meantime I found accidentally how to get linear and bisected it to be related with how Org is loaded: 1) start GNU Emacs with -L pointing to Org and with -Q 2) choice: - for quadratic do: M-x org-mode - for linear do: M-x org-version 3) M-x elp-instrument-package RET org 4) C-x f 400.org 5) M-x elp-results GNU Emacs 24.3.1 and 24.3.2, Org unpatched and make uncompiled release_8.2.3c-291-gbe8a1a and today's release_8.2.3c-303-g5a2dabc. The same happens if in 1) I add my local patches for Org and all my customization which includes already some implicit level of loading Org. This is beyond my knowledge, can you reproduce it? Michael
[O] not handling failing sql statements in ob-sql.el with postgresql
Hi,
in case psql (version 9.1 and later) encounters a SQL error, e.g. a
syntax error, it doesn't exit with an error-code. Instead it
continues and exits with 0. This means that evaluating faulty SQL-code
in org-mode/babel leaves the user with no clue of why the result set is
empty.
I changed the code in ob-sql.el by adding the
--set="ON_ERROR_STOP-1"
command-line option to the psql command in order to make things work
correct. This option not only makes psql exit at the first error, it
also exits with a not 0 error-code.
line 125 and further of my ob-sql.el:
('postgresql (format
"psql --set=\"ON_ERROR_STOP=1\" -A -P footer=off -F \"\t\" -f %s -o
%s %s"
(org-babel-process-file-name in-file)
(org-babel-process-file-name out-file)
(or cmdline "")))
Is this a change worth applying? Or will it break things?
regards,
Joost
--
Snow B.V.http://snow.nl
[O] multiple agenda custom commands causes tag-filter-preset not to work?
Hi all,
consider the following configuration:
(setq org-agenda-custom-commands
'(("h" "home"
((agenda "" ((org-agenda-span 'day)
(org-agenda-tag-filter-preset '("-work"
(alltodo)
It appears that `org-agenda-tag-filter-preset' does not work when I define
multiple commands under one. The agenda is rendered as if filter was never
set.
On the other hand, if I remove `(alltodo)', thus defining only the agenda,
then
the filter works without problems.
Any ideas?
Regards,
Miro
Re: [O] multiple agenda custom commands causes tag-filter-preset not to work?
Forgot to mention. I'm using org-mode 8.2.2.
Regards,
Miro
On Wed, Nov 27, 2013 at 11:23 AM, Miro Bezjak wrote:
> Hi all,
>
> consider the following configuration:
>
>
> (setq org-agenda-custom-commands
> '(("h" "home"
> ((agenda "" ((org-agenda-span 'day)
> (org-agenda-tag-filter-preset '("-work"
> (alltodo)
>
>
> It appears that `org-agenda-tag-filter-preset' does not work when I define
> multiple commands under one. The agenda is rendered as if filter was never
> set.
>
> On the other hand, if I remove `(alltodo)', thus defining only the agenda,
> then
> the filter works without problems.
>
> Any ideas?
>
> Regards,
> Miro
>
Re: [O] org-contacts, multi-line properties, postal addresses
* Kyle Machulis wrote: > > Thought about maybe trying to extend AsynK with an org-contacts backend? > That'd be ridiculously useful. > http://karra-asynk.appspot.com/ This is a great suggestion, indeed. However, I do not have the urge to sync with Outlook, GCal, ... yet. So I pass on this one. -- 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] Opening an Org file slowed down
Hi Michael, Michael Brand writes: > 2) choice: >- for quadratic do: M-x org-mode >- for linear do: M-x org-version Can you show the output of M-: (insert (mapconcat #'car load-history "\n")) in each case ? It will output the list of loaded files, which hopefuly shows a difference. -- Nico.
Re: [O] Anniversaries from BBDB available to calendar and diary?
Hi Joseph, j...@ftfl.ca writes: > It makes sense to put birthdays and other anniversaries in BBDB as > described in section 10.3.1 of the Org manual. I wonder, did you look at the section of 10.3.1 titled "Anniversaries from BBDB"? > Why repeat information by putting it in the diary when you already > have a contact entry in BBDB for the person? The only problem with > this is that the anniversaries aren't marked in the calendar and don't > show up the diary. Is there away to make the calendar/diary aware of > anniversaries in BBDB? Myles
Re: [O] Org-mode issue with cyclic tasks and checkboxes
Hi Borja, I can't see that you have received a reply yet, which is unusual for this excellent list. borja.tarr...@gmail.com writes: > I am working with cyclic or repetitive tasks in org-mode, inside this task, > I have several checkboxes. So when I finished all the list, normally I put > the task as done, and new task with sublist of checkboxes is created for > the next cycle, however, those checkboxes appears as ticked and I think > should be unticked as it is new cycle task, e.g.: > > * TODO Cyclic monthly home [0/5] > SCHEDULED: <2013-11-30 Sat +1m> > - [ ] pay sauna > - [ ] pay electricity > - [ ] pay renting > - [ ] pay internet > - [ ] pay union > > Once I ticked all of them and put it as done, this is what I can see: > > * WIP Cyclic monthly home [5/5] > SCHEDULED: <2014-01-30 Thu +1m> > - State "DONE" from "WIP"[2013-11-06 Wed 20:49] > :PROPERTIES: > :LAST_REPEAT: [2013-11-06 Wed 20:49] > :END: > - [X] pay sauna <--- this should be unticked > - [X] pay electricity <-- this should be unticked > - [X] pay renting <-- this should be unticked > - [X] pay internet <-- this should be unticked > - [X] pay union <-- this should be unticked > > Am I missing something? or is some bug that should be fixed? May be use this: ;; uncheck tick boxes --- (require 'org-checklist) (defun my-uncheck-ticks() "Uncheck tick boxes in the TODO item when state is changed to DONE" ( when (and (string= org-state "DONE") (org-get-repeat)) (org-reset-checkbox-state-subtree))) (add-hook 'org-after-todo-state-change-hook 'my-uncheck-ticks) > I am using those versions: > > Emacs version: > GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll bars) > of 2013-08-30 on apocalipsis > > Org-mode version: > Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ > /usr/local/share/emacs/24.3/lisp/org/) Org 8 is out, may be time to upgrade? Myles
Re: [O] Split source block at point
C-h K C-c C-v C-d Alexander Baier writes: > Hello together, > > is therer a command or a function that lets me split a source block at a > given position? I think what I mean is best demonstrated by looking at > an example: > > Given this buffer: > > begin_src emacs-lisp > (defun foo () > (bar)) > > (baz (foo)) > end_src > > > With point somewhere at the free line I want to invoke the split > function and get this: > > begin_src emacs-lisp > (defun foo () > (bar)) > end_src > > begin_src emacs-lisp > (baz (foo)) > end_src > > This is similar to what M-RET does in message-mode. > > Do we already have something like this in org? And if not, do you think > this is useful? Personally I find myself quite frequently splitting up > soure blocks manually. > > Best regards, > -- > Alexander Baier
Re: [O] Split source block at point
Jambunathan K writes: > C-h K C-c C-v C-d ^ ^ k Looks like the keybindings are not indexed the canonical way in the Org manual. > Alexander Baier writes: > >> Hello together, >> >> is therer a command or a function that lets me split a source block at a >> given position? I think what I mean is best demonstrated by looking at >> an example: >> >> Given this buffer: >> >> begin_src emacs-lisp >> (defun foo () >> (bar)) >> >> (baz (foo)) >> end_src >> >> >> With point somewhere at the free line I want to invoke the split >> function and get this: >> >> begin_src emacs-lisp >> (defun foo () >> (bar)) >> end_src >> >> begin_src emacs-lisp >> (baz (foo)) >> end_src >> >> This is similar to what M-RET does in message-mode. >> >> Do we already have something like this in org? And if not, do you think >> this is useful? Personally I find myself quite frequently splitting up >> soure blocks manually. >> >> Best regards, >> -- >> Alexander Baier
Re: [O] Org-mode issue with cyclic tasks and checkboxes
Thanks for answer. I already got another answer from stackoverflow, where I ask exactly the same question, is here: http://stackoverflow.com/questions/20164918/how-to-untick-checkboxes-in-org-mode-for-the-next-cyclic-repetitive-task But basically the solution it was include this: :PROPERTIES: :RESET_CHECK_BOXES: t :END: and of course (require 'org-checklist) should be included in .emacs configuration file. Again, thanks for the answer. Regards, Borja Tarraso 2013/11/16 Borja Tarraso > Hi, > > I am working with cyclic or repetitive tasks in org-mode, inside this > task, I have several checkboxes. So when I finished all the list, normally > I put the task as done, and new task with sublist of checkboxes is created > for the next cycle, however, those checkboxes appears as ticked and I think > should be unticked as it is new cycle task, e.g.: > > * TODO Cyclic monthly home [0/5] > SCHEDULED: <2013-11-30 Sat +1m> > - [ ] pay sauna > - [ ] pay electricity > - [ ] pay renting > - [ ] pay internet > - [ ] pay union > > Once I ticked all of them and put it as done, this is what I can see: > > * WIP Cyclic monthly home [5/5] > SCHEDULED: <2014-01-30 Thu +1m> > - State "DONE" from "WIP"[2013-11-06 Wed 20:49] > :PROPERTIES: > :LAST_REPEAT: [2013-11-06 Wed 20:49] > :END: > - [X] pay sauna <--- this should be unticked > - [X] pay electricity <-- this should be unticked > - [X] pay renting <-- this should be unticked > - [X] pay internet <-- this should be unticked > - [X] pay union <-- this should be unticked > > Am I missing something? or is some bug that should be fixed? > > I am using those versions: > > Emacs version: > GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll bars) > of 2013-08-30 on apocalipsis > > Org-mode version: > Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ > /usr/local/share/emacs/24.3/lisp/org/) > > Regards, > Borja Tarraso >
Re: [O] Opening an Org file slowed down
Hi Nico On Wed, Nov 27, 2013 at 12:27 PM, Nicolas Richard wrote: > Can you show the output of > M-: (insert (mapconcat #'car load-history "\n")) > in each case ? It will output the list of loaded files, which hopefuly > shows a difference. It shows a difference, see attachements. It looks like but it was not me loosing some first lines when doing this, I cross-checked :-). Michael org-mode/lisp/org-element.el org-mode/lisp/org-rmail.el org-mode/lisp/org-mhe.el org-mode/lisp/org-irc.el org-mode/lisp/org-info.el org-mode/lisp/org-gnus.el org-mode/lisp/org-docview.el emacs/lisp/doc-view.elc emacs/lisp/jka-compr.elc emacs/lisp/image-mode.elc emacs/lisp/dired.elc org-mode/lisp/org-bibtex.el emacs/lisp/textmodes/bibtex.elc org-mode/lisp/org-bbdb.el org-mode/lisp/org-w3m.el org-mode/lisp/org.el emacs/lisp/emacs-lisp/byte-opt.elc emacs/lisp/emacs-lisp/warnings.elc emacs/lisp/emacs-lisp/bytecomp.elc emacs/lisp/emacs-lisp/cconv.elc emacs/lisp/edmacro.elc emacs/lisp/kmacro.elc emacs/lisp/emacs-lisp/derived.elc org-mode/lisp/org-macro.el org-mode/lisp/org-footnote.el org-mode/lisp/org-pcomplete.el emacs/lisp/pcomplete.elc org-mode/lisp/org-list.el org-mode/lisp/org-faces.el org-mode/lisp/org-entities.el emacs/lisp/outline.elc org-mode/lisp/org-version.el org-mode/lisp/ob-emacs-lisp.el org-mode/lisp/ob.el org-mode/lisp/ob-tangle.el org-mode/lisp/org-src.el emacs/lisp/emacs-lisp/easy-mmode.elc org-mode/lisp/ob-ref.el org-mode/lisp/ob-lob.el org-mode/lisp/ob-table.el org-mode/lisp/ob-keys.el org-mode/lisp/ob-exp.el org-mode/lisp/ob-comint.el emacs/lisp/comint.elc emacs/lisp/ansi-color.elc emacs/lisp/emacs-lisp/ring.elc org-mode/lisp/ob-core.el org-mode/lisp/ob-eval.el org-mode/lisp/org-compat.el emacs/lisp/emacs-lisp/advice.elc emacs/lisp/help-fns.elc org-mode/lisp/org-macs.el org-mode/lisp/org-loaddefs.el emacs/lisp/emacs-lisp/find-func.elc emacs/lisp/calendar/calendar.elc emacs/lisp/calendar/cal-menu.elc emacs/lisp/calendar/cal-loaddefs.el emacs/lisp/gnus/gnus-sum.elc emacs/lisp/gnus/nnoo.elc emacs/lisp/gnus/gnus-group.elc emacs/lisp/gnus/gnus-undo.elc emacs/lisp/gnus/nnmail.elc emacs/lisp/gnus/mail-source.elc emacs/lisp/gnus/gnus-start.elc emacs/lisp/gnus/gnus-spec.elc emacs/lisp/gnus/gnus-int.elc emacs/lisp/gnus/gnus-range.elc emacs/lisp/gnus/message.elc emacs/lisp/emacs-lisp/cl-macs.elc emacs/lisp/emacs-lisp/gv.elc emacs/lisp/format-spec.elc emacs/lisp/mail/rfc822.elc emacs/lisp/gnus/mml.elc emacs/lisp/emacs-lisp/easymenu.elc emacs/lisp/gnus/mml-sec.elc emacs/lisp/gnus/mm-decode.elc emacs/lisp/gnus/mm-bodies.elc emacs/lisp/gnus/mm-encode.elc emacs/lisp/gnus/mail-parse.elc emacs/lisp/gnus/rfc2231.elc emacs/lisp/gnus/rfc2047.elc emacs/lisp/gnus/rfc2045.elc emacs/lisp/gnus/ietf-drums.elc emacs/lisp/mail/mailabbrev.elc emacs/lisp/gnus/gmm-utils.elc emacs/lisp/mail/mailheader.elc emacs/lisp/gnus/gnus-win.elc emacs/lisp/gnus/gnus.elc emacs/lisp/gnus/gnus-ems.elc emacs/lisp/gnus/nnheader.elc emacs/lisp/gnus/gnus-util.elc emacs/lisp/mail/mail-utils.elc emacs/lisp/gnus/mm-util.elc emacs/lisp/gnus/mail-prsvr.elc emacs/lisp/wid-edit.elc emacs/lisp/emacs-lisp/cl.elc emacs/lisp/emacs-lisp/cl-lib.elc emacs/lisp/emacs-lisp/cl-loaddefs.el emacs/lisp/calendar/time-date.elc emacs/lisp/international/uni-mirrored.el emacs/lisp/subdirs.el emacs/leim/leim-list.el emacs/lisp/tooltip.elc emacs/lisp/vc/ediff-hook.elc emacs/lisp/vc/vc-hooks.elc emacs/lisp/emacs-lisp/float-sup.elc emacs/lisp/mwheel.elc emacs/lisp/term/x-win.elc emacs/lisp/term/common-win.elc emacs/lisp/x-dnd.elc emacs/lisp/dynamic-setting.elc emacs/lisp/tool-bar.elc emacs/lisp/dnd.elc emacs/lisp/international/fontset.elc emacs/lisp/image.elc emacs/lisp/emacs-lisp/regexp-opt.elc emacs/lisp/fringe.elc emacs/lisp/buff-menu.elc emacs/lisp/emacs-lisp/tabulated-list.elc emacs/lisp/replace.elc emacs/lisp/newcomment.elc emacs/lisp/textmodes/fill.elc emacs/lisp/textmodes/text-mode.elc emacs/lisp/emacs-lisp/lisp-mode.elc emacs/lisp/textmodes/paragraphs.elc emacs/lisp/register.elc emacs/lisp/textmodes/page.elc emacs/lisp/emacs-lisp/lisp.elc emacs/lisp/menu-bar.elc emacs/lisp/rfn-eshadow.elc emacs/lisp/isearch.elc emacs/lisp/emacs-lisp/timer.elc emacs/lisp/select.elc emacs/lisp/scroll-bar.elc emacs/lisp/mouse.elc emacs/lisp/jit-lock.elc emacs/lisp/font-lock.elc emacs/lisp/emacs-lisp/syntax.elc emacs/lisp/facemenu.elc emacs/lisp/font-core.elc emacs/lisp/term/tty-colors.elc emacs/lisp/frame.elc emacs/lisp/indent.elc emacs/lisp/language/cham.elc emacs/lisp/language/burmese.elc emacs/lisp/language/khmer.elc emacs/lisp/language/georgian.elc emacs/lisp/language/utf-8-lang.elc emacs/lisp/language/misc-lang.elc emacs/lisp/language/vietnamese.elc emacs/lisp/language/tibetan.elc emacs/lisp/language/thai.elc emacs/lisp/language/tai-viet.elc emacs/lisp/language/lao.elc emacs/lisp/language/korean.elc emacs/lisp/language/japanese.elc emacs/lisp/international/eucjp-ms.el emacs/lisp/international/cp51932.el emacs/lisp/language/hebrew.elc emacs/lisp/language/greek.elc emacs/lisp/language/romanian.elc
Re: [O] org-publish parameters mismatch → cannot publish to HTML
Daniel Clemente writes: > Hi, in ox-publish.el I see in line 555: > > (defun org-publish-org-to (backend filename extension plist &optional pub-dir) > … > > org-publish-org-to-html seems to have its parameters in the same > order (filename, extension, plist). Correct me if I'm wrong. > > But then in same file, line 654: > (when (org-publish-needed-p > filename pub-dir f tmp-pub-dir base-dir) > (funcall f project-plist filename tmp-pub-dir) > … > > With the default setting f == org-publish-org-to-html, the funcall > passes parameters in the wrong order: plist filename. It should be: > filename extension plist > > Later I see org trying to open the „filename“ variable which is not > a file name but a plist: (wrong-type-argument stringp (:base-directory > "~/repoweb/ofinial…" …) …) file-truename((:base-directory > "~/repoweb/ofinial/hacer/" :publishing-directory …) …) > > > Maybe my setup is wrong (I'm confused with the org-publish / > ox-publish mix) but the org-publish-project-alist seems safe; the > stranges thing is: :publishing-function org-publish-org-to-html > > > Does org-publish work for someone else? Why do I see new problems > each time I try to publish…? > If you are using org8.X, then org-publish-org-to-html no longer exists. If it does, you are picking up old org bits from somewhere. See http://orgmode.org/worg/org-8.0.html for some tips, but bear in mind that it's probably incomplete. -- Nick
Re: [O] Controlling image width and placement in Beamer export
Jarmo Hurri writes: > Greetings John. > > John Hendy writes: > >> This comes up all the time. > > Perhaps we could lower the frequency by making a small change to the > manual? > >> The key is to put it 1) before results (as you've done) and 2) to use >> a named source block (with #+name: foo above your babel code) so that >> Org knows what the results block actually is. Otherwise, as you >> currently have it, if you re-run the babel block, you'll keep the >> results section you already have and it will spit out another one >> below it since it no longer recognizes that the babel block and >> current, modified results block go together. > > Done. For some reason not doing 2) also worked correctly, but I agree > that it is still a good idea to name the blocks. > Yes, Eric fixed that problem some months ago, so the urgency of naming code blocks has gone way down - but it should still be considered "best practice" imo. -- Nick
Re: [O] commit 5ea0228 has problem opening big org-mode file
I pushed the fix to master. Thanks to York and Tom for all the help. I ran ``make test before pushing''. There were two failures, I believe unrelated to this patch: , | Ran 481 tests, 479 results as expected, 2 unexpected (2013-11-27 09:20:58-0500) | 4 expected failures | | 2 unexpected results: |FAILED test-ob/catches-all-references |FAILED test-org-element/link-parser ` -- Nick
Re: [O] not handling failing sql statements in ob-sql.el with postgresql
On 2013-11-27 04:49, Joost Helberg wrote:
Hi,
in case psql (version 9.1 and later) encounters a SQL error, e.g. a
syntax error, it doesn't exit with an error-code. Instead it
continues and exits with 0. This means that evaluating faulty SQL-code
in org-mode/babel leaves the user with no clue of why the result set is
empty.
I changed the code in ob-sql.el by adding the
command-line option to the psql command in order to make things work
correct. This option not only makes psql exit at the first error, it
also exits with a not 0 error-code.
line 125 and further of my ob-sql.el:
('postgresql (format
"psql --set=\"ON_ERROR_STOP=1\" -A -P footer=off -F \"\t\" -f %s -o
%s %s"
(org-babel-process-file-name in-file)
(org-babel-process-file-name out-file)
(or cmdline "")))
Is this a change worth applying? Or will it break things?
Did a quick check, and this option goes all the way back to postgresql
7.1, so it looks like it won't break anything that shouldn't be
broken :), and should be applied.
rick
[O] Getting checkboxes in HTML output?
I noticed that HTML output contains "[ ]" and "[X]", just like the mark-up. Wouldn't it make sense to use actual unchecked or checked checkboxes in HTML? Is there a simple way to do this that I've overlooked? Thanks, -pd
Re: [O] Getting checkboxes in HTML output?
Peter Davis writes: > I noticed that HTML output contains "[ ]" and "[X]", just like the > mark-up. Wouldn't it make sense to use actual unchecked or checked > checkboxes in HTML? > > Is there a simple way to do this that I've overlooked? > A cursory glance through ox-html.el uncovered this: --8<---cut here---start->8--- (defun org-html-checkbox (checkbox) "Format CHECKBOX into HTML." (case checkbox (on "[X]") (off "[ ]") (trans "[-]") (t ""))) --8<---cut here---end--->8--- Maybe you can redefine this function to do what you want? Nick
Re: [O] Opening an Org file slowed down
Michael Brand writes: > On Wed, Nov 27, 2013 at 12:27 PM, Nicolas Richard >> M-: (insert (mapconcat #'car load-history "\n")) > > It shows a difference, see attachements. It seems from my own tests that in the `org-version' case, org-element is in fact not used. Example with org-element loaded: $ emacs --batch -Q -L /home/youngfrog/sources/org-mode/lisp -l org-element --eval '(elp-instrument-package "org")' 400.org --eval '(elp-results)' OVERVIEW Loading vc-git... Function Name Call Count Elapsed Time Average Time == == org-mode1 5.400860453 5.400860453 org-set-startup-visibility 1 5.313854095 5.313854095 org-cycle-hide-drawers 2 5.3121005389 2.6560502694 org-element-at-point400 5.266095204 0.0131652380 org-element-cache-get 82199 0.6185547400 7.525...e-06 org-element-type162000 0.2590344329 1.598...e-06 org-element-put-property81401 0.1565762810 1.923...e-06 org-element--current-element12010.1494111070 0.0001244055 org-element-property88592 0.1363126259 1.538...e-06 org-element--cache-pending-changes-p82197 0.1144674349 1.392...e-06 org-load-modules-maybe 2 0.08437738 0.04218869 org-flag-drawer 400 0.0376304490 9.407...e-05 org-element-item-parser 400 0.0275906270 6.897...e-05 org-element-cache-put 12010.0250324789 2.084...e-05 org-element-cache-reset 1 0.023597284 0.023597284 org-element--list-struct1 0.010440769 0.010440769 org-element-paragraph-parser400 0.0072944419 1.823...e-05 org-at-heading-p28010.0071912889 2.567...e-06 org-get-limited-outline-regexp 24010.0061038529 2.542...e-06 org-match-string-no-properties 12000.0054390299 4.532...e-06 org-element-property-drawer-parser 400 0.0045985369 1.149...e-05 org-element--collect-affiliated-keywords401 0.0031594279 7.878...e-06 org-looking-at-p23990.0028486419 1.187...e-06 org-list-get-tag400 0.0027069029 6.767...e-06 org-string-match-p 11990.0020501510 1.709...e-06 org-cycle-show-empty-lines 2 0.000984001 0.0004920005 org-list-get-nth400 0.0008991660 2.247...e-06 org-cycle 1 0.000850248 0.000850248 org-cycle-internal-global 1 0.000763145 0.000763145 org-set-regexps-and-options 1 0.000669289 0.000669289 org-element-plain-list-parser 1 0.000519329 0.000519329 org-add-link-type 8 0.0004422659 5.528...e-05 org-element-restriction 401 0.0004163749 1.038...e-06 org-macro-initialize-templates 1 0.000405989 0.000405989 org-make-link-regexps 8 0.0003423549 4.279...e-05 org-set-visibility-according-to-property1 0.000317979 0.000317979 org-babel-hide-all-hashes 1 0.000316974 0.000316974 org-macro--collect-macros 1 0.000306365 0.000306365 org-overview1 0.000227539 0.000227539 org-set-regexps-and-options-for-tags1 0.000193121 0.000193121 org-update-radio-target-regexp 1 0.000179085 0.000179085 org-all-targets 1 0.000164694 0.000164694 org-install-agenda-files-menu 1 0.00012613 0.00012613 org-set-local 45 7.178...e-05 1.595...e-06 org-unlogged-message1 5.5189e-05 5.5189e-05 org-setup-filling 1 4.4196e-05 4.4196e-05 org-add-hook5 2.937...e-05 5.874e-06 org-find-invisible-foreground
[O] useing :PROPERTIES: to set export options for pdflatex
Below is what I have in a subtree that I export to pdf. It does what I
want. But isn't there a way to do it entirely with setting tree
PROPERTIES? (without use of #+LATEX_HEADER or #+OPTIONS) I seem to
recall there is, but for the life of me I can't find the link to the
documentation I thought I had saved.
Thanks.
** Changes adopted at CSE committee meeting [2013-11-25 Mon]
:PROPERTIES:
:EXPORT_FILE_NAME: ThomasWileyCloseOf-11-25-2013
:EXPORT_TITLE: Thomas Wiley as Adopted by CSE Committee 25 November 2013
:END:
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+OPTIONS: toc:nil
--Chris
--
Christopher W. Ryan, MD, MS
SUNY Upstate Medical University Clinical Campus at Binghamton
425 Robinson Street, Binghamton, NY 13904
cryanatbinghamtondotedu
Re: [O] Opening an Org file slowed down
Michael Brand writes: > 2) choice: >- for quadratic do: M-x org-mode >- for linear do: M-x org-version You have a botched installation. Make sure that the autoloads are current, that the Org install directory comes first in load-path and that you require org-loaddefs before anything else in your startup sequence that possibly touches anything Org-related. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Getting checkboxes in HTML output?
On Wed, Nov 27, 2013 at 11:03:38AM -0500, Nick Dokos wrote: > Peter Davis writes: > > > I noticed that HTML output contains "[ ]" and "[X]", just like the > > mark-up. Wouldn't it make sense to use actual unchecked or checked > > checkboxes in HTML? > > > > Is there a simple way to do this that I've overlooked? > > > > A cursory glance through ox-html.el uncovered this: > > --8<---cut here---start->8--- > (defun org-html-checkbox (checkbox) > "Format CHECKBOX into HTML." > (case checkbox (on "[X]") > (off "[ ]") > (trans "[-]") > (t ""))) > --8<---cut here---end--->8--- > > Maybe you can redefine this function to do what you want? Yes, this works: --8<---cut here---start->8--- (defun org-html-checkbox (checkbox) "Format CHECKBOX into HTML." (case checkbox (on "") (off "") (trans "[-]") (t ""))) --8<---cut here---end--->8--- Thank you! -pd
Re: [O] Anniversaries from BBDB available to calendar and diary?
Hi Myles, Thanks for your reply. Myles English writes: > I wonder, did you look at the section of 10.3.1 titled "Anniversaries > from BBDB"? This is what prompted me to store many of the anniversaries in BBDB as opposed to the diary. Following the information in section 10.3.1 of the manual allows one to see these anniversaries in the Org agenda, but they are now not shown in the calendar/diary. So far, I've been able to partially resolve the issue by upgrading to BBDB 3, which includes bbdb-anniv.el. ;; To display BBDB anniversaries in the Emacs diary, use ;; (add-hook 'diary-list-entries-hook 'bbdb-anniv-diary-entries) Joseph
Re: [O] useing :PROPERTIES: to set export options for pdflatex
Hello,
On 11/27/2013 06:15 PM, Christopher W. Ryan wrote:
> Below is what I have in a subtree that I export to pdf. It does what I
> want. But isn't there a way to do it entirely with setting tree
> PROPERTIES? (without use of #+LATEX_HEADER or #+OPTIONS) I seem to
> recall there is, but for the life of me I can't find the link to the
> documentation I thought I had saved.
>
> Thanks.
>
>
> ** Changes adopted at CSE committee meeting [2013-11-25 Mon]
> :PROPERTIES:
> :EXPORT_FILE_NAME: ThomasWileyCloseOf-11-25-2013
> :EXPORT_TITLE: Thomas Wiley as Adopted by CSE Committee 25 November 2013
> :END:
> #+LATEX_HEADER: \usepackage[margin=1in]{geometry}
> #+OPTIONS: toc:nil
The answer is the same Nicolas sent me yesterday on a different question
("derived exporter EXPORT_... options"):
You can use
** Changes adopted at CSE committee meeting [2013-11-25 Mon]
:PROPERTIES:
:EXPORT_FILE_NAME: ThomasWileyCloseOf-11-25-2013
:EXPORT_TITLE: Thomas Wiley as Adopted by CSE Committee 25 November 2013
:EXPORT_LATEX_HEADER: \usepackage[margin=1in]{geometry}
:EXPORT_OPTIONS: toc:nil
:END:
Best regards,
Robert
--
Robert Klein
UNIX Operations, Max Planck-Institut für Polymerforschung
Ackermannweg 10
55218 Mainz
Re: [O] derived exporter EXPORT_... options
Thanks a lot, I was still thinking in old exporter terms. Best regards Robert On 11/26/2013 08:49 PM, Nicolas Goaziou wrote: > Hello, > > Robert Klein writes: > >> I'm trying to user EXPORT_... options in subtree export in a derived >> exporter. >> >> Using attached ox-hans exporter and the org file hans.org, >> I only get "Wurst" as :hans-option, never "Bratwurst", as given under >> the heading "Two", using both options with subtree export (C-c C-e C-d j >> h and C-c C-e C-d j H. >> >> Do I misunderstand subtree export? > > Keyword are global. Subtree export options are expected to be properties > attached to the root headline: > > * Two > :PROPERTIES: > :EXPORT_HANS_OPTION: Bratwurst > :END: > > Also, the property name will still be :hans-option (i.e. no "export-" > appended). During a subtree export the property has precedence over the > keyword. > > > Regards, > -- Robert Klein UNIX Operations, Max Planck-Institut für Polymerforschung Ackermannweg 10 55218 Mainz
Re: [O] commit 5ea0228 has problem opening big org-mode file
Nick Dokos writes: > I pushed the fix to master. Thanks to York and Tom for all the help. I'm not sure this fix is complete. It seems that when someone would manually enter org-mode (say, in a scratch buffer) Emacs could return to an entirely different mode upon executing org-reset. > | 2 unexpected results: > |FAILED test-ob/catches-all-references This one is the bug I reported earlier today. > |FAILED test-org-element/link-parser This on the other hand bisects to your commit. Plus, the above explanation is the reason for the test fail. I've pushed a fix (f2483ec) that hopefully has no other side-effects not covered by tests. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] commit 5ea0228 has problem opening big org-mode file
Achim Gratz writes: > Nick Dokos writes: >> I pushed the fix to master. Thanks to York and Tom for all the help. > > I'm not sure this fix is complete. It seems that when someone would > manually enter org-mode (say, in a scratch buffer) Emacs could return to > an entirely different mode upon executing org-reset. > >> | 2 unexpected results: >> |FAILED test-ob/catches-all-references > > This one is the bug I reported earlier today. > >> |FAILED test-org-element/link-parser > > This on the other hand bisects to your commit. Plus, the above > explanation is the reason for the test fail. I've pushed a fix > (f2483ec) that hopefully has no other side-effects not covered by tests. > OK, thanks for that. I was rushing this morning and did a pattern match on the test name and decided it couldn't be me: famous last words. And to add insult to injury, I didn't check on failures without the patch. Oy,vey... However, with your patch there is the opposite side of the coin: if you have a buffer in a mode derived from org (as in York's case), then doing C-c C-c on the options line will reset the mode to org, not to the derived one, right? Nick
Re: [O] Opening an Org file slowed down
Hi Achim Thank you for looking into this. On Wed, Nov 27, 2013 at 7:13 PM, Achim Gratz wrote: > Michael Brand writes: >> 2) choice: >>- for quadratic do: M-x org-mode >>- for linear do: M-x org-version > > You have a botched installation. Make sure that the autoloads > are current, I always do "make cleanall uncompiled". Is this correct? > that the Org install directory comes first in load-path I checked with C-h v load-path and my "/git/org-mode/lisp" is the very first. > and that you require org-loaddefs before anything else in your > startup sequence that possibly touches anything Org-related. Before I tried without the --eval, but I can reproduce quadratic with the following too: /[...]/Emacs -Q -L /git/org-mode/lisp --eval '(require (quote org-loaddefs))' Now I tried "make cleanall compile" the first time and then I can not reproduce anymore until I go back to "make cleanall uncompiled". Did you try to reproduce with my recipe and uncompiled? Michael
Re: [O] commit 5ea0228 has problem opening big org-mode file
Nick Dokos writes: > However, with your patch there is the opposite side of the coin: if you > have a buffer in a mode derived from org (as in York's case), then doing > C-c C-c on the options line will reset the mode to org, not to the > derived one, right? It would have done exactly that before your patch, so at least that doesn't change anything. If that is indeed a problem, then one would either have to remember the mode-name, then call normal-mode and then re-instate the mode that has been remembered (and hope for the best) or check that the mode we ended up in is derived from org-mode. I think the latter is general enough to cover the use-cases discussed so far, so I've implemented it until someone finds a better solution. But all these troubles seem to indicate that maybe it isn't a very bright idea to simply re-initialize org-mode completely just to get the local setup refreshed. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Opening an Org file slowed down
Michael Brand writes: > I always do "make cleanall uncompiled". Is this correct? I don't recommend it, but it should work if you're using a non-buggy Emacs (i.e. not Emacs 23, which never ignores site-lisp). > Before I tried without the --eval, but I can reproduce quadratic with > the following too: > > /[...]/Emacs -Q -L /git/org-mode/lisp --eval '(require (quote org-loaddefs))' Then you pull in something via an old autoload that points to a file that doesn't exist anymore in newer Org. Also, if Emacs (with a capital E) isn't a typo, you might want to check it isn't actually a script that doesn't feed through all switches. > Now I tried "make cleanall compile" the first time and then I can not > reproduce anymore until I go back to "make cleanall uncompiled". Did > you try to reproduce with my recipe and uncompiled? No. But you can try this: /[...]/Emacs -Q -L /git/org-mode/lisp \ -l ../testing/org-batch-test-init.el -l org-loaddefs Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Opening an Org file slowed down
Hi Achim On Wed, Nov 27, 2013 at 9:05 PM, Achim Gratz wrote: > Michael Brand writes: >> I always do "make cleanall uncompiled". Is this correct? > > I don't recommend it, but it should work if you're using a non-buggy > Emacs (i.e. not Emacs 23, which never ignores site-lisp). Not recommend which part? Did you mean to recommend compiled and not recommend uncompiled?? > Also, if Emacs (with a capital E) isn't a typo No, it's the OS X specific Mach-O executable, built with --with-ns and make install. > But you can try this: > > /[...]/Emacs -Q -L /git/org-mode/lisp \ > -l ../testing/org-batch-test-init.el -l org-loaddefs Uncompiled and then the rest of my recipe? Still quadratic. Michael
Re: [O] useing :PROPERTIES: to set export options for pdflatex
Excellent, thanks Robert. It seemed like I was mixing paradigms, and I didn't
like it. This is much better.
Chris
Sent from my android device.
-Original Message-
From: Robert Klein
To: "Christopher W. Ryan" , emacs-orgmode@gnu.org
Sent: Wed, 27 Nov 2013 13:47
Subject: Re: [O] useing :PROPERTIES: to set export options for pdflatex
Hello,
On 11/27/2013 06:15 PM, Christopher W. Ryan wrote:
> Below is what I have in a subtree that I export to pdf. It does what I
> want. But isn't there a way to do it entirely with setting tree
> PROPERTIES? (without use of #+LATEX_HEADER or #+OPTIONS) I seem to
> recall there is, but for the life of me I can't find the link to the
> documentation I thought I had saved.
>
> Thanks.
>
>
> ** Changes adopted at CSE committee meeting [2013-11-25 Mon]
> :PROPERTIES:
> :EXPORT_FILE_NAME: ThomasWileyCloseOf-11-25-2013
> :EXPORT_TITLE: Thomas Wiley as Adopted by CSE Committee 25 November 2013
> :END:
> #+LATEX_HEADER: \usepackage[margin=1in]{geometry}
> #+OPTIONS: toc:nil
The answer is the same Nicolas sent me yesterday on a different question
("derived exporter EXPORT_... options"):
You can use
** Changes adopted at CSE committee meeting [2013-11-25 Mon]
:PROPERTIES:
:EXPORT_FILE_NAME: ThomasWileyCloseOf-11-25-2013
:EXPORT_TITLE: Thomas Wiley as Adopted by CSE Committee 25 November 2013
:EXPORT_LATEX_HEADER: \usepackage[margin=1in]{geometry}
:EXPORT_OPTIONS: toc:nil
:END:
Best regards,
Robert
--
Robert Klein
UNIX Operations, Max Planck-Institut für Polymerforschung
Ackermannweg 10
55218 Mainz
Re: [O] Opening an Org file slowed down
Michael Brand writes: > It shows a difference, see attachements. It looks like but it was not > me loosing some first lines when doing this, I cross-checked :-). I've had a brief look at this. It seems that some of the differences are due to elp instrumenting a much larger range of functions when org-mode has already initialized vs. when only org-version had been called. Another difference is that when org-mode gets initialized before, org-startup-folded is true, which introduces another slight difference. lisp/org-mode> time emacs --batch -Q -L lisp -l testing/org-batch-test-init.el -l org-loaddefs 400.org 3.748u 0.096s 0:04.22 90.7% lisp/org-mode> time emacs --batch -Q -L lisp -l testing/org-batch-test-init.el -l org-loaddefs 800.org 13.880u 0.068s 0:14.47 96.3% lisp/org-mode> time emacs --batch -Q -L lisp -l testing/org-batch-test-init.el -l org-loaddefs -f org-version 400.org 3.764u 0.072s 0:04.08 93.8% lisp/org-mode> time emacs --batch -Q -L lisp -l testing/org-batch-test-init.el -l org-loaddefs -f org-version 800.org 13.956u 0.072s 0:14.51 96.6% lisp/org-mode> time emacs --batch -Q -L lisp -l testing/org-batch-test-init.el -l org-loaddefs -f org-mode 400.org OVERVIEW 3.736u 0.092s 0:04.16 91.8% lisp/org-mode> time emacs --batch -Q -L lisp -l testing/org-batch-test-init.el -l org-loaddefs -f org-mode 800.org OVERVIEW 13.872u 0.056s 0:14.51 95.9% Once that is out of the equation, there isn't any difference to speak of. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] imaxima babel
Alan Schmitt writes: > > This is very useful, thanks a lot. A couple comments and questions on > your example file (which would be a nice addition to worg). > There is actually already some maxima documentation on worg that got me started as I was unsure if maxima is supported at all, I have added the link in the summary. It would probably be good to merge to worg, but I have no access to it and not time right now to learn how it works. Feel free to copy paste whatever is useful to amend it though. > It would be useful to know more about maxima and how to enable it with > babel (a link to existing documentation, if there is any, would be > great). > Thanks for the pointer, I have included some more resources I used. > In my setup, the previewing latex fragment keybinding is "C-c C-x C-l", > not "C-c C-x C-x". Sorry, that was a typo! > > I tried previewing the fragment, but I got the error: > > , > | Failed to create dvi file from > /var/folders/68/fvntfrw92y50gkk_67rkhsfwgn/T/orgtex16220cbr.tex > ` > > Looking at the tex file and the log file, it seems that the tex files is > to be processed by xelatex, but the command called seems to be pdfTeX. I > probably have something misconfigured, but I don't know what it is. Any > suggestion? > Are you sure you have 'dvipng' installed as mentioned in the manual? , | If you have `dvipng' installed, LaTeX fragments can be processed to | produce preview images of the typeset expressions: ` I have dvipng 1.14 that comes with texlive 2013-3 in F20 which seems to work fine. > Finally, and it's a nitpick: breaking lines in the middle of (info ...) > links prevents following them using "C-x C-e". > Actually, I never used these sort of links myself, thanks for pointing out how this is done! :) I moved all infolinks to footnotes to avoid the line breaks. All the best, J orgmaxima_example.org Description: Lotus Organizer
[O] firefox bookmarks to org-mode
Dear list, Could anyone give me some pointers on a set-up to get links from firefox to an org-mode file? I would like to press a key combination in firefox (say Ctrl-D) and have the web address of the site stored as an entry in some org-mode file. Many thanks, Julian -- Julian Mariano Burgos, PhD Hafrannsóknastofnun/Marine Research Institute Skúlagata 4, 121 Reykjavík, Iceland Sími/Telephone : +354-5752037 Bréfsími/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is
[O] working mathjax example
Hi,
I'm trying to bring up a simple mathjax example. Org-mode is git
current and otherwise works fine. MathJax is git current and lives in
/opt/mathjax/git/MathJax.js. Both firefox 26 and chromium 31 display
the MathJax tests perfectly from my org->html test directory.
I've copied the example code from the org manual into a file
containing:
--cut-herecut-herecut-herecut-herecut-here--
#+HTML_MATHJAX: align:"left" mathml:t path:"/opt/mathjax/git/MathJax.js"
#+options: latex:verbatim
\begin{equation}
x=\sqrt{b}
\end{equation}
If $a^2=b$ and \( b=2 \), then the solution must be
either $$ a=+\sqrt{2} $$ or \[ a=-\sqrt{2} \].
--cut-herecut-herecut-herecut-herecut-here--
I exported per the instructions using org-export-to-html. The
exported html file has lots of good stuff suggesting that the export
seems to be working. But both firefox and chrome display the math
bits replaced by [Math Processing Error]. Does anyone have an idea
what I am doing wrong?
The actual exported is (stuff before elided):
json
\begin{equation}
x=\sqrt{b}
\end{equation}
If \(a^2=b\) and \( b=2 \), then the solution must be
either $$ a=+\sqrt{2} $$ or \[ a=-\sqrt{2} \].
Author: Russell L. Carter
Created: 2013-11-27 Wed 16:17
http://www.gnu.org/software/emacs/";>Emacs 24.3.1
(http://orgmode.org";>Org mode 8.2.3c)
http://validator.w3.org/check?uri=referer";>Validate
Thanks!
Russell
[O] #+LATEX before first heading getting ignored LaTeX output
I am experiencing a problem in org-mode whereby a #+LATEX block before
the first heading is being ignored in the generated LaTeX. Below is a
simple example, first without export the Introduction header with
:noexport: , and then with. I realise I could use #+BEGIN_abstract ,
but this is not about abstracts.. I have lots of #+LATEX lines in a
more realistic example, i.e. acknowledgements, dedication etc.
%
#+LaTeX_CLASS: article
#+TITLE: My Title
#+AUTHOR: Joe Bloggs
#+OPTIONS: H:5
#+LATEX: \begin{abstract}
This is my abstract.
#+LATEX: \end{abstract}
#+TOC: headlines 2
* Introduction :noexport:
Hello.
%
Exporting this gives:
%
% Created 2013-11-27 Wed 23:47
\documentclass[11pt]{article}
\author{Joe Bloggs}
\date{\today}
\title{My Title}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs 24.3.1 (Org mode 8.2.3c)}}
\begin{document}
\maketitle
\tableofcontents
\begin{abstract}
This is my abstract.
\end{abstract}
\setcounter{tocdepth}{2}
\tableofcontents
% Emacs 24.3.1 (Org mode 8.2.3c)
\end{document}
%
However, if I switch the tag for the `Introduction` heading to
:export: , the generated LaTeX is:
%
% Created 2013-11-27 Wed 23:48
\documentclass[11pt]{article}
\author{Joe Bloggs}
\date{\today}
\title{My Title}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs 24.3.1 (Org mode 8.2.3c)}}
\begin{document}
\maketitle
\tableofcontents
\section{Introduction}
\label{sec-1}
Hello.
% Emacs 24.3.1 (Org mode 8.2.3c)
\end{document}
%
Why has my \begin{abstract} .. \end{abstract} disappeared? As you can
see, I'm runing org-mode 8.2.3c, from HEAD from the git repo.
Re: [O] commit 5ea0228 has problem opening big org-mode file
> The only path that needs to be in load-path is the lisp directory for > org-mode, which is the second line (that you say is "key"). You are right on this which I didn't realize before you pointed out, thanks. Anyways, in my configuration I always have both lines, and I'm going to delete the first line. And also, when I was trying to reproduce the issue in a minimum setup, I deleted the second line then the problem didn't show up which I now realized was simply because I ended up running the `org-mode' shipped with Emacs 24.3, my bad, sorry for the confusion. > Unless you have created your completely original way of "installing" Org, then > only the second line is needed. As explained above, yes, my `org-mode' is in some other path outside of Emacs, e.g., "foo/org-mode", which I had already explained, I'm going to delete the first line. But it doesn't hurt to have the first line anyways right? > If you do have created your own completely original way of "installing" Org, > then please don't expect anybody else to be able to help. It should have been clear by now that this was a "real" problem totally unrelated to "my own completely original way of installing Org" and had been addressed properly. I'm not sure if you had tried my reproducer. > Yes, because you wouldn't load any of the new code. Already explained on this in previous paragraphs. > Maybe because your "installation" is borked, No, my installation had never broken, and as we've all seen, the problem has nothing to do with my "broken installation". > but we can't know because you never provided enough information to tell. I'm pretty sure I had provided pretty effective reproducer with which Nicolas had successfully reproduced the issue. By the way, it took me two hours to isolate it from my own .emacs (over 400KB). > There's a reason for org-submit-bug-report to exist; among other things it > includes information about the Emacs and Org version and clueas as to how the > installation is set up. I didn't know that, thanks for telling me. York
Re: [O] #+LATEX before first heading getting ignored LaTeX output
On Wed, Nov 27, 2013 at 5:54 PM, Rob Stewart wrote:
> I am experiencing a problem in org-mode whereby a #+LATEX block before
> the first heading is being ignored in the generated LaTeX. Below is a
> simple example, first without export the Introduction header with
> :noexport: , and then with. I realise I could use #+BEGIN_abstract ,
> but this is not about abstracts.. I have lots of #+LATEX lines in a
> more realistic example, i.e. acknowledgements, dedication etc.
>
I can confirm on Linux running Org-mode version 8.2.3c
(release_8.2.3c-227-g54a64f), though interestingly on Windows, I
*just* exported an analogous example to your successfully. It's
running a git version from April 2013. Rebooting into Linux and trying
on the same file removes my #+begin/end_latex section containing
specifications for fancyhdr and I no longer get my custom footer with
just one headline tagged :export:.
If I tag all headlines *except* the one of interest, it goes back to
functioning properly. I'm guessing this will require tacking back to
the right git commit and it was an intended or un-intended consequence
of some change to the exporter.
Best regards,
John
> %
> #+LaTeX_CLASS: article
>
> #+TITLE: My Title
> #+AUTHOR: Joe Bloggs
> #+OPTIONS: H:5
>
> #+LATEX: \begin{abstract}
> This is my abstract.
> #+LATEX: \end{abstract}
>
> #+TOC: headlines 2
>
> * Introduction
> :noexport:
>
> Hello.
> %
>
> Exporting this gives:
>
> %
> % Created 2013-11-27 Wed 23:47
> \documentclass[11pt]{article}
> \author{Joe Bloggs}
> \date{\today}
> \title{My Title}
> \hypersetup{
> pdfkeywords={},
> pdfsubject={},
> pdfcreator={Emacs 24.3.1 (Org mode 8.2.3c)}}
> \begin{document}
>
> \maketitle
> \tableofcontents
>
> \begin{abstract}
> This is my abstract.
> \end{abstract}
>
> \setcounter{tocdepth}{2}
> \tableofcontents
> % Emacs 24.3.1 (Org mode 8.2.3c)
> \end{document}
> %
>
>
> However, if I switch the tag for the `Introduction` heading to
> :export: , the generated LaTeX is:
>
> %
> % Created 2013-11-27 Wed 23:48
> \documentclass[11pt]{article}
> \author{Joe Bloggs}
> \date{\today}
> \title{My Title}
> \hypersetup{
> pdfkeywords={},
> pdfsubject={},
> pdfcreator={Emacs 24.3.1 (Org mode 8.2.3c)}}
> \begin{document}
>
> \maketitle
> \tableofcontents
>
> \section{Introduction}
> \label{sec-1}
>
> Hello.
> % Emacs 24.3.1 (Org mode 8.2.3c)
> \end{document}
> %
>
> Why has my \begin{abstract} .. \end{abstract} disappeared? As you can
> see, I'm runing org-mode 8.2.3c, from HEAD from the git repo.
>
Re: [O] imaxima babel
writes: > Alan Schmitt writes: > > ... >> Finally, and it's a nitpick: breaking lines in the middle of (info ...) >> links prevents following them using "C-x C-e". >> > Actually, I never used these sort of links myself, thanks for pointing > out how this is done! :) I moved all infolinks to footnotes to avoid the > line breaks. > Just a clarification: you cannot break the *string* argument but newlines in other places are fine: (info "(org) The Spreadsheet") works fine, but (info "(org) The Spreadsheet") does not: the second string is not the same as the first one, since it includes a newline. OTOH, you can escape the newline: (info "(org) The \ Spreadsheet") works fine. The point is that all of this follows from the properties of strings. Just go to the *scratch* buffer and evaluate some expressions: (string-equal "a b" "a \ b") t (string-equal "a b" "a b") nil -- Nick
Re: [O] imaxima babel
writes: > There is actually already some maxima documentation on worg that got me > started as I was unsure if maxima is supported at all, I have added the > link in the summary. It would probably be good to merge to worg, but I > have no access to it and not time right now to learn how it works. Feel > free to copy paste whatever is useful to amend it though. I added this to ob-doc-maxima. It might require some editing. You can learn how to edit Worg here: http://orgmode.org/worg/worg-git.html All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] firefox bookmarks to org-mode
While it's been a while since I've done this, I did get it working at least
once, in a roundable way. I had a setup for bookmarking via org-protocol
and keysnail (http://github.com/mooz/keysnail).
I set up org-protocol in firefox like the documentation said (though I
remember it being REALLY finnicky, but this was well over a year ago so I
can't remember exactly what the issue was). I made an org-capture template
bound to w (hence the /w/ in the URL below), that would take the bookmark
name and URL.
The keysnail setup looked like:
key.setGlobalKey(['C-c', 's', 'l'], function (ev, arg) {
let wc = window.content;
let d = ev.target.ownerDocument;
location.href='org-protocol://capture://w/'+encodeURIComponent(wc.location.href)+'/'+encodeURIComponent(d.title)+'/'+encodeURIComponent(window.getSelection());
display.echoStatusBar("Saved " + d.title + " to org links buffer");
}, 'Save to org-mode capture', true);
So, not the most direct route, but it did the job. These days, I just use
pinboard. Might be nice to make a pinboard to org exporter though. :)
On Wed, Nov 27, 2013 at 3:40 PM, Julian M. Burgos wrote:
> Dear list,
>
> Could anyone give me some pointers on a set-up to get links from firefox
> to an org-mode file? I would like to press a key combination in firefox
> (say Ctrl-D) and have the web address of the site stored as an entry in
> some org-mode file.
> Many thanks,
>
> Julian
>
>
> --
> Julian Mariano Burgos, PhD
> Hafrannsóknastofnun/Marine Research Institute
> Skúlagata 4, 121 Reykjavík, Iceland
> Sími/Telephone : +354-5752037
> Bréfsími/Telefax: +354-5752001
> Netfang/Email: jul...@hafro.is
>
>
Re: [O] Anniversaries from BBDB available to calendar and diary?
Joseph Mingrone writes: > Hi Myles, > > Thanks for your reply. > > Myles English writes: >> I wonder, did you look at the section of 10.3.1 titled "Anniversaries >> from BBDB"? > > This is what prompted me to store many of the anniversaries in BBDB as > opposed to the diary. Following the information in section 10.3.1 of > the manual allows one to see these anniversaries in the Org agenda, but > they are now not shown in the calendar/diary. So far, I've been able to > partially resolve the issue by upgrading to BBDB 3, which includes > bbdb-anniv.el. > > ;; To display BBDB anniversaries in the Emacs diary, use > ;; (add-hook 'diary-list-entries-hook 'bbdb-anniv-diary-entries) Just to make sure I'm following -- no one's yet gotten BBDB anniversaries showing up in the calendar proper yet, have they? I don't use the diary, but I'd sure like to see colored blobs in the calendar (like holidays are currently displayed) for anniversaries defined in BBDB. Eric
[O] How can I convert a org file to a flowchart
Hello: I have to draw a flowchart with many many nodes (about 500) and less construct types(only sequence construct and condition construct), Now I use org file record all the node labels, How can I convert this org to a flowchar if i use tag and link to record all the construct? for example: * A * B :COND: * C * D to a -> B -> C \-> D Thanks --
Re: [O] Bug when cycling
Bastien writes: > with latest master and the file below, hitting TAB at the beginning > of the headline will produce the attached backtrace. I just fixed this: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=c811bb -- Bastien
Re: [O] Anniversaries from BBDB available to calendar and diary?
Eric Abrahamsen writes: > Joseph Mingrone writes: > >> Hi Myles, >> >> Thanks for your reply. >> >> Myles English writes: >>> I wonder, did you look at the section of 10.3.1 titled "Anniversaries >>> from BBDB"? >> >> This is what prompted me to store many of the anniversaries in BBDB as >> opposed to the diary. Following the information in section 10.3.1 of >> the manual allows one to see these anniversaries in the Org agenda, but >> they are now not shown in the calendar/diary. So far, I've been able to >> partially resolve the issue by upgrading to BBDB 3, which includes >> bbdb-anniv.el. >> >> ;; To display BBDB anniversaries in the Emacs diary, use >> ;; (add-hook 'diary-list-entries-hook 'bbdb-anniv-diary-entries) > > Just to make sure I'm following -- no one's yet gotten BBDB > anniversaries showing up in the calendar proper yet, have they? I don't > use the diary, but I'd sure like to see colored blobs in the calendar > (like holidays are currently displayed) for anniversaries defined in > BBDB. > No, but from the calendar, I can use 'd' (diary-view-entries) to show the fancy diary with the BBDB anniversaries. So, the only piece missing, from my perspective, is a way to mark the calendar for the days with a BBDB anniversary. A function for one of the calendar display hooks might do the trick. Joseph
Re: [O] org-publish parameters mismatch → cannot publish to HTML
> > > > org-publish-org-to-html seems to have its parameters in the same > > order (filename, extension, plist). Correct me if I'm wrong. > > > > If you are using org8.X, then org-publish-org-to-html no longer > exists. If it does, you are picking up old org bits from somewhere. > True. And I was following an outdated page which used org-publish-org-to-html: http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html With the new function, it works, thanks. Can we use define-obsolete-function-alias for the old functions?
Re: [O] commit 5ea0228 has problem opening big org-mode file
York Zhao writes: > As explained above, yes, my `org-mode' is in some other path outside of Emacs, > e.g., "foo/org-mode", which I had already explained, I'm going to delete the > first line. But it doesn't hurt to have the first line anyways right? It could have (depending on what other files you might have had there, not from the Git repo). It certainly muddied the waters w.r.t. your bug report. For the rest of your post: no need to get defensive. My point was (and is) that each bug report should clearly state which version of Emacs and Org is used, and where and how these are installed; the most concise way of providing this information is to use org-submit-bug-report. The guesswork to glean this from other information in the thread too often leads to wrong conclusions. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
