Re: [O] [PATCH]: BUG fix and Add header-args property to source block info
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Rainer M Krug wrote: what do you mean by ECM? http://orgmode.org/worg/org-faq.html#ecm Ah - learned something. Merci beaucoup, Rainer Best regards, Seb -- Rainer M. Krug email: Raineratkrugsdotde PGP: 0x0F52F982 signature.asc Description: PGP signature
Re: [O] closing column mode for beamer export
On Friday, 13 Feb 2015 at 02:09, James Harkins wrote: [...] Again, this is a hack. I was weaned on IBM S/370 assembler language so hack is what I do ;-) Beamer export has the :B_columns: tag for exactly this purpose. Indeed and thanks for highlight this as I had forgotten about this property. I find it less æsthetically pleasing. YMMV, of course. The beauty of org is that there are so many ways of accomplishing a given task. Thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-820-gd92ef9
Re: [O] [PATCH]: BUG fix and Add header-args property to source block info
Rainer M Krug wrote: what do you mean by ECM? http://orgmode.org/worg/org-faq.html#ecm Best regards, Seb -- Sebastien Vauban
Re: [O] Announcement: org-one-to-many
Hello Marcin, Marcin Borkowski wrote: so I've got this little library of mine, called org-one-to-many, which can split an Org file into pieces, modifying internal links so that they still point to the same place (even if now in another file). But I have a problem with it. I would like to export all the resulting files into, say, HTML, and the problem is that all the options (obviously) don't propagate to the “subfiles” [...] Maybe you've already explained it, but it's not clear to me whether you really cut one big Org file into smaller ones (once and for all) or you simply export one big Org file into different HTML ones. Can you restate it? Best regards, Seb -- Sebastien Vauban
Re: [O] How to obtain the list of files included in HTML export?
Marcin Borkowski wrote: the subject pretty much says it all. Apart from the HTML file itself there might be inlined images and bitmaps of equations. Since I'd like to make my customized exporter create a self-contained zip file, I need the list of all files comprising the generated web page. Don't forget about CSS (and what about if CSS is on some remote server: do you take a copy of it?) and, worse of all, external elements of CSS (such as: LI bullets replaced by a GIF file)... Best regards, Seb -- Sebastien Vauban
Re: [O] [PATCH]: BUG fix and Add header-args property to source block info
Nicolas Goaziou m...@nicolasgoaziou.fr writes: Rainer M Krug rai...@krugs.de writes: I think I will skip the bonus points this time - sorry. OK. You may also send me a couple of ECM, so I can turn them into tests. Sorry - what do you mean by ECM? I would be very grateful if you could submit the patch without a test. Applied. Thank you. Thanks, Rainer Regards. -- Rainer M. Krug email: Raineratkrugsdotde PGP: 0x0F52F982 signature.asc Description: PGP signature
[O] org-carddav [was: Re: ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.]
On Wed 21 January 2015, Rasmus wrote: Gour address@hidden writes: On Sub, 2014-08-02 at 11:12 +1000, Alexis wrote: 2. Using org-vcard as a library, create org-carddav (which i hope to start working on shortly) in order to be able to synchronise contacts stored in Org with arbitrary CardDAV servers. Cool stuff! Sorry i've not replied to this sooner; i've had a lot happening, and haven't been able to follow this list. Unfortunately my work on org-carddav got stymied at an early stage by this Emacs issue: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18290 Iirc, this not only presented an obstacle to interaction with Google's CardDAV service, but also with a DAViCal server i set up on my LAN. If someone familiar with the source of url-http.el reviewed this, and amended its code along the lines i suggested in my bug report - even if only in the Emacs master branch - i would happily resume working on org-carddav. :-) Alexis.
Re: [O] Colon in block name?
On Friday, 13 Feb 2015 at 08:49, Loris Bennett wrote: [...] In my ECM and in my original posting there are no empty lines between the table information and the actual table (see attached screenshot of my original ECM). However, I can see that in your quoted version above there is one. Ummm, interesting. The way to avoid this issue may be to actually attach a file instead of pasting the contents into the email. Can you attach your ECM so that we can see what happens with it? -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-727-ga1cdc6.dirty
[O] Org Babel code blocks in COMMENT subtrees gets executed!?
Save this as and Org file, and press C-c C-v C-e... --8---cut here---start-8--- * Intro #+begin_src emacs-lisp (print Foo) #+end_src * COMMENT Method #+begin_src emacs-lisp (print Bar) #+end_src ^ I don't think we should have blocks in COMMENT trees executed, right? Isn't that supposed to be (one of) the difference(s) between :noexport: and COMMENT? * Results #+begin_src emacs-lisp (print Baz) #+end_src --8---cut here---end---8--- Best regards, Seb -- Sebastien Vauban
[O] Orgmode → ODT: Certain chars break export
While we're on the topic of ODT export problems: I was in the process of converting PDF to Text to Org to ODT/DocX and discovered that certain characters seem to break exported odt documents, which fail with a line and col number. So far the only one I know for sure is the (Char: C-l (12, #o14, #xc)). Hopefully a single fix can handle all such cases. You probably don't need it, but I verified with the following file: http://toryanderson.com/files/breakorg.org Org-mode version 8.2.10 (8.2.10-32-gddaa1d-elpa)
Re: [O] Colon in block name?
Eric S Fraga e.fr...@ucl.ac.uk writes: On Friday, 13 Feb 2015 at 08:49, Loris Bennett wrote: [...] In my ECM and in my original posting there are no empty lines between the table information and the actual table (see attached screenshot of my original ECM). However, I can see that in your quoted version above there is one. Ummm, interesting. The way to avoid this issue may be to actually attach a file instead of pasting the contents into the email. Can you attach your ECM so that we can see what happens with it? * Test with block names containing a colon ** Data My data can be found in Table [[tab:my_data]]. #+CAPTION: My data #+NAME: tab:my_data | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Code My code can be found in Listing [[code:my_code]]. #+CAPTION: My code #+NAME: code:my_code #+HEADER: :var data=tab:my_data :colnames yes #+BEGIN_SRC R d - data #+END_SRC ** Results My results can be found in Table [[tab:my_results]]. #+CAPTION: My results #+NAME: tab:my_results #+RESULTS: code:my_code | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Conclusions Names with colons don't work. -- This signature is currently under construction.
Re: [O] Colon in block name?
Loris Bennett loris.benn...@fu-berlin.de writes: Eric S Fraga e.fr...@ucl.ac.uk writes: On Friday, 13 Feb 2015 at 08:49, Loris Bennett wrote: [...] In my ECM and in my original posting there are no empty lines between the table information and the actual table (see attached screenshot of my original ECM). However, I can see that in your quoted version above there is one. Ummm, interesting. The way to avoid this issue may be to actually attach a file instead of pasting the contents into the email. Can you attach your ECM so that we can see what happens with it? * Test with block names containing a colon ** Data My data can be found in Table [[tab:my_data]]. #+CAPTION: My data #+NAME: tab:my_data | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Code My code can be found in Listing [[code:my_code]]. #+CAPTION: My code #+NAME: code:my_code #+HEADER: :var data=tab:my_data :colnames yes #+BEGIN_SRC R d - data #+END_SRC ** Results My results can be found in Table [[tab:my_results]]. #+CAPTION: My results #+NAME: tab:my_results #+RESULTS: code:my_code | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Conclusions Names with colons don't work. The above was attached with Gnus 'C-c RET f', MIME type 'text/x-org'. Reading with Gnus, I don't see any blank lines between the table info and the table itself. Just to get back to the original question: Should and does 'tab:my_data' work as a value for a variable in a source block header? I get Reference 'my_data' not found in this buffer If I replace the colon with '_', ';', or even '=', everything works as expected. Cheers, Loris -- This signature is currently under construction.
Re: [O] Orgmode → ODT: Certain chars break export
torys.ander...@gmail.com (Tory S. Anderson) writes: While we're on the topic of ODT export problems: I was in the process of converting PDF to Text to Org to ODT/DocX and discovered that certain characters seem to break exported odt documents, which fail with a line and col number. So far the only one I know for sure is the (Char: C-l (12, #o14, #xc)). Hopefully a single fix can handle all such cases. You probably don't need it, but I verified with the following file: http://toryanderson.com/files/breakorg.org The export is fine, but the produced XML is invalid since it contains an illegal character. But how to resolve this? Should ox strip illegal charterers (if so what are they)? If so, could they be used for entities? —Rasmus -- I hear there's rumors on the, uh, Internets. . .
Re: [O] org-carddav [was: Re: ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.]
Alexis flexibe...@gmail.com writes: If someone familiar with the source of url-http.el reviewed this, and amended its code along the lines i suggested in my bug report - even if only in the Emacs master branch - i would happily resume working on org-carddav. :-) You might have a better chance finding that someone on the emacs-devel list. I hope the bug is fixed. I'd really like to see a Emacs ↔ Carddav thingy —Rasmus -- Got mashed potatoes. Ain't got no T-Bone. No T-Bone
[O] (org-use-fast-tag-selection (quote auto)) - problem with TAB Completion and non ASCII tag selection characters [\200]
I have
one
persistent tag
set with a key character like this:
'(org-tag-persistent-alist (quote ((a . 97
There are no file based #+TAGS in any of org files.
I also like to have access to all tags in all files, so I set this up:
(org-complete-tags-always-offer-all-agenda-tags t)
Finally I'd like to have a fast selection splash screen:
(org-use-fast-tag-selection (quote auto))
Now the problems:
1.
Running C-q in an org file on a heading shows a fast selection splash window
.
It shows all the tags from all the org files.
The main problem is that
apart from [a] defined in org-tag-persistent-alist other characters are
assigned
for
fast pick
randomly
and
are not only 'a-z', but also
seemingly
non-ASCII characters which are shown as:
- [\200] tagname1
- [\204] tagname2
- etc
There seems to be no way to select tagname1 or tagname2.
2. With all the above variables unchanged hitting the TAB here for
selection of tags in the minibuffer only allows tags already in the file,
ignoring the (org-complete-tags-always-offer-all-agenda-tags t) variable.
Disabling
'
org-use-fast-tag-selection
' by setting it
to
'nil'
and hitting TAB after C-q
produces ':' and the Completions buffer is not opened. However, typing a
first character of a tag, say 'b' and hitting TAB opens 'Completions'
buffer and lists all tags starting with 'b'
.
Note that org ido completion (which would be shown as 'Ido Completions'
buffer name) is not used although (org-completion-use-ido t) if
(org-use-fast-tag-selection (quote
nil
))
.
3.
I
n addition to problem 1., and problem 2., TAB does not show a full list of
tags in the Completions buffer
which start with 'a' {probably due to the tag 'a'
defined above}, but selecting another starting letter and hitting TAB opens
Completion buffer with all tags starting with 'b'
.
So, fast select seems broken.
I would expect it behave like this:
1. having (org-complete-tags-always-offer-all-agenda-tags t) and
(org-use-fast-tag-selection (quote auto)) should limit the tags selection
to ASCII only characters or offer double character selection like [aa]-[zz]
if there are more tags that az permits. Use numbers perhaps too?.
2. If 1. is not possible then perhaps limit the characters to
'
a
-
z
'
and leaving other tags out of the fast select but allow TAB to choose all
tags in all org files using org-ido?
I'm forced currently to disable (org-use-fast-tag-selection (quote auto))
setting it to (org-use-fast-tag-selection (quote
nil
)) and use the Completions buffer, which
seems to work more consistently.
Re: [O] Colon in block name?
Loris Bennett loris.benn...@fu-berlin.de writes: The above was attached with Gnus 'C-c RET f', MIME type 'text/x-org'. But you attached it as inline, so the same problems could arise. To be sure to transfer the file unmodified, choose attachment as disposition. Reading with Gnus, I don't see any blank lines between the table info and the table itself. It depends on your Gnus configuration. If you set (setq gnus-inhibit-mime-unbuttonizing t) then at least my version of Gnus (v5.13) does indeed split the buffer in multiple pieces with additional newlines. -- Until the next mail..., Stefan.
Re: [O] How to include time when generating timestamp for DEADLINE/SCHEDULE
On 02/12/2015 07:37 PM, Yuri Niyazov wrote: PS It is clear that you can *both* select the correct date using calendar, and *then* type in the time while still in the calendar selector, right? On Thu, Feb 12, 2015 at 5:36 PM, Yuri Niyazov yuri.niya...@gmail.com wrote: On Thu, Feb 12, 2015 at 4:16 PM, Subhan Michael Tindall subh...@familycareinc.org wrote: Not really an acceptable answer. Having to use 2 different interface methods to fill in one time/date stamp value is confusing and cludgy. Plus, if you type in a full time/date stamp + time, you can still move around in the calendar, but it doesn't update the selected datestamp in yellow. Also confusing. Cludgy is in the eye of the beholder. I am hugely bothered by various inconsistencies in org-mode user interface (see my other posts to this list) but this one is very far down on the list. This is why: When I need to schedule a date, it is sufficiently close to today's date that it is usually 2-3 S+ARROWS keystrokes away from today, so the calendar with today selected as default is great. So, let's see how a time selector would work: When you bring up a time selector, it could by default show one of the following three options: 1) The current time 2) The last time you selected when you used the time selector 3) Some default configurable time like noon When I need to schedule a time for an event, the time that something needs to happen is usually not related to any times on that list, so using S+ARROWS would be less efficient than typing out the time, which is at most four keystrokes if its on the hour. (E.g. 10pm ). Of course, this is only true if you are a touch-typist. Why bother with the arrow keys at all? I have a capture template for appointments and deadlines which requests date and time. Calendar is called. Rather than arrow keys I type the datespacetime (optional duration) and then enter - e.g. call the template, then 2/28 13:30 (and then enter the rest of template requests such as 'What has to be done Charlie Millar Charlie Millar
Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'
Hello, Christian Moe m...@christianmoe.com writes: Would it make sense to be able to link to a footnote label? Rationale: 1. If a footnote definition is already meaningfully labeled, a dedicated target is redundant. 2. Since you can link to named tables, source blocks etc., users might expect to be able to do the same with labeled footnote definitions. So given a link like [[labeledfootnote]], could Org-mode look for a footnote definition with that label -- e.g. after looking for a dedicated target or a #+name'd element, and before doing a text search? Or is there a reason why it shouldn't? First and foremost, mixing links and footnotes would be a maintenance burden. The link-target association does just that, and I think it is sufficient. Also, Org can renumber automatically footnotes, so it should also check every link in the buffer to possibly update it. I think it's a false good idea. Regards, -- Nicolas Goaziou0x80A93738
Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes: Allow me to revisit this thread in a week or 10 days so that I can 1. take a look at ODF standard. 2. dig in to LibreOffice discussion lists to see whether such instances have ever surfaced (and how they were dealt with). Until then, please keep the patch in waiting. Too late. Having slept over your idea, I think you're right. We should extend footnote export API to provide an alternate order for tree walking, as long as footnote definitions are not ignored. This should now be fixed in master. Of course, if you find something new, we can always make further changes. Thank you. Regards,
Re: [O] How to include time when generating timestamp for DEADLINE/SCHEDULE
On 02/13/2015 08:14 AM, Charles Millar wrote: On 02/12/2015 07:37 PM, Yuri Niyazov wrote: PS It is clear that you can *both* select the correct date using calendar, and *then* type in the time while still in the calendar selector, right? On Thu, Feb 12, 2015 at 5:36 PM, Yuri Niyazov yuri.niya...@gmail.com wrote: On Thu, Feb 12, 2015 at 4:16 PM, Subhan Michael Tindall subh...@familycareinc.org wrote: Not really an acceptable answer. Having to use 2 different interface methods to fill in one time/date stamp value is confusing and cludgy. Plus, if you type in a full time/date stamp + time, you can still move around in the calendar, but it doesn't update the selected datestamp in yellow. Also confusing. Cludgy is in the eye of the beholder. I am hugely bothered by various inconsistencies in org-mode user interface (see my other posts to this list) but this one is very far down on the list. This is why: When I need to schedule a date, it is sufficiently close to today's date that it is usually 2-3 S+ARROWS keystrokes away from today, so the calendar with today selected as default is great. So, let's see how a time selector would work: When you bring up a time selector, it could by default show one of the following three options: 1) The current time 2) The last time you selected when you used the time selector 3) Some default configurable time like noon When I need to schedule a time for an event, the time that something needs to happen is usually not related to any times on that list, so using S+ARROWS would be less efficient than typing out the time, which is at most four keystrokes if its on the hour. (E.g. 10pm ). Of course, this is only true if you are a touch-typist. Why bother with the arrow keys at all? I have a capture template for appointments and deadlines which requests date and time. Calendar is called. Rather than arrow keys I type the datespacetime (optional duration) and then enter - e.g. call the template, then 2/28 13:30 (and then enter the rest of template requests such as 'What has to be done Charlie Millar Forgot to mention that with the deadline I also might enter a lead time
Re: [O] Orgmode → ODT: Certain chars break export
From a user perspective just stripping the characters seems best to me, but finding out what the characters seems obnoxious. Neither a quick search nor skimming the ODT doc specification[1][2] seem to give any insight into a set of illegal characters. Does elisp have anything similar to Java's isWhitespace[3] that could be used to check character features? Rasmus ras...@gmx.us writes: torys.ander...@gmail.com (Tory S. Anderson) writes: While we're on the topic of ODT export problems: I was in the process of converting PDF to Text to Org to ODT/DocX and discovered that certain characters seem to break exported odt documents, which fail with a line and col number. So far the only one I know for sure is the (Char: C-l (12, #o14, #xc)). Hopefully a single fix can handle all such cases. You probably don't need it, but I verified with the following file: http://toryanderson.com/files/breakorg.org The export is fine, but the produced XML is invalid since it contains an illegal character. But how to resolve this? Should ox strip illegal charterers (if so what are they)? If so, could they be used for entities? —Rasmus Footnotes: [1] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office [2] http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1415196_253892949 [3] http://www.fileformat.info/info/unicode/char/000c/index.htm
Re: [O] tasks, clocks, and notes
That is perfect! Thank you! --hymie!http://lactose.homelinux.net/~hymie hy...@lactose.homelinux.net My fitbit says I've walked 1582 steps today (as of 08:54). Subhan Michael Tindall writes: Try '(org-log-note-clock-out t) This gives you something like this: * WORK break This is my break log CLOCK: [2015-02-04 Wed 11:20]--[2015-02-04 Wed 11:30] =3D 0:10 - coffee CLOCK: [2015-02-04 Wed 09:52]--[2015-02-04 Wed 10:16] =3D 0:24 - coffee, walk CLOCK: [2015-02-03 Tue 09:35]--[2015-02-03 Tue 09:45] =3D 0:10 - walk
Re: [O] [org-drill] Suggestion to fix the drop of org-end-of-meta-data-and-drawers
Hello, Marco Wahl marcowahls...@gmail.com writes: AFAICT a possible fix is: #v+ diff --git a/contrib/lisp/org-drill.el b/contrib/lisp/org-drill.el index a0d33aa..8154904 100644 --- a/contrib/lisp/org-drill.el +++ b/contrib/lisp/org-drill.el @@ -1708,7 +1708,7 @@ Note: does not actually alter the item. (org-back-to-heading t) (let ((lim (save-excursion (outline-next-heading) (point - (org-end-of-meta-data-and-drawers) + (org-end-of-meta-data t) (or (= (point) lim) (null (re-search-forward [[:graph:]] lim t)) #v- Is it sufficient to apply this fix to master? This is correct. Thank you for taking care of it. Regards, -- Nicolas Goaziou
[O] navigating org-clock-in recent work list
As per a recent discussion on the mailing list, I'm using the following to enable persistence and extended length of the clock history: --8---cut here---start-8--- ;; Org clock-in (org-clock-persistence-insinuate) (setq org-clock-persist t) ;;; * Orgmode Modules (add-to-list 'org-modules 'habits) ;; Number of clock tasks to remember in history. (setq org-clock-history-length 35) ; 1 to 9 + A to Z --8---cut here---end---8--- It works great, with one annoying problem: now that I have a list that goes to M, it can be hard to figure out which shortcut goes to which item. I can think of two possible solutions: 1. Alternately highlight lines, or underline (spreadsheet/table style) 2. Preferably, since I use Helm, if there were simply an autocomplete prompt (like switch-buffer; no shortcut keys) this would actually be easiest. Can I disable the special pop-up screen (i.e. `org-clock-select-task') and just use an shortcut-less autocomplete prompt (which, with helm will be facilitated)?
Re: [O] Orgmode → ODT: Certain chars break export
torys.ander...@gmail.com (Tory S. Anderson) writes: From a user perspective just stripping the characters seems best to me, but finding out what the characters seems obnoxious. But maybe there is a valid way to represent such characters in XML? At the very least entities must be replaced before stripping these... Neither a quick search nor skimming the ODT doc specification[1][2] seem to give any insight into a set of illegal characters. Does elisp have anything similar to Java's isWhitespace[3] that could be used to check character features? It's an XML thing. When I tried to open the contents.xml with Firefox it also says broken XML. But I also don't know which are the characters that are not supported by XML. —Rasmus -- This space is left intentionally blank
Re: [O] Orgmode → ODT: Certain chars break export
There is a helpful wiki page now that you found XML; it even mentions my specific character.[1] The main source seems to be at the w3.org spec.[2] Rasmus ras...@gmx.us writes: torys.ander...@gmail.com (Tory S. Anderson) writes: From a user perspective just stripping the characters seems best to me, but finding out what the characters seems obnoxious. But maybe there is a valid way to represent such characters in XML? At the very least entities must be replaced before stripping these... Neither a quick search nor skimming the ODT doc specification[1][2] seem to give any insight into a set of illegal characters. Does elisp have anything similar to Java's isWhitespace[3] that could be used to check character features? It's an XML thing. When I tried to open the contents.xml with Firefox it also says broken XML. But I also don't know which are the characters that are not supported by XML. —Rasmus Footnotes: [1] https://en.wikipedia.org/wiki/Valid_characters_in_XML#XML_1.1 [2] http://www.w3.org/TR/xml11/#charsets
[O] org-time-stamp adds repeater where there is none.
Consider the following line: 2015-02-13 ven. (10h-13h) Hiting C-c . RET with point on the timestamp gives 2015-02-13 ven. -13h (10h-13h) which is not expected. Please consider the patch below From 688851438f363eaa86dcfe2acfb779d6c22adc16 Mon Sep 17 00:00:00 2001 From: Nicolas Richard theonewiththeevill...@yahoo.fr Date: Fri, 13 Feb 2015 16:57:59 +0100 Subject: [PATCH] * lisp/org.el (org-time-stamp): Restrict to timestamp when determining repeater. --- lisp/org.el | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 7c2419d..6a0e4c6 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -16149,12 +16149,13 @@ (defun org-time-stamp (arg optional inactive) (apply 'encode-time (org-parse-time-string (match-string 1))) (current-time))) (default-input (and ts (org-get-compact-tod ts))) -(repeater (save-excursion -(save-match-data - (beginning-of-line) - (when (re-search-forward +(repeater (save-match-data +(with-temp-buffer + (insert ts) + (goto-char (point-min)) + (when (re-search-forward \\([.+-]+[0-9]+[hdwmy] ?\\)+ ;;\\(?:[/ ][-+]?[0-9]+[hdwmy]\\)?\\) ? - (save-excursion (progn (end-of-line) (point))) t) + nil t) (match-string 0) org-time-was-given org-end-time-was-given time) (cond -- 2.1.4
[O] Babel blocks get unindented when making changes outside the blocks
Hello all, Given the following code: - BEGIN CODE - * some headline - blah - blah - blah - blah - blah #+begin_src octave first line if (num = 2) stuff end #+end_src - blah # some comments # more comments 1. item 1 - END CODE - If I go to the end of the 'item 1' line, and do 'M-x org-meta-return', the code in the preceding source-block gets un-indented, so that it looks like: #+begin_src octave first line if (num = 2) stuff end #+end_src This behavior has been confirmed by another via IRC, and supposedly the problem lies somewhere in org-list-struct-apply-struct. I just wanted to report this strange behavior in the hope that someone might have an idea on how to remedy it. Regards, Mark
Re: [O] closing column mode for beamer export
Eric S Fraga e.fr...@ucl.ac.uk writes: Beamer export has the :B_columns: tag for exactly this purpose. Indeed and thanks for highlight this as I had forgotten about this property. I find it less æsthetically pleasing. YMMV, of course. The beauty of org is that there are so many ways of accomplishing a given task. Org: there's more than one way to do it - catchy that! ;-) Nick
Re: [O] Colon in block name?
Loris Bennett loris.benn...@fu-berlin.de writes: Hi, I want to export to LaTeX and refer to tables and code blocks as in the example below. However a name with a colon, such as 'tab:my_data' used as a variable for a source block fails: org-babel-ref-resolve: Reference 'my_data' not found in this buffer Yes, it looks as if the babel header parsing code is a bit picky: changing just tab:my_data to tabmy_data everywhere it occurs is enough for the export to succeed. Obviously, and perhaps not surprisingly, the use of the colon in the name seems to be problematic. Should this work? If not, is there a common alternative to the idiom tab:shootings_in_the_foot and fig:foot_with_hole? Cheers, Loris PS: In the example below, the last table is not exported to the LaTeX file, but this is presumably an unrelated issue ... Yes, you need :exports both for that. Example: * Test with block names containing a colon ** Data My data can be found in Table [[tab:my_data]]. #+CAPTION: My data #+NAME: tab:my_data | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Code My code can be found in Listing [[code:my_code]]. #+CAPTION: My code #+NAME: code:my_code #+HEADER: :var data=tab:my_data :colnames yes #+BEGIN_SRC R d - data #+END_SRC ** Results My results can be found in Table [[tab:my_results]]. #+CAPTION: My results #+NAME: tab:my_results #+RESULTS: code:my_code | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Conclusions Names with colons don't work. Nick
Re: [O] markup text with leading, trailing spaces
hymie! writes: I'd like to be able to have a series of commands in my raw org file that I can copy-n-paste into my shell window. But I also like to export my org files to HTML so that I can make ePubs and keep them in my iPad. And this #+BEGIN_SRC command1 command2 command3 #+END_SRC is just IMO ugly. It shouldn't be. Try adding the word shell after BEGIN_SRC, so that it fontifies the code correctly (the variable org-src-fontify-natively should be set to t, but that has been default for a while). Also, add shell to the loaded babel languages, so that you can execute the code and get the results right away in org: #+BEGIN_SRC emacs-lisp (org-babel-do-load-languages 'org-babel-load-languages '((shell . t))) #+END_SRC No need for copy-n-paste, just do C-c C-c where you have your commands. Another added benefit is that it is way easier to add the shell scripts inside a SRC block after you press C-c ' (C-c ' again to go back to your org file), since then you will have the power of Shell-script mode available, for example: C-c (to define a function C-c TAB for an if statement C-c C-l for an indexed loop Try copying this example into an org file, it should fontify it nicely, both in the org file and in the html exported. #+BEGIN_SRC shell echo hello cd ls n=1 while [ $n -le 10 ]; do echo $n n=$(( n + 1 )) done echo bye #+END_SRC Best, -- Jorge.
Re: [O] [patch] better(?) indention for cdlatex-environment
Hi, Nicolas Goaziou m...@nicolasgoaziou.fr writes: I don't feel strongly about it. Anyway, I like this better. Cdlatex is, um, opinionated about is insertion of newlines. I still think it is better to split line. Your behaviour just requires a C-e before calling the function. I agree that the simpler approach is better. That's what I mean by the this above. cdlatex-environment always return nil. I would have to analyze if something got inserted manually. IOW, I don't have the name of the environment, and cdlatex-environment returns nil if I press C-g and if I select and environment. I don't know how to distinguish the cases. If point moved, some text was inserted. I insert a newline before I even call cdlatex. The attached patch works as expected at all locations marked with |, but not the one marked with / and \, which lead to the next question. | - i1 | i2 | / - i3 | \ `org-get-indentation' returns the column of the first non-blank character on the line. This has nothing to do with the point. I think the environment should not indent if point is a bol, but I can check for that. Well, if you have (X being the point) - i1 - i2 X indenting like should give - i1 - i2 X I fail to see the relevant of your example. I want to know why: -i1 X -i2 = C-j -i1 -i2 I.e. i2 becomes a child of i1. —Rasmus -- May the Force be with you
Re: [O] Colon in block name?
On Friday, 13 Feb 2015 at 13:36, Loris Bennett wrote: Stefan Nobis stefan...@snobis.de writes: Loris Bennett loris.benn...@fu-berlin.de writes: The above was attached with Gnus 'C-c RET f', MIME type 'text/x-org'. But you attached it as inline, so the same problems could arise. To be sure to transfer the file unmodified, choose attachment as disposition. Thanks for that explanation. I don't do much attaching these days. Here is the file again as a proper attachment. I can now confirm that there are indeed problems with : in both table names and in the names of results. I am using a relatively up to date version of org (day or so old). -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-820-gd92ef9
Re: [O] Org Babel code blocks in COMMENT subtrees gets executed!?
Hello, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Save this as and Org file, and press C-c C-v C-e... * Intro #+begin_src emacs-lisp (print Foo) #+end_src * COMMENT Method #+begin_src emacs-lisp (print Bar) #+end_src ^ I don't think we should have blocks in COMMENT trees executed, right? Isn't that supposed to be (one of) the difference(s) between :noexport: and COMMENT? C-c C-v C-e on the block executes it. I see nothing wrong with that. However, during an export process, it will not be executed. Do you mean anything else? Regards, -- Nicolas Goaziou
Re: [O] [patch] better(?) indention for cdlatex-environment
Rasmus ras...@gmx.us writes: Nicolas Goaziou m...@nicolasgoaziou.fr writes: I don't see how it is desirable. The logical behaviour is to split the line, unless, of course, docstring clearly specifies this. I don't feel strongly about it. Anyway, I like this better. Cdlatex is, um, opinionated about is insertion of newlines. I still think it is better to split line. Your behaviour just requires a C-e before calling the function. This is also simpler to implement, which is non negligible. cdlatex-environment always return nil. I would have to analyze if something got inserted manually. IOW, I don't have the name of the environment, and cdlatex-environment returns nil if I press C-g and if I select and environment. I don't know how to distinguish the cases. If point moved, some text was inserted. The attached patch works as expected at all locations marked with |, but not the one marked with / and \, which lead to the next question. | - i1 | i2 | / - i3 | \ I expect indentation at all points not at bol. At \ (org-get-indentation) returns 2 even though I'm at bol. Why? `org-get-indentation' returns the column of the first non-blank character on the line. This has nothing to do with the point. Regarding /. In the following i2 is indented meaning that (org-get-indentation) becomes 2. Is that a feature? (with-temp-buffer (org-mode) (insert \n- i1\n- i2) (beginning-of-line) (org-return-indent) (buffer-string)) Well, if you have (X being the point) - i1 - i2 X indenting like should give - i1 - i2 X so that is indeed correct. Regards, -- Nicolas Goaziou
Re: [O] org-time-stamp adds repeater where there is none.
Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: Consider the following line: 2015-02-13 ven. (10h-13h) Hiting C-c . RET with point on the timestamp gives 2015-02-13 ven. -13h (10h-13h) which is not expected. It should now be fixed. Please consider the patch below Thank you for the patch. However, I applied something different. Regards, -- Nicolas Goaziou
[O] markup text with leading, trailing spaces
Greetings. My next SNAFU involves mark-up text. I'd like to be able to have a series of commands in my raw org file that I can copy-n-paste into my shell window. But I also like to export my org files to HTML so that I can make ePubs and keep them in my iPad. So while I strongly prefer the exported version of - ~command1~ - ~command2~ - ~command3~ it's hard to copy-n-paste with the tildes in the way. Unfortunately, this - ~ command1 ~ - ~ command2 ~ - ~ command3 ~ does not mark up the text in my exported-to-html version. And this #+BEGIN_SRC command1 command2 command3 #+END_SRC is just IMO ugly. Is there something I can do, where I can get output similar to - ~command1~ - ~command2~ - ~command3~ without the tildes blocking my text? --hymie!
Re: [O] Org Babel code blocks in COMMENT subtrees gets executed!?
Hello Nicolas, Nicolas Goaziou wrote: Sebastien Vauban writes: Save this as and Org file, and press C-c C-v C-e... * Intro #+begin_src emacs-lisp (print Foo) #+end_src * COMMENT Method #+begin_src emacs-lisp (print Bar) #+end_src ^ I don't think we should have blocks in COMMENT trees executed, right? Isn't that supposed to be (one of) the difference(s) between :noexport: and COMMENT? C-c C-v C-e on the block executes it. I see nothing wrong with that. However, during an export process, it will not be executed. Do you mean anything else? I guess you must be right. I've mentally confused execute all code blocks in buffer with export. I don't think he should work otherwise. Sorry for the noise. Best regards, Seb -- Sebastien Vauban
Re: [O] Exporting a given file (not buffer)
Marcin Borkowski wrote: I need a function, which – given an org file's name – opens it silently, exports to a file, and closes. I can write it myself, but maybe such a function already exists? It seems that `org-export-to-file' exports the current buffer, so I could make a new buffer, `insert-file-contents' the given file to it, turn on `org-mode', do my export and close the buffer (probably using `with-temp-buffer' in the first place) – but is it really necessary to code it, or is it ready somewhere in Org? This is the core part of the code which would do that: --8---cut here---start-8--- (with-temp-buffer (insert-file-contents orgfile) (setq htmlcontents (org-export-as 'html)) (delete-region (point-min) (point-max)) (insert htmlcontents) (buffer-string)) --8---cut here---end---8--- Best regards, Seb -- Sebastien Vauban
[O] Exporting a given file (not buffer)
Hello fellow Orgers, I need a function, which – given an org file's name – opens it silently, exports to a file, and closes. I can write it myself, but maybe such a function already exists? It seems that `org-export-to-file' exports the current buffer, so I could make a new buffer, `insert-file-contents' the given file to it, turn on `org-mode', do my export and close the buffer (probably using `with-temp-buffer' in the first place) – but is it really necessary to code it, or is it ready somewhere in Org? TIA, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] [patch] better(?) indention for cdlatex-environment
Rasmus ras...@gmx.us writes: Hi, Nicolas Goaziou m...@nicolasgoaziou.fr writes: I don't feel strongly about it. Anyway, I like this better. Cdlatex is, um, opinionated about is insertion of newlines. I still think it is better to split line. Your behaviour just requires a C-e before calling the function. I agree that the simpler approach is better. That's what I mean by the this above. This patch applies indentation unless at BOL in which case it stays at BOL. The rest is basically just to work with cdlatex and not insert too many blank lines. It's still quicky, but these quirks seem to be cdlatex quirks. I wonder, are there any commands to merge two elements buffer-undo-list into one? 'Cause ATM it takes two undo-presses to undo an environment insert via this command. —Rasmus -- El Rey ha muerto. ¡Larga vida al Rey! From 85e6e454412c20b13d10e3d2b15dd3f9cb7e3a6b Mon Sep 17 00:00:00 2001 From: rasmus ras...@gmx.us Date: Tue, 10 Feb 2015 12:02:59 +0100 Subject: [PATCH] org.el: Change indention for cdlatex environments * org.el (org-cdlatex-environment-indent): Use different indent algorithm based on content above the new latex-environment. --- lisp/org.el | 45 - 1 file changed, 40 insertions(+), 5 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 59b245a..eaa9084 100755 --- a/lisp/org.el +++ b/lisp/org.el @@ -18645,12 +18645,47 @@ Revert to the normal definition outside of these fragments. (call-interactively (key-binding (vector last-input-event)) (defun org-cdlatex-environment-indent (optional environment item) - Execute `cdlatex-environment' and indent the inserted environment. + Execute `cdlatex-environment' and indent the inserted environment. + +The inserted environment is indented to current indentation +unless point is at the beginning of the line in which case no +indentation occurs. (interactive) - (cdlatex-environment environment item) - (let ((element (org-element-at-point))) -(org-indent-region (org-element-property :begin element) - (org-element-property :end element + (let ((non-blank-eolp + (save-excursion + (and (not (save-excursion + (skip-chars-backward \t) + (bolp))) + (progn (skip-chars-forward \t) (eolp) + (ind (if (bolp) 0 + (save-excursion + (unless (and (bolp) + (save-excursion +(skip-chars-forward \t) +(eolp))) + (org-return-indent)) + (org-get-indentation) +;; Skip forward to next bol to avoid extra newline from +;; cdlatex-environment. +(when non-blank-eolp (forward-line 1) (beginning-of-line)) +(cdlatex-environment environment item) +;; Indent new latex-environment. +(unless (zerop ind) + (let* ((element (org-element-at-point)) + (beg (org-element-property :begin element)) + (end (copy-marker + (save-excursion + (goto-char (org-element-property :end element)) + (skip-chars-backward \t\n\r) + (point) + (save-excursion + (goto-char beg) + (beginning-of-line) + (while (= (point) end) + (org-indent-to-column ind) + (forward-line 1))) + (set-marker end nil)) + (forward-char ind LaTeX fragments -- 2.3.0
Re: [O] [patch] better(?) indention for cdlatex-environment
Rasmus ras...@gmx.us writes: I insert a newline before I even call cdlatex. If point moved _after calling cdlatex_ you know it worked. Otherwise, you just remove the newline. I fail to see the relevant of your example. I want to know why: -i1 X -i2 = C-j -i1 -i2 I.e. i2 becomes a child of i1. This was a bug, which is now fixed. Thanks. Regards,
Re: [O] Orgmode → ODT: Certain chars break export
torys.ander...@gmail.com (Tory S. Anderson) writes: There is a helpful wiki page now that you found XML; it even mentions my specific character.[1] The main source seems to be at the w3.org spec.[2] I don't understand unicode well enough to propose a solution. For now you could use a org-export-before-parsing-hook or org-export-filter-final-output-functions or maybe org-export-filter-body-functions to solve the issue locally. —Rasmus -- Governments should be afraid of their people
Re: [O] Colon in block name?
Stefan Nobis stefan...@snobis.de writes: Loris Bennett loris.benn...@fu-berlin.de writes: The above was attached with Gnus 'C-c RET f', MIME type 'text/x-org'. But you attached it as inline, so the same problems could arise. To be sure to transfer the file unmodified, choose attachment as disposition. Thanks for that explanation. I don't do much attaching these days. Here is the file again as a proper attachment. * Test with block names containing a colon ** Data My data can be found in Table [[tab:my_data]]. #+CAPTION: My data #+NAME: tab:my_data | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Code My code can be found in Listing [[code:my_code]]. #+CAPTION: My code #+NAME: code:my_code #+HEADER: :var data=tab:my_data :colnames yes #+BEGIN_SRC R d - data #+END_SRC ** Results My results can be found in Table [[tab:my_results]]. #+CAPTION: My results #+NAME: tab:my_results #+RESULTS: code:my_code | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Conclusions Names with colons don't work. Reading with Gnus, I don't see any blank lines between the table info and the table itself. It depends on your Gnus configuration. If you set (setq gnus-inhibit-mime-unbuttonizing t) then at least my version of Gnus (v5.13) does indeed split the buffer in multiple pieces with additional newlines. I haven't customised gnus-inhibit-mime-unbuttonizing and it has the value 'nil'. If I read the thread via http://permalink.gmane.org/gmane.emacs.orgmode/94919 there are also no extra newlines. Does anyone else apart from Eric also see space between table header and table? BTW, I'm still more interested in the colon thing ... -- This signature is currently under construction.
Re: [O] markup text with leading, trailing spaces
In our last episode, the evil Dr. Lacto had captured our hero, jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo), who said: hymie! writes: I'd like to be able to have a series of commands in my raw org file that I can copy-n-paste into my shell window. But I also like to export my org files to HTML so that I can make ePubs and keep them in my iPad. And this #+BEGIN_SRC command1 command2 command3 #+END_SRC is just IMO ugly. It shouldn't be. Try adding the word shell after BEGIN_SRC, so that it fontifies the code correctly (the variable org-src-fontify-natively should be set to t, but that has been default for a while) It's not that the font is ugly. It's that * (in the epub) the source code appears in a box * (in the html/epub) it's impossible to tell the difference between two different commands and a single command that was too long and word wrapped to fit in the box * (in the html/epub) I can't have non-monospace comments between/attached to/within the code without drawing four or five separate boxes around my code * (in the org file) For whatever reason, monospace code appears as a light-gray font, which is hard to read against a white background. I'm sure that can be changed, but I haven't had time to figure it out yet. Also, add shell to the loaded babel languages, so that you can execute the code and get the results right away in org: No need for copy-n-paste, just do C-c C-c where you have your commands. I think you are making the incorrect assumption that the machine on which I maintain my Org files is the same machine that I wish to execute commands on. Try copying this example into an org file, it should fontify it nicely, both in the org file and in the html exported. If my commnds were all 8 characters long or less, it would be fine. Some of my commands look like this: adduser username -d /data/chroot/home/username -s /usr/bin/rssh -m -k /dev/null -g rssh useradd -U -G wheel -p '$6$wcMRrkcdGeNHLT5c$0s4qezb00ISmGZSsILOyV/WJn3RnuZPkSEknwoSZ22HvbgkBTe4TQwCz/mpG.3zby.1Jwnmtsq1B.uCbyg5l./' username pssh -x '-q -t -t' -I -i --hosts hosts_linux_rhel6 'sudo -S wget puppet/puppet/pub/system_patch.pl -O /usr/local/bin/system_patch.pl' hostnamefile While I admit that the useradd command is an extreme example, this becomes horribly ambiguous: adduser username -d /data/chroot/home/username -s /usr/bin/rssh -m -k /dev/null -g rssh pssh -x '-q -t -t' -I -i --hosts hosts_linux_rhel6 'sudo -S wget puppet/puppet/pub/system_patch.pl -O /usr/local/bin/system_patch.pl' hostnamefile --hymie!http://lactose.homelinux.net/~hymiehy...@lactose.homelinux.net
