Re: [O] Bug: org-mouse.el breaks footnote jumping (Reference to definition doesn't work) [8.2.10 (8.2.10-33-g880a2b-elpaplus @ /home/lufimtse/.emacs.d/elpa/org-plus-contrib-20150216/)]
Hello, Leo Ufimtsev lufim...@redhat.com writes: I define a footnote via : kbd C-c C-x f /kbd as described in the [manual][1]. Then I have something like: - [ ] Leo once said [fn:1] (reference) .. .. .. * Footnotes [fn:1] To make the world a better place, one should use Emacs. (definition) [fn:1] needs to be at column 0 for a definition. I have org-mouse enabled with all org-Mouse-Features Now clicking on the definition `[fn:1] To make ..` jumps back to the reference. But clicking on the reference doesn't jump me to the definition. This works if org-mouse is disabled. I cannot reproduce it on development version. Clicking on the definition jumps me to the reference. Regards, -- Nicolas Goaziou
Re: [O] How to extract raw link and description from the link element?
Marcin Borkowski mb...@wmi.amu.edu.pl writes: Hi all, so I have this: [[file:whatever.org][Some link]] How do I extract bith parts of this link programmatically? My use case is that I have an Org tree of links, and I want to export them to certain XML format. TIA, Have you considered a custom exporter? Just a little thought. Sam -- Samuel W. Flint swfl...@flintfam.org (402) 517-8468 XMPP freenode: swflint http://flintfam.org/~swflint 4096R/266596F4 (9477 D23E 389E 40C5 2F10 DE19 68E5 318E 2665 96F4) The most dangerous phrase in the language is, 'We've always done it this way'. -- Grace Hopper
Re: [O] FR: Fontify links even when in comments
with org-mouse, i sometimes click in the middle of a comment and get surprised that a link opened. -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. And ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] FR: Fontify links even when in comments
inline footnotes too! -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. And ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] [ox-latex, bug?] :caption forces environment
Rasmus ras...@gmx.us writes: AFAIK, we use float actively at one place, namely ;; Case 1. No source fontification. Of org-latex-src-block. In that particular case I guess we could also use capt-of, actually. It's worth trying. Do you want to provide a patch? At some point I wanted to get rid of float, until I became aware that capt-of doesn't ensure that floats/non-floats appear in the right order. Since we wouldn't use floats anymore, this isn't a problem, is it? Regards,
Re: [O] FR: Fontify links even when in comments
On 2/24/15, Nicolas Goaziou m...@nicolasgoaziou.fr wrote: That shouldn't happen, at least in development version. If you can reproduce it, please send an ECM. thank you. it is maint, so it's probably fine in master. btw, my only concern with semantic footnote highlighting is that i just cannot get used to only allowing a single paragraph in inline [unlike non-inline where multiple paragraphs are ok]. i have a filter to fix that that you kindly provided, but it would look awful if they were not highlighted as footnotes.
Re: [O] How to extract raw link and description from the link element?
Marcin Borkowski mb...@wmi.amu.edu.pl writes: On 2015-02-24, at 21:50, Samuel W. Flint swfl...@flintfam.org wrote: Marcin Borkowski mb...@wmi.amu.edu.pl writes: Hi all, so I have this: [[file:whatever.org][Some link]] How do I extract bith parts of this link programmatically? My use case is that I have an Org tree of links, and I want to export them to certain XML format. TIA, Have you considered a custom exporter? Just a little thought. That's exactly what I'm writing. It just hadn't occured to me to use the parsed version in the element tree – I just concentrated on exporting the headlines (which contain the links). Stupid me. Thanks for this (obvious) tip! You are welcome! Glad I could help! Sam -- Samuel W. Flint swfl...@flintfam.org (402) 517-8468 XMPP freenode: swflint http://flintfam.org/~swflint 4096R/266596F4 (9477 D23E 389E 40C5 2F10 DE19 68E5 318E 2665 96F4) The most dangerous phrase in the language is, 'We've always done it this way'. -- Grace Hopper
Re: [O] FR: Fontify links even when in comments
Hello, Samuel Wales samolog...@gmail.com writes: inline footnotes too! That shouldn't happen, at least in development version. If you can reproduce it, please send an ECM. Regards -- Nicolas Goaziou
Re: [O] How to extract raw link and description from the link element?
On 2015-02-24, at 21:50, Samuel W. Flint swfl...@flintfam.org wrote: Marcin Borkowski mb...@wmi.amu.edu.pl writes: Hi all, so I have this: [[file:whatever.org][Some link]] How do I extract bith parts of this link programmatically? My use case is that I have an Org tree of links, and I want to export them to certain XML format. TIA, Have you considered a custom exporter? Just a little thought. That's exactly what I'm writing. It just hadn't occured to me to use the parsed version in the element tree – I just concentrated on exporting the headlines (which contain the links). Stupid me. Thanks for this (obvious) tip! Sam Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
[O] [RFC] Table's documentation
Hi, reading the 8.3beta manual, I note that *#+NAME: *and *#+CAPTION:* were not clearly introduced in the Chapter on tables. (the first in Remote References the last in Images and Tables). I wonder if it is a good a idea to introduce them in the Chapter or tables (just befor The Orgtbl minor mode), refering Remote References and Images and Tables. Thierry
Re: [O] Embedding diagrams in Org
On Tuesday, 24 Feb 2015 at 01:01, Marcin Borkowski wrote: [...] I have one question. #+begin_src latex :results latex raw :exports results Why :results latex raw and not :results latex? I have no idea ;-) I find, unfortunately, that getting babel to do what I want is somewhat of an arcane art (for me) so once I get something doing what I want it to do, I leave things alone... I'm sure it all makes sense but it's probably a case of my not having the time to figure things out properly. When I need to get something done, it's often because I need it *now* (or yesterday :-). -- : Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-843-ga5f1a3.dirty
Re: [O] Problem with relative paths of links in export
Hello, Vikas Rawal vikasli...@agrarianresearch.org writes: I have an old org file, with some source blocks that create a table with some hyperlinks like [[file:../receipts/2015/02/aj140212_1.pdf][19998-DUPLT]] (the file is in receipts subdirectory of the parent directory). Export from the org file used to work fine. But just now, these paths are now working in exported pdf files. What do you get now when exporting such link? What did you expect instead? Regards, -- Nicolas Goaziou
Re: [O] FR: Fontify links even when in comments
Ken Mankoff mank...@gmail.com writes: To me comments are mainly things that don't get exported. Comments are much more than that. They also deactivate the syntax (which is what I call dead syntax). * Headline # SCHEDULED: 2015-02-24 Tue (org-entry-get nil SCHEDULED) = nil Their utility and data density is reduced if they can't contain links (or I can't see that the link is there, which is sort-of the same thing). When writing a document it is useful to leave informal notes to myself that say see X where X is an external file, or a section (or some code) elsewhere in this document, etc. They cannot contain link, nor anything else. However, the feature you describe above was deemed useful enough that `org-open-at-point' sloppily opens anything looking like a link (or a timestamp) within a comment. However, there is, per syntax, no link there, and I don't think it should be fontified. Regards,
[O] Bug: RFE: Truncate habit history [8.2.10 (8.2.10-33-g880a2b-elpa @ /home/phil/.emacs.d/elpa/org-20150216/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Please support limiting the number of state-change history entries for
habits to, say, org-habit-preceding-days (by default, customizable, zero
to mean keep all). The history list for my habits just grows and
grows, to no purpose, but with the effect of slowing down habit cycling.
Emacs : GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll
bars)
of 2014-01-02 on quiz
Package: Org-mode version 8.2.10 (8.2.10-33-g880a2b-elpa @
/home/phil/.emacs.d/elpa/org-20150216/)
current state:
==
(setq
org-id-locations-file ~/.emacs.d/org-id-locations
org-hide-leading-stars t
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-mobile-files '(org-agenda-files ~/org/bookmarks.org
~/org/Cygwin-install-checklist.org
~/org/emacs-install-checklist.org
~/org/Handles.org ~/org/Home-LAN.org
~/org/linux-install-checklist.org
~/org/Mac-install-checklist.org
~/org/Movies.org ~/org/music.org
~/org/Windows-install-checklist.org)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-agenda-diary-file ~/SpiderOak/diary.org
org-occur-hook '(org-first-headline-recenter)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-log-done 'time
org-confirm-shell-link-function 'yes-or-no-p
org-finalize-agenda-hook '(org-agenda-to-appt)
org-special-ctrl-a/e t
org-agenda-prefix-format '((agenda . %-6:c%?-12t%-13s) (timeline . % s)
(todo . %-12:c)
(tags . %-12:c) (search . %-12:c))
org-return-follows-link t
org-default-notes-file ~/org/notes.org
org-capture-templates '((w Capture from web browser such as Conkeror
entry
(file+headline ~/org/bookmarks.org Web
capture)
* %c %?\n Sourced: %u\n %i :prepend t
:jump-to-captured t)
(t Capture a task entry (file+headline
~/org/ToDo.org Incoming)
* TODO %? %^G\n SCHEDULED: %t\n Created:
%U\n %^{Effort}p
:prepend t :jump-to-captured t)
(b Capture a purchasing task entry
(file+headline ~/org/ToDo.org Incoming)
* TODO Bought %? %^G:buy:work:\n
SCHEDULED: %t\n Created: %U\n
:PROPERTIES:\n :DATE_ORDERED: %u\n :END:
%^{PRICE}p :prepend t :jump-to-captured t)
(h Capture a habit entry (file+headline
~/org/ToDo.org Incoming)
* TODO %? %^G\n SCHEDULED:
%(format-time-string \%Y-%m-%d %a\)
.+%^{Interval:|1d}\n Created: %U\n
:PROPERTIES:\n :STYLE:habit\n
:REPEAT_TO_STATE: TODO\n :END: :prepend t
:jump-to-captured t)
(c Capture a phone call to make entry
(file+headline ~/org/ToDo.org Incoming)
* TODO Called %a on %c to %? %^G:@phone:\n
SCHEDULED: %t\n Created: %U\n %^{Effort}p
:prepend t :jump-to-captured t)
(x Capture an SMS text message to send entry
(file+headline ~/org/ToDo.org Incoming)
* TODO Texted %a on %c to %?
%^G:@phone:\n SCHEDULED: %t\n Created: %U\n
%^{Effort}p :prepend t :jump-to-captured t)
(j Capture a journal entry entry (file
~/org/journal.org.gpg)
* %^u Daily journal:\n:PROPERTIES:\n:MOOD:
%^{Mood|10|1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19}\n:MOON:
%(ph/lunar-current-phase-name)\n:STRESS:
Re: [O] Problem with relative paths of links in export
I have an old org file, with some source blocks that create a table with some hyperlinks like [[file:../receipts/2015/02/aj140212_1.pdf][19998-DUPLT]] (the file is in receipts subdirectory of the parent directory). Export from the org file used to work fine. But just now, these paths are now working in exported pdf files. What do you get now when exporting such link? What did you expect instead? Actually, it is a bit weird. The latex export is correct. But link in the pdf file does not open. Perhaps something wrong with the way links work in pdf files (I have tried skim and adobe readers). Does not look like fault of org-mode. My apologies. Vikas
Re: [O] Problem with relative paths of links in export
Actually, it is a bit weird. The latex export is correct. But link in the pdf file does not open. Perhaps something wrong with the way links work in pdf files (I have tried skim and adobe readers). Does not look like fault of org-mode. My apologies. Oops, my bad. I used wrong path! Terrible. Sorry. Vikas
Re: [O] FR: Fontify links even when in comments
Nicolas Goaziou m...@nicolasgoaziou.fr writes: They cannot contain link, nor anything else. However, the feature you describe above was deemed useful enough that `org-open-at-point' sloppily opens anything looking like a link (or a timestamp) within a comment. However, there is, per syntax, no link there, and I don't think it should be fontified. AUCTeX has a variable named `LaTeX-syntactic-comments' : , | User option: If non-nil comments will be handled according to LaTeX |syntax. ` In AUCTeX, it is mainly about filling and indentation, but in Org it could mean let the usual (interactive) commands pretend we're not in a comment. If Org is to adopt such a variable, it could fontify according to what the interactive commands will do. Would that be acceptable ? It could be made a minor mode. -- Nicolas Richard.
[O] org-agenda-to-appt interactively with multiple args?
So I've been playing around with org appointments and found the org-agenda-to-appt function; but upon calling it, it loads my whole day into the appointment queue. I have various questions, such as how I can view and edit the current queue, but more importantly, I read the following as part of the doc string: (org-agenda-to-appt optional REFRESH FILTER rest ARGS) Activate appointments found in `org-agenda-files'. With a C-u prefix, refresh the list of appointments. If FILTER is t, interactively prompt the user for a regular expression, and filter out entries that don't match it. If FILTER is a string, use this string as a regular expression for filtering entries out. Now, is this function not primarily meant to be called interactively? Or, after all these years in emacs, am I going to learn how to pass multiple args to an interactive function? Because the fact is, I don't always want EVERYTHING in the appointment list. I just want an alarm for those one or two things... Sheepishly yours, - Tory
[O] org-mobile-copy-agenda-files: Truncating output file
Hi, org-mobile-push frequently fails to copy my org files to the staging directory with following output: Copying files... org-mobile-copy-agenda-files: Truncating output file: interrupted system call, /Volumes/guivho/org/z.org This error is not consistent. Just call it again, sometimes again and again, and eventually the copy succeeds. Any ideas? Guido -- The opposite of a profound truth may well be another profound truth. -- Bohr
Re: [O] FR: Fontify links even when in comments
Le 24/02/2015 15:37, Nicolas Goaziou a écrit : Nicolas Richard theonewiththeevill...@yahoo.fr writes: In AUCTeX, it is mainly about filling and indentation, but in Org it could mean let the usual (interactive) commands pretend we're not in a comment. If Org is to adopt such a variable, it could fontify according to what the interactive commands will do. This is orthogonal to the current problem. `org-open-at-point' already pretends it is not in a comment, but the OP is asking for special fontification. I was suggesting to put these two worms in the same can, which could be opened by turning org-syntactic-comments-mode on, where all the hideous special-casing could be done instead of the org core. Would that be acceptable ? It could be made a minor mode. I don't know what are the usual (interactive) commands, so I cannot tell. Tbh, I'm not sure what the others are either. Maybe links are the only syntactic elements which make sense inside comments, so there isn't anything else beyond org-open-at-point. If that is the case, I'm just making noise for no reason -- sorry about that. Nicolas.
[O] [ox-odt] optimal width of tables
Hi, Libreoffice has a nice feature called AutoFit → Optimal width of columns. This seems to minimized the width of tables. By default Org sets the width to 100% which looks horrible for small tables. From this helpful post I gather that it can be fixed by a macro. http://ask.libreoffice.org/en/question/18664/optimal-column-width-for-all-tables-in-odt-documents/ Is there any way to call macros from ox-odt? It seems you can call LO with the -invisible flag to apply macros without bothering the user... Anybody got experience in this regard? —Rasmus -- With monopolies the cake is a lie!
Re: [O] [ODT][BUG] Custom link types in ODT footnotes
Hello, Christian Moe m...@christianmoe.com writes: custom link types created with org-add-link-type seem to no longer work in ODT footnotes. The expected output of the below example is for the bbdb link to be replaced with /nil/ (I don't have Stallman in my address book) and for SCREAMING LINK to be upcased if you've executed the source block. This works in both body text and footnote for HTML export, but only in body text, not footnote, for ODT. --- Example: #+title: Test of custom link types in footnotes This is a bbdb:R.*Stallman link.[fn:1] #+begin_src emacs-lisp (org-add-link-type scream nil (lambda (path desc format) (upcase desc))) #+end_src This is a silly [[scream:234][screaming link]] for testing.[fn:2] * Footnotes [fn:1] This is a bbdb:R.*Stallman link in a footnote. [fn:2] This is a silly [[scream:234][screaming link]] in a footnote. This should be fixed. Thank you. Regards, -- Nicolas Goaziou
Re: [O] FR: Fontify links even when in comments
On 2015-02-24 at 07:53, Nicolas Richard theonewiththeevill...@yahoo.fr wrote: Nicolas Goaziou m...@nicolasgoaziou.fr writes: They cannot contain link, nor anything else. However, the feature you describe above was deemed useful enough that `org-open-at-point' sloppily opens anything looking like a link (or a timestamp) within a comment. However, there is, per syntax, no link there, and I don't think it should be fontified. AUCTeX has a variable named `LaTeX-syntactic-comments' : , | User option: If non-nil comments will be handled according to LaTeX |syntax. ` In AUCTeX, it is mainly about filling and indentation, but in Org it could mean let the usual (interactive) commands pretend we're not in a comment. If Org is to adopt such a variable, it could fontify according to what the interactive commands will do. Would that be acceptable ? It could be made a minor mode. It would certainly be acceptable to me... -k.
Re: [O] scale inline images in orgmode
Hello,
This setting works fine:
(setq org-image-actual-width 300)
= always resize inline images to 300 pixels
However, this does not {it falls back to 400 and ignores #+ATTR}:
(setq org-image-actual-width '(400))
= if there is a #+ATTR.*: width=200, resize to 200,
otherwise resize to 400
I tried different versions of #+ATTR, including:
##+ATTR.*: :width 150px
##+ATTR.*: width=100
##+ATTR_HTML: :width 300px
#+ATTR_HTML: :width=100
Any idea what’s wrong?
[O] [ODT][BUG] Custom link types in ODT footnotes
Hi, custom link types created with org-add-link-type seem to no longer work in ODT footnotes. The expected output of the below example is for the bbdb link to be replaced with /nil/ (I don't have Stallman in my address book) and for SCREAMING LINK to be upcased if you've executed the source block. This works in both body text and footnote for HTML export, but only in body text, not footnote, for ODT. --- Example: #+title: Test of custom link types in footnotes This is a bbdb:R.*Stallman link.[fn:1] #+begin_src emacs-lisp (org-add-link-type scream nil (lambda (path desc format) (upcase desc))) #+end_src This is a silly [[scream:234][screaming link]] for testing.[fn:2] * Footnotes [fn:1] This is a bbdb:R.*Stallman link in a footnote. [fn:2] This is a silly [[scream:234][screaming link]] in a footnote. Yours, Christian
Re: [O] FR: Fontify links even when in comments
Nicolas Richard theonewiththeevill...@yahoo.fr writes: In AUCTeX, it is mainly about filling and indentation, but in Org it could mean let the usual (interactive) commands pretend we're not in a comment. If Org is to adopt such a variable, it could fontify according to what the interactive commands will do. This is orthogonal to the current problem. `org-open-at-point' already pretends it is not in a comment, but the OP is asking for special fontification. Would that be acceptable ? It could be made a minor mode. I don't know what are the usual (interactive) commands, so I cannot tell. However, it sounds like a can of worms, and should probably be done on a case by case basis, like `org-open-at-point' currently does. Regards,
Re: [O] [RFC] [PATCH] Changes to Tag groups - allow nesting and regexps
Gustav Wikström gustav.e...@gmail.com writes:
Hi again! The FSA-assignment is now complete. New patches are attached
and comments below.
OK. I updated list of contributors accordingly.
The reason for the use of [ ] is because { } already has another purpose
- it is used to make the tags within { } exclusive.
this example
,
| #+TAGS: { group : include1 include2 }
`
will only allow one of the tags on any specific headline. [ ] solves
this. Note that grouptags doesn't care if { } or [ ] is used. The only
difference is the exclusiveness. I.e both
,
| #+TAGS: [ group : include1 include2 ]
| #+TAGS: { group : include1 include2 }
`
will work. With some limitations on the second example due to the way {
} works since before.
OK, but is it really needed? What is the point of having two tags of the
same group (or, if we consider nested group tags, the same set of
siblings) at the same time?
Subject: [PATCH 1/3] org: Grouptags not unique and can contain regexp
* lisp/org.el (org--setup-process-tags):
(org-fast-tag-selection):
Grouptags had to previously be defined with { }. This syntax is
already used for exclusive tags and Grouptags need their own,
non-exclusive syntax. This behaviour is achieved with [ ]
instead. Note: { } can still be used also for Grouptags but then
only one of the given tags can be used on the headline at the same
time. Example:
You need to separate sentences with two spaces. Also, commit messages
need to be formatted this way
* lisp/org.el (function): Small description.
(other function): Small description.
Long explanations.
-(org-re \\`\\([[:alnum:]_@#%]+\\)\\(?:(\\(.\\))\\)?\\') e)
+(org-re (concat \\`\\([[:alnum:]_@#%]+
+\\|{.+}\\) ; regular expression
^^^
I think it should be non-greedy above.
+ (taggroups (or org-tag-groups-alist-for-agenda
org-tag-groups-alist))
+ (taggroups (if downcased (mapcar (lambda(tg) (mapcar 'downcase
tg)) taggroups) taggroups))
Nitpick:
(lambda (tg) ... #'downcase ...)
Also it should be wrapped at 80 characters.
+ (taggroups-keys (mapcar 'car taggroups))
Nitpick: (mapcar #'car taggroups)
+ (return-match (if downcased (downcase match) match))
+ (count 0)
+ regexps-in-match tags-in-group regexp-in-group
regexp-in-group-escaped)
;; @ and _ are allowed as word-components in tags
(modify-syntax-entry ?@ w stable)
(modify-syntax-entry ?_ w stable)
- (while (and tml
+ ;; Temporarily replace regexp-expressions in the match-expression
Nitpick: missing full stop.
+ (while (string-match {.+?} return-match)
+ (setq count (1+ count))
Nitpick:
(incf count)
+ (setq regexps-in-match (cons (match-string 0 return-match)
regexps-in-match))
Nitpick:
(push (match-string 0 return-match) regexps-in-match)
+ (setq return-match (replace-match (concat (number-to-string
count) ) t nil return-match)))
Nitpick:
(format %d count)
+ ; Filter tag-regexps from tags
+ (setq regexp-in-group-escaped (delq nil (mapcar (lambda (x)
+ (if (stringp x)
+ (and
(string-prefix-p { x)
+
(string-suffix-p } x)
+ x)
+ x))
tags-in-group))
We cannot use `string-prefix-p' and `string-suffix-p' due to backward
compatibility. The former will be fine in Org 8.4 (it was introduced in
Emacs 24.1), but the latter comes from Emacs 24.4.
You can use (equal (substring x ... ...) ...) instead.
Be careful about line width, too.
+ tags-in-group (delq nil (mapcar (lambda (x)
+ (if (stringp x)
+ (and (not
(string-prefix-p { x))
+(not
(string-suffix-p } x))
+x)
+ x)) tags-in-group)))
Ditto.
+ ; If single-as-list, do no more in the while-loop...
+ (if (not single-as-list)
+ (progn
+ (if regexp-in-group
+ (setq regexp-in-group (concat \\| (mapconcat
'identity regexp-in-group \\|
+ (setq tags-in-group (concat dir {\\ (regexp-opt
tags-in-group) regexp-in-group \\}))
+ (if (stringp tags-in-group) (org-add-props tags-in-group
'(grouptag t)))
Nitpick: (when (stringp tags-in-group) ...)
+ (setq return-match (replace-match tags-in-group t t
[O] Using org-mode to create an on-line manual for a software product
Hi! I've been using Org-mode for creating an administration manual and user guide for a software product in the company I work. I output the manual to latex (nearly 170 pages). The thought occurs to me that it might be possible to publish it to html for use as an on-line manual that could be invoked from within the application. Ideally it would be useful to be able to open the relevant section in the manual in a browser. Does anyone have practical experience, or suggestions of implementing such a solution with org-mode? The software application runs in a CentOS 6.X environment Regards, Ciaran Mulloy
Re: [O] [ODT][BUG] Custom link types in ODT footnotes
Hi, I confirm it's fixed. Thanks! That was fast. Yours, Christian Nicolas Goaziou writes: Hello, Christian Moe m...@christianmoe.com writes: custom link types created with org-add-link-type seem to no longer work in ODT footnotes. The expected output of the below example is for the bbdb link to be replaced with /nil/ (I don't have Stallman in my address book) and for SCREAMING LINK to be upcased if you've executed the source block. This works in both body text and footnote for HTML export, but only in body text, not footnote, for ODT. --- Example: #+title: Test of custom link types in footnotes This is a bbdb:R.*Stallman link.[fn:1] #+begin_src emacs-lisp (org-add-link-type scream nil (lambda (path desc format) (upcase desc))) #+end_src This is a silly [[scream:234][screaming link]] for testing.[fn:2] * Footnotes [fn:1] This is a bbdb:R.*Stallman link in a footnote. [fn:2] This is a silly [[scream:234][screaming link]] in a footnote. This should be fixed. Thank you. Regards,
Re: [O] [ox-odt] optimal width of tables
Rasmus ras...@gmx.us writes: Libreoffice has a nice feature called AutoFit → Optimal width of columns. This seems to minimized the width of tables. By default Org sets the width to 100% which looks horrible for small tables. From this helpful post I gather that it can be fixed by a macro. http://ask.libreoffice.org/en/question/18664/optimal-column-width-for-all-tables-in-odt-documents/ Is there any way to call macros from ox-odt? It seems you can call LO with the -invisible flag to apply macros without bothering the user... So the particular problem can be solved using this macro under OrgMacros: REM * BASIC * Sub OptimzeColumnWidth Dim s As String Dim i As Long Dim oTables Dim oTable Dim oCell oTables = ThisComponent.getTextTables() If NOT oTables.hasElements() Then Exit Sub For i = 0 To oTables.getCount() - 1 oTable = oTables.getByIndex(i) ThisComponent.getCurrentController().select(oTable) oFrame = ThisComponent.CurrentController.Frame oDispHelper = createUnoService(com.sun.star.frame.DispatchHelper) oDispHelper.executeDispatch(oFrame, .uno:SelectTable, , 0, Array()) oDispHelper.executeDispatch(oFrame, .uno:SetOptimalColumnWidth, , 0, Array()) Next End Sub Sub OptimizeColumnWidtSaveQuit OptimzeColumnWidth() ThisComponent.store() ThisComponent.close(True) StarDesktop.Terminate end Sub I couldn't figure out how to make comments in LO Basic, so that's why there's not a back-reference to the url above... It's called via libreoffice --invisible --nofirststartwizard --headless --norestore MYFILE.odt macro:///Standard.OrgMacros.OptimizeColumnWidtSaveQuit() This is Makefile-friendly (and ox-publish), but it would be great if we could (i) collect some useful macros like the above, and (ii) provide an convenient way to call them on exported documents. —Rasmus -- Need more coffee. . .
[O] 8.3 git head new math $ behavior
I've started running the git head version of Org mode, since 8.3 has some features I'm interested in that were not in the version I was previously using (the latest on elpa). Is this list an appropriate place to as questions or mention bugs I find in 8.3, or is there a better place for that? I write because in the new version $x$ exports to latex as before, but ($x$) does not. It exports as seen, including the dollar sign. ($$x$$) does export as math. Is this an intentional changed behavior? Or some regex exporter bug that I've come across? -k.
[O] [bug] links in macros comments are fortified
Hi, Consider the following macro that I'm employing hoping to export a document as a odt (the document is optimized towards latex). #+MACRO: tikzgraph (eval (format [[file:$1.%s]] (if (org-export-derived-backend-p org-export-current-backend 'latex) tikz png))) In org this was displayed as #+MACRO: tikzgraph (eval (format file:$1.%s (if (org-export-derived-backend-p org-export-current-backend 'latex) tikz png))) Which let me to type #+MACRO: tikzgraph (eval (format file:$1.%s (if (org-export-derived-backend-p org-export-current-backend 'latex) tikz png))) Which gave a funky output that I fortunately found. At least in macros, links should not be formatted IMO. —Rasmus -- However beautiful the theory, you should occasionally look at the evidence
Re: [O] Citation syntax and ODT
Thomas S. Dye writes:
AFAIK, the only software that has proposed a solution to the
problem of maintaining a citation database that can support the
universe of citation styles developed in the wild is BibLaTeX.
Well with BibTeX alone you can maintain a citation database and to
support any citation style, you just:
reverse polish notation
know?
'skip
{reverse polish notation learn}
if
citation style
write
--
Jorge.
Re: [O] [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t
John Kitchin jkitc...@andrew.cmu.edu writes: Fabulous! Thanks! BTW, #+BEGIN_SRC emacs-lisp '((a (b))) #+END_SRC #+RESULTS: foo | a | (b) | Shouldn't we also return lists deeper than 2 levels as strings? Does it even make sense to try formatting them into a table? Regards,
Re: [O] Embedding diagrams in Org
On Tue, 24 Feb 2015, Eric S Fraga wrote: On Tuesday, 24 Feb 2015 at 01:01, Marcin Borkowski wrote: [...] I have one question. #+begin_src latex :results latex raw :exports results Why :results latex raw and not :results latex? I have no idea ;-) I find, unfortunately, that getting babel to do what I want is somewhat of an arcane art (for me) so once I get something doing what I want it to do, I leave things alone... `:results latex raw' is equivalent to `:results raw'. If you try C-c C-v C-i in your src block, you will get , | Lang: latex | Properties: | :header-argsnil | :header-args:latex nil | Header Arguments: | :cache no | :exportsresults | :hlines no | :noweb no | :resultsraw replace | :sessionnone | :tangle no ` So the result is processed by the exporter as `raw', which works ok as long as the exporter leaves the latex alone --- as in your case. But sometimes is not what you want. For example, a naked ~tildes~ will be marked up as \verb~tildes~ under `:results raw' or `:results latex raw', and as ~tildes~ under `:results latex'. I'm sure it all makes sense but it's probably a case of my not having the time to figure things out properly. When I need to get something done, it's often because I need it *now* (or yesterday :-). Been there, too. Chuck
Re: [O] [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t
I don't have a strong opinion on this. My sense is if you get a table it is fine, if not, you should get a string. Most important to me is no error. Of second importance is usability of the result. If I add this after the block, it works as expected for me, so the current behavior seems ok to me. #+BEGIN_SRC emacs-lisp :var d=foo :results code d #+END_SRC I am not actually sure if a string is usable, without a read statement for emacs-lisp. Nicolas Goaziou writes: John Kitchin jkitc...@andrew.cmu.edu writes: Fabulous! Thanks! BTW, #+BEGIN_SRC emacs-lisp '((a (b))) #+END_SRC #+RESULTS: foo | a | (b) | Shouldn't we also return lists deeper than 2 levels as strings? Does it even make sense to try formatting them into a table? Regards, -- 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] 8.3 git head new math $ behavior
Ken Mankoff mank...@gmail.com writes: I write because in the new version $x$ exports to latex as before, but ($x$) does not. It exports as seen, including the dollar sign. ($$x$$) does export as math. As far as I recall it's a feature. I think there's a discussion with this exact example a way back, but it's hard to search for... $·$ happens to work sometimes. \(·\) Should work unambiguously. —Rasmus -- Slowly unravels in a ball of yarn and the devil collects it
[O] [PATCH] was Re: [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t
On Tue, 24 Feb 2015, Nicolas Goaziou wrote:
John Kitchin jkitc...@andrew.cmu.edu writes:
Fabulous! Thanks!
BTW,
#+BEGIN_SRC emacs-lisp
'((a (b)))
#+END_SRC
#+RESULTS: foo
| a | (b) |
Shouldn't we also return lists deeper than 2 levels as strings? Does it
even make sense to try formatting them into a table?
My vote is no - it doesn't make sense. Let the user pick `:results list'
or `:results pp' after it returns a string.
BTW, the string produced when a list cannot be rendered as a table ought
to be removable.
The patch makes such strings removable. i.e.
#+BEGIN_SRC emacs-lisp
org-babel-load-languages
#+END_SRC
will have the : prefix or #+begin/end_example delimiters to allow later
removal like this:
#+RESULTS:
: ((R . t) (latex . t) ... (sql) ...
HTH,
ChuckFrom b1179a79c6d72cc0beab6e7fd9774f49ea1bbbae Mon Sep 17 00:00:00 2001
From: Charles Berry ccbe...@ucsd.edu
Date: Tue, 24 Feb 2015 15:12:53 -0800
Subject: [PATCH] ob-core.el: examplify list made into strings
* ob-core.el (org-babel-insert-result): When a list cannot be rendered
as a table and is turned into a string make it removable if
`:results replace' (the default) or `:results table' was specified.
---
lisp/ob-core.el | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index f2062ef..4be10c1 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -2299,7 +2299,10 @@ INFO may provide the values of these header arguments
(in the
{{{results( )}}}))
((and inlinep (member file result-params))
(funcall wrap nil nil nil nil {{{results( )}}}))
-((and (not (funcall proper-list-p result))
+((and (not (and (funcall proper-list-p result)
+ (org-every (lambda (e)
+(or (atom e) (funcall proper-list-p
e)))
+ result)))
(not (member file result-params)))
(let ((org-babel-inline-result-wrap
;; Hard code {{{results(...)}}} on top of
customization.
--
1.9.3 (Apple Git-50)
Re: [O] Key-binding to a command with prefix argument
On 2015-02-25, at 00:24, Giacomo M jackja...@gmail.com wrote: Dear all, I started using more frequently C-u C-c C-x tab, which offers a list of recently clocked tasks to clock into. I already assigned f11 to org-clock-in, but how can I assign (let say) C-f11 to org-clock-in with a prefix argument? What about (defun org-clock-in-recent () Clock in a recently clocked task. (interactive) (org-clock-in '(4))) (global-set-key (kbd C-f11) #'org-clock-in-recent) ? BTW, I seldom use C-c C-x tab - I prefer C-c C-x C-i. Also, you might want to read this: http://mbork.pl/2013-05-25_Clocking_in_from_anywhere_%28en%29 Thanks, Giacomo Hth, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] Citation syntax: a revised proposal
On Wednesday 25 February 2015 09:59 AM, Richard Lawrence wrote: Vaidheeswaran Cvaidheeswaran.chinnar...@gmail.com writes: If you need help with ODT/JabRef integration, I am willing to lend a hand. (Only thing is) I would expect that someone hand-hold me wrt what one wants in the final exporter on a case-by-case basis. I would rather build bottom-up, rather than top-down. That's great, thanks! I don't know if JabRef will be a/the tool we eventually want to `bless'...from what you say, it sounds more limited than Zotero, though I don't know because I haven't personally used either...but it's nice to have volunteers! I agree that we should go for the best tool chain that is available. I wish you success with your new initiative. Do write to me if you ever feel that JabRef-based workflow will be of some interest to you with your document production needs.
Re: [O] Key-binding to a command with prefix argument
On Tue, Feb 24, 2015 at 4:15 PM, Marcin Borkowski mb...@wmi.amu.edu.pl wrote: On 2015-02-25, at 00:24, Giacomo M jackja...@gmail.com wrote: Dear all, I started using more frequently C-u C-c C-x tab, which offers a list of recently clocked tasks to clock into. I already assigned f11 to org-clock-in, but how can I assign (let say) C-f11 to org-clock-in with a prefix argument? What about (defun org-clock-in-recent () Clock in a recently clocked task. (interactive) (org-clock-in '(4))) (global-set-key (kbd C-f11) #'org-clock-in-recent) ? Thanks Marcin, indeed it worked as expected. BTW, I seldom use C-c C-x tab - I prefer C-c C-x C-i. Do C-c C-x tab and C-c C-x C-i call the same command? My system doesn't seem to distinguish the two. How could I distinguish them and why should I prefer one instead of the other? Also, you might want to read this: http://mbork.pl/2013-05-25_Clocking_in_from_anywhere_%28en%29 Thanks, interesting. Apparently org-clock-in-recent seems to work already from anywhere. Giacomo Hth, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] Using org-mode to create an on-line manual for a software product
Another hosted service that uses markdown (not org-mode) http://readthedocs.org/ On 2/24/2015 8:38 PM, Melanie Bacou wrote: Ciaran Have a look at ox-twbs in MELPA https://github.com/marsmining/ox-twbs. This will publish your org files to HTML with Twitter Bootstrap CSS support that you can customize. There's also https://github.com/fniessen/org-html-themes --Mel. On 2/24/2015 9:55 AM, ciaran_mulloy wrote: Hi! I've been using Org-mode for creating an administration manual and user guide for a software product in the company I work. I output the manual to latex (nearly 170 pages). The thought occurs to me that it might be possible to publish it to html for use as an on-line manual that could be invoked from within the application. Ideally it would be useful to be able to open the relevant section in the manual in a browser. Does anyone have practical experience, or suggestions of implementing such a solution with org-mode? The software application runs in a CentOS 6.X environment Regards, Ciaran Mulloy -- Melanie BACOU International Food Policy Research Institute Snr. Program Manager, HarvestChoice E-mail m.ba...@cgiar.org Visit www.harvestchoice.org
[O] Key-binding to a command with prefix argument
Dear all, I started using more frequently C-u C-c C-x tab, which offers a list of recently clocked tasks to clock into. I already assigned f11 to org-clock-in, but how can I assign (let say) C-f11 to org-clock-in with a prefix argument? Thanks, Giacomo
Re: [O] Using org-mode to create an on-line manual for a software product
Ciaran Have a look at ox-twbs in MELPA https://github.com/marsmining/ox-twbs. This will publish your org files to HTML with Twitter Bootstrap CSS support that you can customize. There's also https://github.com/fniessen/org-html-themes --Mel. On 2/24/2015 9:55 AM, ciaran_mulloy wrote: Hi! I've been using Org-mode for creating an administration manual and user guide for a software product in the company I work. I output the manual to latex (nearly 170 pages). The thought occurs to me that it might be possible to publish it to html for use as an on-line manual that could be invoked from within the application. Ideally it would be useful to be able to open the relevant section in the manual in a browser. Does anyone have practical experience, or suggestions of implementing such a solution with org-mode? The software application runs in a CentOS 6.X environment Regards, Ciaran Mulloy -- Melanie BACOU International Food Policy Research Institute Snr. Program Manager, HarvestChoice E-mail m.ba...@cgiar.org Visit www.harvestchoice.org
Re: [O] [ox-latex, bug?] :caption forces environment
Nicolas Goaziou m...@nicolasgoaziou.fr writes: Rasmus ras...@gmx.us writes: AFAIK, we use float actively at one place, namely ;; Case 1. No source fontification. Of org-latex-src-block. In that particular case I guess we could also use capt-of, actually. It's worth trying. Do you want to provide a patch? Yeah, I started already, but so far only tables works, but I'm really busy ATM with funding applications. [BTW: For one I need to send a .doc. I'm getting random crashes with ox-odt as well (as Eric), but I haven't been able to track it down...] At some point I wanted to get rid of float, until I became aware that capt-of doesn't ensure that floats/non-floats appear in the right order. Since we wouldn't use floats anymore, this isn't a problem, is it? Well the problem is that you can get unorder. E.g. the following where I don't know if the syntax is valid. Table 1 can be printed midway on the page, and table 2 can be printed on top of the page, but table 2 would actually be called Table 2. I haven't tested this thoroughly though. Text #+Attr_latex: :float nil | 1 | Text #+Attr_latex: :float t :options [t] | 2 | —Rasmus -- El Rey ha muerto. ¡Larga vida al Rey!
[O] Here is a patch I want to add to org.el……
But how to do it？ Besides， I‘m glad to view your opinions，so here comes the codes： The place：(defun org-ctrl-c-ctrl-c the first (cond add： (cond ((overlayp (car (overlays-at (point (let ((overlay (car (overlays-at (point) (if (overlayp overlay) (delete-overlay overlay) ))) so that I won’t make all overlays disappear at only once “C-c C-c” Sent from Windows Mail
Re: [O] Citation syntax: a revised proposal
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes: If you need help with ODT/JabRef integration, I am willing to lend a hand. (Only thing is) I would expect that someone hand-hold me wrt what one wants in the final exporter on a case-by-case basis. I would rather build bottom-up, rather than top-down. That's great, thanks! I don't know if JabRef will be a/the tool we eventually want to `bless'...from what you say, it sounds more limited than Zotero, though I don't know because I haven't personally used either...but it's nice to have volunteers! Best, Richard
