Re: [O] org-babel: two confirmations for org/HTML macro?
Eric Schulte writes: After walking through this patch, it looks like it provides exactly the correct behavior. Please go ahead and apply these changes. Thanks for checking, pushed to master. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] org.texi:8719 Error
Feng Shu writes: org-version: 8.0-pre (release_8.0-pre-416-gbf338e) makeinfo --no-split org.texi -o org org.texi:8719: No closing brace for footnote `'. org.texi:8719: Unmatched }. makeinfo: Removing output file `org' due to errors; use --force to preserve. make[1]: *** [org] Error 1 make[1]: Leaving directory `/home/feng/project/org-mode/doc' make: *** [info] Error 2 Fixed in master. Arguments to macros can not span several lines in TeXinfo. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] adding images in org
so - has anyone tried something like this before? i thought this would be legion. how would you go about implementing this? On 4/12/13, Bastien b...@gnu.org wrote: Hi David, da...@adboyd.com (J. David Boyd) writes: Hmm, then is there any method in Org to auto-download the image, and then inline it? No. Or in other words, do attachments have to be locally available, or will a URL work to attach something? The former. HTH, -- Bastien
Re: [O] #attr_latex :width \textwidth
And I still mean #+attr_ latex: :width :) You're still missing a colon. John On Apr 12, 2013 7:48 PM, Vikas Rawal vikasli...@agrarianresearch.org wrote: Sorry, I meant: #+attr_latex :width \textwidth Vikas
Re: [O] org.texi:8719 Error
Achim Gratz strom...@nexgo.de writes: Feng Shu writes: org-version: 8.0-pre (release_8.0-pre-416-gbf338e) makeinfo --no-split org.texi -o org org.texi:8719: No closing brace for footnote `'. org.texi:8719: Unmatched }. makeinfo: Removing output file `org' due to errors; use --force to preserve. make[1]: *** [org] Error 1 make[1]: Leaving directory `/home/feng/project/org-mode/doc' make: *** [info] Error 2 Fixed in master. Arguments to macros can not span several lines in TeXinfo. Thanks for fixing this, -- Bastien
Re: [O] [babel] sbe not working properly (resolved)
* Christian Moe m...@christianmoe.com wrote:
Hi,
Hi!
I cannot replicate Karl's problem. I copied the code examples, and got
the right results on Org 8.0-pre (pulled this morning).
I did have to make one change -- Babel wouldn't recognize the variables
until I passed them with :var rather than in parens after the codeblock
name. (I saw there was some discussion on dropping the latter syntax;
whoa -- has it already happened?)
I can confirm that using the :var syntax, it is working properly:
#+NAME: epoch2day
#+BEGIN_SRC python :results output :var epoch=1262675465119
time = epoch
import datetime
strtime = str(time)
datetimestamp = datetime.datetime.utcfromtimestamp(int(strtime[:10]))
print datetimestamp.strftime('[%Y-%m-%d %a %H:%M:%S]')
#+END_SRC
#+RESULTS: epoch2day
: [2010-01-05 Tue 07:11:05]
| epoch | day |
|---+---|
| 1262675465119 | [2010-01-05 Tue 07:11:05] |
|123456 | [1970-01-02 Fri 10:17:36] |
| 8754 | [1973-03-03 Sat 09:25:54] |
#+TBLFM: $2='(sbe epoch2day (epoch $1))
... works (and enriches my Org-mode capabilities enourmously! :-).
#+name: add1
#+begin_src python :results silent :var x=1
return x + 1
#+end_src
#+RESULTS: add1
: 2
| foo | bar | 3 | 4 |
#+TBLFM: @1$4='(sbe add1 (x $3))
... does work as well.
Thanks for pointing me to the change of syntax.
--
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] converting people to Emacs and org-mode
* Suvayu Ali fatkasuvayu+li...@gmail.com wrote: Personally I think, any attempts at conversion is futile. I agree only for cases, where the person does not have issues with the current editor/workflow. Just like real religion, choosing an editor is an immensely personal decision if editing text (in whatever form, source code, or prose) is a major part of your day. From my experience, I do have to disagree in this point. *Most* people do not care at all, which editor they are using. Most people did not spend a reasonable time on the decision which tools they are using. The issue for most people is that there is a change of habits, not a change of editor. Only a small percentage of people really do care about a specific product. The others are happy to switch in case they see a certain amount of benefits. Without any proper set of benefits, it's a religious war, I agree. In case of Emacs, there is *always* a proper set of benefits if you are willing to learn this monster IMHO :-) -- 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] adding images in org
Aditya Mandayam adity...@gmail.com writes: so - has anyone tried something like this before? i thought this would be legion. how would you go about implementing this? I doubt so and for a good reason: it opens the door for potential security problems. On the Internet, nobody knows you're a dog; and nobody knows if a picture of a dog is really a picture. -- Bastien
Re: [O] converting people to Emacs and org-mode
* 42 147 aeus...@gmail.com wrote: Hello mailing list, Hi! The question is the title: have you been able to convert many people to Emacs / org-mode? I am not quite sure how many people actually switched to Emacs/Org-mode. However, I have seen many open mouths by showing simply the basic (tables, babel, ...)[1]. This heavily depends on the background of the person (programmer, manager, ...). I recognised that I got very cool reactions on Memacs[2] which enriches my agenda with so much great stuff. With Memacs, I am able to tell quite exactly what happened when and I can correlate tasks with web pages visited, phone calls done, and so forth. However, I got the feeling that people really do want to have such an environment (because of the advantages of its featureset) but most of them are afraid of the set-up process and the learning curve. Not everybody wants (or is able) to invest time to learn Emacs/Org-mode. Last autumn, I had the pleasure to conduct a 12h-workshop at our university with a bunch of very interested people. Everybody added his/her own requirements and the feedback was quite good. I guess that they all switched to Org-mode. Next week, there is an event called Grazer Linuxtage[3] which is the largest open source event in Austria. Last year, I presented Org-mode using [1]. This year, I am planning to concentrate on workflows[4]. I will ask the audience to tell me workflow examples they are coping with in daily life and show them, how to accomplish this using Org-mode (or give pointers to features I did not try by myself). Bring your own workflow is my motto. Opportunities like this are great to get people in touch with Emacs/Org-mode. Two years ago, somebody shortly presented Org-mode basics during a Python talk. This was my introduction to this great tool :-) 1. https://github.com/novoid/org-mode-workshop/blob/master/featureshow/org-mode-teaser.org 2. see signature below 3. http://linuxtage.at (German) 4. http://glt13-programm.linuxtage.at/events/161.de.html -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: get Memacs from https://github.com/novoid/Memacs https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] org-agenda-show-log, org-timeline bugs
Hi Derek, Derek Upham s...@blarg.net writes: I tried running org-timeline on an Org file with lots of timestamped TODO - DONE state changes, and didn't see the matches I was expecting. While poking around, I found two problems. I finally fixed those. Thanks for reporting this. -- Bastien
Re: [O] Bug: ATTACH tag gets exported unconditonally to PDF [8.0-pre (release_8.0-pre-11014-gd195e8 @ /home/mrb/dev/emacs/packages/org-mode/lisp/)]
Hi Marcel, Marcel van der Boom mar...@hsdev.com writes: When exporting a subtree, I often use the attach functionality (C-c C-a) to attach files to a heading. This gives the heanding an :ATTACH: tag. When exporting such a subtree via latex to pdf, using org-export-dispatch (C-c e) the output in pdf contains the :ATTTACH: tag. If I use other tags on headings, they are not printed, which is what I expect to happen, given my configuration. Possibly related is that setting '#+EXPORT_EXCLUDE_TAGS: exclude' also does NOT hide the section having that tag if using a #SETUPFILE directive. It *does* work when setting the 'org-export-excluded-tags' variable directly, so I think this is a separate issue. I'm not sure I fully understand the issue but in any case, :ATTACH: is treated like any other tag when exporting a subtree for me. -- Bastien
Re: [O] Enriched/Org is a colorful Org
Hi Eli, On Fri, Apr 12, 2013 at 09:38:47PM +0300, Eli Zaretskii wrote: Date: Fri, 12 Apr 2013 20:00:56 +0200 From: Suvayu Ali fatkasuvayu+li...@gmail.com Cc: Torsten Wagner torsten.wag...@gmail.com, emacs-orgmode@gnu.org, carsten.domi...@gmail.com If some package wants to keep something updated (line number displays in this case), is using the post-command-hook the only option? No. The other one is piggy-back jit-lock. See nlinum in ELPA for an example, which actually is a drop-in replacement for linum, but without many of its problems. Thanks a lot :) -- Suvayu Open source is the future. It sets us free.
Re: [O] New exporter and dates in tables
Hello, Bastien b...@gnu.org writes: Nicolas Goaziou n.goaz...@gmail.com writes: Thinking more about it, I think I need to make some more exceptions anyway. For example timestamps in clock lines and in planning info shouldn't react to `org-export-with-timestamps' (it would be silly to have `org-export-with-planning' set to t and still see nothing because `org-export-with-timestamps' is nil). Indeed :) Thinking again about Bernt's use-case and Carsten's feedback, I suggest making rules for planning instead of exceptions for time-stamps. - planning information is - SCHEDULED: time-stamp - DEADLINE: time-stamp - CLOSED: time-stamp - one or more time-stamps (active or inactive) alone on a line - a non-planning time-stamp is any time-stamp that does not fall into the categories above, i.e. if it is inlined in an element (usually a paragraph or a table). SCHEDULED and friends define a property in the associated headline. Generic timestamps don't (excepted for the first one, but it's arbitrary and the parser ignores it anyway). Also, there can be as many active timestamps in a section, but there can be only one planning info element. Therefore, I don't think they belong to the same category. We ought to treat them differently, like we do at the moment. The inactive/active time-stamp in a table is handled. And so is another corner case that we did not discussed yet: people using active time-stamps right below a headline, with the expectation that this time-stamp will bring the entry up in the agenda -- such time-stamp is now considered a time-stamp while it is really some planning info. This is obviously some planning info, but not a planning-info element. Any active timestamp is a planning info by the way. The planning-info term just defines the line with SCHEDULED, DEADLINE, CLOSED keyword. It may be silly, be a name had to be chosen. Anyway, I don't think it's a corner case. I guess this is cleaner than creating exceptions. What about it? I'd rather create the aforementioned exceptions (in tables but more importantly in planning info and clocks): it is important to distinguish planning-info from a mere timestamp. We can change the name if it's confusing, though. Is that OK with you? Regards, -- Nicolas Goaziou
Re: [O] [BUG] org-clock-in menu scrolls off the top of the window
Bernt Hansen be...@norang.ca writes: I'm fine with removing duplicates in the 1-N list. Done. -- Bastien
Re: [O] #attr_latex :width \textwidth
And I still mean #+attr_ latex: :width :) You're still missing a colon. :). Sorry, I was not copying and pasting. Anyhow, this works: #+attr_latex: :environment tabulary :width \textwidth :align L|RR Thanks, Vikas
Re: [O] Enriched/Org is a colorful Org
In your opinion, would it be possible to reproduce the functionality of outline-mode using text properties rather than overlays? And in the case of org-mode, would this really make that much of a difference in terms of performance? Regards, Sean On Fri, Apr 12, 2013 at 1:36 PM, Eli Zaretskii e...@gnu.org wrote: From: Carsten Dominik carsten.domi...@gmail.com Date: Fri, 12 Apr 2013 12:56:11 +0200 Cc: emacs-orgmode@gnu.org I guess outline mode does have the exact same problem in this case, in fact any mode with large amount of hidden text. Of course. The only difference is that outline is not as popular as Org, and usually is used with relatively short chunks of text. But the problems are exactly the same.
Re: [O] New exporter and dates in tables
Nicolas Goaziou n.goaz...@gmail.com writes: Is that OK with you? I still resist this idea. I would find it both cleaner and more useful for users to extend `org-export-with-timestamps' with three choices: 'inactive-not-standalone 'active-not-standalone 'not-standalone When set to 'not-standalone, it means export time-stamps except standone time-stamps, i.e. those who are alone on a line. That's the set-up most users will want after t, it fits the habits that Bernt has been describing, and it's useful for users who wants to get rid of the planning-like active time-stamp right below the headline. Also, it's easier to explain users how to set this up (through the docstring) than to explain why time-stamps are not removed in tables with (setq org-export-with-timestamps nil). -- Bastien
Re: [O] phone links...
Michael Strey mst...@strey.biz writes: Robert, On Mo, Apr 08, 2013 at 09:44:12 -0500, Robert Goldman wrote: Michael Strey wrote: Currently org-phone.el as well as my org-dial.el are incompatible with org-contacts. The only idea behind my proposal was to make the contributors of both packages aware of each other. Can you explain what makes org-phone incompatible with org-contacts? Maybe my naming of some function? The problem is on the side of org-contacts. Org-contacts does not support links in its properties. Thus, currently the only solution to use the advantages of org-contacts and org-phone is to give the information twice, like in the following example. #+BEGIN_SRC org * Strey, Michael :PROPERTIES: :EMAIL:mst...@strey.biz f...@bar.com :PHONE:+493514129535 +491263213 :END: [[mailto:mst...@strey.biz]] [[mailto:f...@bar.com]] [[phone:+49 (0)351 41295-35]] [[phone:+49 126 3213]] #+END_SRC I use a export function which can export all contacts to the format: #+begin_example * NAME ** EMAIL: [[mailto:n...@n.com]] ** EMAIL: [[mailto:n...@n.com]] ** PHONE: [[tel:123456789]] ** PHONE: [[tel:123456789]] #+end_example It it only a temporary solution, may be someone will need it ,but adding it to the master may be not a good idea. From 2c73cdfdf54fe4c882a3bc0d3ce3cd268555100e Mon Sep 17 00:00:00 2001 From: Feng Shu tuma...@gmail.com Date: Sat, 13 Apr 2013 22:00:03 +0800 Subject: [PATCH] org-contacts.el, export contacts to outline-format * contrib/lisp/org-contacts.el (org-contacts-outline-file): new variable (org-contacts-outline-format): new function which formats a contact to outline-format (org-contacts-export-as-outline-format): new function, formats all contacts to outline-format * NAME :PROPERTIES: :EMAIL: n...@n.com n...@n.com :PHONE: 123456789 :END: export as: * NAME ** EMAIL: [[mailto:n...@n.com]] ** EMAIL: [[mailto:n...@n.com]] ** PHONE: [[tel:123456789]] ** PHONE: [[tel:123456789]] --- contrib/lisp/org-contacts.el | 69 ++ 1 个文件被修改，插入 69 行(+) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index a3c4aed..dd89251 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -156,6 +156,12 @@ This overrides `org-email-link-description-format' if set. :group 'org-contacts :type 'file) +(defcustom org-contacts-outline-file contacts-outline.org + Default file for outline-format export. + :group 'org-contacts + :type 'file) + + (defcustom org-contacts-enable-completion t Enable or not the completion in `message-mode' with `org-contacts'. :group 'org-contacts @@ -896,6 +902,69 @@ is created and the VCard is written into that buffer. (current-buffer) (progn (save-buffer) (kill-buffer) +(defun org-contacts-outline-format (contact) + Formats CONTACT in outline format. + (let* ((properties (caddr contact)) + (name (org-contacts-vcard-escape (car contact))) + (n (org-contacts-vcard-encode-name name)) + (email (cdr (assoc-string org-contacts-email-property properties))) + (tel (cdr (assoc-string org-contacts-tel-property properties))) + (note (cdr (assoc-string org-contacts-note-property properties))) + (bday (org-contacts-vcard-escape (cdr (assoc-string org-contacts-birthday-property properties + (addr (cdr (assoc-string org-contacts-address-property properties))) + (nick (org-contacts-vcard-escape (cdr (assoc-string org-contacts-nickname-property properties + (head (format * %s\n name))) +(concat head + (when email (progn + (setq emails-list (split-string email [,;: ]+)) + (setq result ) + (while emails-list + (setq result (concat result ** EMAIL: (concat [[mailto: (car emails-list) ]]) \n)) + (setq emails-list (cdr emails-list))) + result)) + (when addr + (format ** ADRESS: (replace-regexp-in-string \\, ? ; addr))) + (when tel (progn + (setq phones-list (split-string tel [,;: ]+)) + (setq result ) + (while phones-list + (setq result (concat result ** TEL: (concat [[tel: (car phones-list) ]] ) \n)) + (setq phones-list (cdr phones-list))) + result)) + (when bday + (let ((cal-bday (calendar-gregorian-from-absolute (org-time-string-to-absolute bday + (format ** BDAY:%04d-%02d-%02d\n + (calendar-extract-year cal-bday) + (calendar-extract-month cal-bday) + (calendar-extract-day cal-bday + (when nick (format ** NICKNAME: %s\n nick)) + (when note (format ** NOTE: %s\n note) + + + +(defun org-contacts-export-as-outline-format (optional name file to-buffer) + Export all contacts matching NAME as outline format +If TO-BUFFER is nil, the content is written to FILE or +`org-contacts-outline-file'. If TO-BUFFER is non-nil, the buffer +is created and the outlines is written into that buffer. + (interactive) ; TODO ask for name? + (let* ((filename (or file org-contacts-outline-file)) + (buffer (if
Re: [O] Enriched/Org is a colorful Org
Sean O'Halpin sean.ohal...@gmail.com writes: In your opinion, would it be possible to reproduce the functionality of outline-mode using text properties rather than overlays? And in the case of org-mode, would this really make that much of a difference in terms of performance? Broadly speaking, answer seems to be a Yes. It is possible that some details have to be hammered out wrt indirect buffers. See the last item in this post http://lists.gnu.org/archive/html/emacs-devel/2010-10/msg00177.html Regards, Sean On Fri, Apr 12, 2013 at 1:36 PM, Eli Zaretskii e...@gnu.org wrote: From: Carsten Dominik carsten.domi...@gmail.com Date: Fri, 12 Apr 2013 12:56:11 +0200 Cc: emacs-orgmode@gnu.org I guess outline mode does have the exact same problem in this case, in fact any mode with large amount of hidden text. Of course. The only difference is that outline is not as popular as Org, and usually is used with relatively short chunks of text. But the problems are exactly the same.
Re: [O] Enriched/Org is a colorful Org
Date: Sat, 13 Apr 2013 13:24:13 +0100 From: Sean O'Halpin sean.ohal...@gmail.com Cc: Carsten Dominik carsten.domi...@gmail.com, Org Mode emacs-orgmode@gnu.org In your opinion, would it be possible to reproduce the functionality of outline-mode using text properties rather than overlays? This needs to be analyzed. Outline mode uses several features that are specific to overlays, but not to text properties: isearch-open-invisible and front-advance. (It also uses 'evaporate', but that happens automatically with text properties.) I think front-advance will happen automatically, but searching inside invisible text is currently supported only for overlays (for reasons that I consider irrelevant, but that's me). And in the case of org-mode, would this really make that much of a difference in terms of performance? I don't know, because I didn't measure that, and neither did I see any measurements published. If there are many overlays in a buffer, redisplay performance will certainly be better with text properties, but I don't know whether this improvement will be significant: there could be other factors at work that affect performance to a much greater effect. If we want to know for sure, there's no way around profiling this. Luckily, we now have profiler.el to help us.
Re: [O] #attr_latex :width \textwidth
Hello, Vikas Rawal vikasli...@agrarianresearch.org writes: Anyhow, this works: #+attr_latex: :environment tabulary :width \textwidth :align L|RR For the record, for simple :align strings, you can also use Org syntax: | / || | | | | | | | | l | r | r | r | r | r | r | | | a | b | c | d | e | f | g | It is more intrusive, but it will (should) work in all back-ends. Regards, -- Nicolas Goaziou
Re: [O] #attr_latex :width \textwidth
On Sat, Apr 13, 2013 at 6:50 AM, Vikas Rawal vikasli...@agrarianresearch.org wrote: And I still mean #+attr_ latex: :width :) You're still missing a colon. :). Sorry, I was not copying and pasting. Anyhow, this works: #+attr_latex: :environment tabulary :width \textwidth :align L|RR What was the fix? Using =:environment tabulary= ? Or was it a syntax error? Thanks, John Thanks, Vikas
Re: [O] Attributes on HTML tables?
On Fri, Apr 12, 2013 at 10:06:21AM +0800, Eric Abrahamsen wrote:
François Pinard pin...@iro.umontreal.ca writes:
Christian Moe m...@christianmoe.com writes:
While on this subject! :-)
Could Org allow the output of HTML5 rather than XHTML, under the control
of some option? I've read that some frameworks really expect HTML5 to
work properly, such an option might ease inter-operation between
exported Org and such frameworks.
I'm curious about this possibility as well -- how much work would it be?
Sorry, late to the thread, i've been laid up. Anyway, the xhtml output
from ox-html _should_ be
mostly valid html5 (valid xhtml 1.0 in general should be valid html5).
However, you will need to change the html-table-tag to not use
attributes, and remove the xml declaration
(which is a warning and not an error in html5)
Here's a sample org file (which changes the divs to be more html5ish
as well, not necessary)
which validates as HTML5: (btw, i've remove the scripts and
default-styles just to make the
html output smaller, the file will validate even with them in the
output).
rick
- % -
#+TITLE: HTML 5 Test
#+DATE: {{{modification-time(%Y-%m-%d)}}}
#+HTML_DOCTYPE: !DOCTYPE html
#+BIND: org-html-xml-declaration
#+BIND: org-html-head-include-default-style nil
#+BIND: org-html-table-tag table
#+BIND: org-html-scripts
#+BIND: org-html-divs ((preamble header preamble) (content
section content) (postamble footer postamble))
* Org HTML5 Test
ok?
* How about a table
| col1 | col2 |
|--+--|
| a|1 |
| b|2 |
* And a list
- a
- b
- c
* A definiton list
- a :: foo
- b :: bar
Re: [O] adding images in org
Bastien b...@gnu.org writes: Hi David, da...@adboyd.com (J. David Boyd) writes: Hmm, then is there any method in Org to auto-download the image, and then inline it? No. Or in other words, do attachments have to be locally available, or will a URL work to attach something? The former. HTH, Thanks, that's what I needed to know!:-) Dave
Re: [O] New exporter and dates in tables
Bastien b...@gnu.org writes: I would find it both cleaner and more useful for users to extend `org-export-with-timestamps' with three choices: 'inactive-not-standalone 'active-not-standalone 'not-standalone This is a different idea. The change would happen at the exporter level, not at parser's. When set to 'not-standalone, it means export time-stamps except standone time-stamps, i.e. those who are alone on a line. Well, parsing is not line based, and a timestamp alone on a line doesn't mean much. Though, a timestamp alone in a paragraph is much easier to translate. IOW: 2013-04-13 Sat is not a standalone timestamp (use M-q). but, 2013-04-13 Sat is a standalone timestamp. That's the set-up most users will want after t, it fits the habits that Bernt has been describing, and it's useful for users who wants to get rid of the planning-like active time-stamp right below the headline. Also, it's easier to explain users how to set this up (through the docstring) than to explain why time-stamps are not removed in tables with (setq org-export-with-timestamps nil). If we agree to the alone in a paragraph part, I can implement it. But we still need exceptions for clocks and timestamps (i.e., ignore `org-export-with-timestamps' value when `org-export-with-planning' or `org-export-with-clocks' is non-nil). Regards, -- Nicolas Goaziou
[O] Fix info manual compilation
hi,
The info manual does not compile because of a wrong next node entry in
org.texi. A fix is attached.
--
Suvayu
Open source is the future. It sets us free.
From bed20723adc4700df5289804ab4254d705fe148f Mon Sep 17 00:00:00 2001
From: Suvayu Ali fatkasuvayu+li...@gmail.com
Date: Sat, 13 Apr 2013 21:33:17 +0200
Subject: [PATCH] Fix org info manual compilation
---
doc/org.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/org.texi b/doc/org.texi
index 645c8c5..c65bdc1 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -11273,7 +11273,7 @@ You can choose default values for these options by
customizing the variable
@code{org-html-infojs-options}. If you always want to apply the script to your
pages, configure the variable @code{org-html-use-infojs}.
-@node @LaTeX{} and PDF export, OpenDocument Text export, HTML export, Exporting
+@node @LaTeX{} and PDF export, Markdown export, HTML export, Exporting
@section @LaTeX{} and PDF export
@cindex @LaTeX{} export
@cindex PDF export
--
1.8.1.4
Re: [O] blank todo kw does not delete closed ts
On 4/12/13, Bastien b...@gnu.org wrote: I'm convinved now, and switching to state without any TODO keyword will now remove the CLOSED planning information. Thanks, Bastien. One of the great things about Org is its attention to detail, and that includes little orthogonality pieces. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is NO hope without action. This means YOU.
Re: [O] Fix info manual compilation
Hello, Suvayu Ali fatkasuvayu+li...@gmail.com writes: The info manual does not compile because of a wrong next node entry in org.texi. A fix is attached. Thank you for the patch. You need to add TINYCHANGE at the end of the commit message before I can apply it. Regards, -- Nicolas Goaziou
Re: [O] Attributes on HTML tables?
On Sat, Apr 13, 2013 at 01:31:17PM +0800, Eric Abrahamsen wrote:
Eric Abrahamsen e...@ericabrahamsen.net writes:
François Pinard pin...@iro.umontreal.ca writes:
Bastien b...@gnu.org writes:
Eric Abrahamsen e...@ericabrahamsen.net writes:
The first step is probably to research the differences between xhtml and
html 5.
Well, I would even skip this step and just hack something usable.
I sort of fudged on the below. The upside is that it should be pretty
forgiving now: you can set all kinds of strings as your :html-doctype,
and it will do a reasonably good job of guessing how to handle it.
Barring actual bugs or poor design decisions, what's left to do is:
1. Make sure that inlined script and style chunks are escaped correctly,
I seem to remember reading that the commenting/escaping syntax for these
chunks varies according to html flavor.
2. I'd like to add the possibility to put an arbitrary :html-container
#+BEGIN_SRC emacs-lisp
#+TITLE: HTML 5 Test
#+DATE: {{{modification-time(%Y-%m-%d)}}}
#+HTML_DOCTYPE: html5
#+BIND: org-html-divs ((preamble header preamble) (content section
content) (postamble footer postamble))
* Org HTML5 Test
#+ATTR_HTML: :options html-container article
note that you just just set #+HTML_CONTAINER: article in the head of the
file if you want all the containers to be articles.
+(defconst org-html-doctype-alist
+ '((html4 . !DOCTYPE HTML PUBLIC \-//W3C//DTD HTML 4.01//EN\)
+(html4-strict . !DOCTYPE HTML PUBLIC \-//W3C//DTD HTML 4.01//EN\
+\http://www.w3.org/TR/html4/strict.dtd\;)
+(xhtml . !DOCTYPE HTML PUBLIC \-//W3C//DTD XHTML 1.0 Strict//EN\
+\http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\;)
+(html5 . !DOCTYPE HTML))
I believe that should be (note the lowercase html):
(xhtml . !DOCTYPE html PUBLIC \-//W3C//DTD XHTML 1.0 Strict//EN\
+\http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\;)
(html5 . !DOCTYPE html)
See http://www.w3schools.com/tags/tag_doctype.asp for a fairly
complete list of valid doctypes.
rick
Re: [O] Org-mode outside Org-mode
Hi Thorsten, On 4/12/13, Thorsten Jolitz tjol...@gmail.com wrote: If you structure your Emacs Lisp files the 'outshine way', you can convert them into complete Org files fast and easily using 'outorg.el'. No, we are talking about different things. With what I am talking about, you can: - put your Org notes in your main Org agenda files exactly where you want them - efficiently use planning information to create daily/weekly agenda entries - bounce to and from the exact location in your source code to the exact Org entry Therefore, the category of tools I suggested to you -- which consists of annotation-like mechanisms -- is a completely different way of tackling the problem of dealing with source code and Org simultaneously. Yet it is a way of dealing with them simultaneously, which is the reason I suggested putting them in your document also, if you felt like it. I believe that your outshine and outorg methods cannot do all of those things. Therefore, I believe that they do not solve the same problems at all. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is NO hope without action. This means YOU.
Re: [O] Org-mode outside Org-mode
Hi Eric, Here is old not-working not-finished code that I abandoned. But it illustrates the goal. Samuel === Maybe something like: - In source file, C-c ' to go to Org entry associated with nearest ID marker - C-u C-c ' to create ID marker and create its Org entry in your Org file - when it is created, you can refile it wherever - C-c ' in Org entry to go to associated source file ID marker ;; this is quick and dirty code ;; ;; it is brittle to store a file path. it is much better to ;; incorporate ID markers into the Org ID system, then Org will ;; find the file using org-id-goto. to tell the system where you ;; keep your source files, set a variable. ;; ;; doing so will eliminate the need to store a pathname property. ;; ;; maybe this can be refactored with detangling markers. ;; ;; see also annotation, which requires no marker, but is more ;; brittle and does not indicate that you have an annotation. ;; this should be merged with that. (defconst alpha-org-id-pair-file-property ID-pair-file) (defun alpha-org-bounce-id-pair () The opposite of Org Babel. C-c ' in source code to document it in Org. Same in documentation to go to source code. (interactive) (let ((id (org-id-get))) (if id (org-id-goto id) (let ((source (org-entry-get nil alpha-org-id-pair-file-property))) (find-file source) (re-search-forward id) (forward-line 1) (defun* alpha-org-bounce-or-insert-id-pair (key (comment ;; )) Bounce to the other end of, or create, a (notes, ID marker) pair. Suppose you are editing an Emacs Lisp source code file. You can bounce between a special entry in your Org agenda file \(e.g. notes.org\) and your external file \(e.g. file.el\). (interactive) (let ((id (org-id-new id-pair))) (save-excursion (alpha-org-insert-id-marker id :comment comment)) (org-capture nil))) (defun* alpha-org-insert-id-marker (id key comment) Insert an ID marker. (insert (concat (when comment comment) $[id id ;; (when link (concat :link link)) ;; ;; (org-insert-link) ;; (when label (concat :label \ label \)) ])) (forward-line -1) (funcall indent-line-function)) On 4/6/13, Eric Schulte schulte.e...@gmail.com wrote: That could be handy. For jumping back and for by function name, the following simple implementation might be sufficient. It relies on file local variables to know which src and Org-mode files are related to each other. -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is NO hope without action. This means YOU.
Re: [O] New exporter and dates in tables
Hello, Nicolas Goaziou wrote: Bastien b...@gnu.org writes: I would find it both cleaner and more useful for users to extend `org-export-with-timestamps' with three choices: 'inactive-not-standalone 'active-not-standalone 'not-standalone This is a different idea. The change would happen at the exporter level, not at parser's. When set to 'not-standalone, it means export time-stamps except standone time-stamps, i.e. those who are alone on a line. Well, parsing is not line based, and a timestamp alone on a line doesn't mean much. Though, a timestamp alone in a paragraph is much easier to translate. IOW: 2013-04-13 Sat is not a standalone timestamp (use M-q). but, 2013-04-13 Sat is a standalone timestamp. Wouldn't it be a good moment to introduce APPT: 2013-04-13 Sat or maybe better named EVENT: 2013-04-13 Sat for things that only apply for today? Best regards, Seb -- Sebastien Vauban
[O] C-o now mapped to org-ctrl-o surprise
Hi, I was quite surprised after pulling down master to find that C-o has been bound to org-ctrl-o (commit 45d6d8f8 2013-04-05 11:14:20 +0200). I personally don't use open-line much myself so remap this key for my own use. Wouldn't it be better to do something like: (define-key org-mode-map [remap open-line] 'org-ctrl-o) and let the user choose which key does open-line rather than create a new keybinding which might override a user definition? Also, perhaps the function should be called org-open-line rather than org-ctrl-o. Regards, Sean
[O] having problems exporting to Beamer
When I attempt to export a .org file to Beamer (with C-c C-e l b after
requiring ox-beamer) I get the following error [1]. From the info page
(info (org)Beamer export) it looks like I shouldn't have to do any
special buffer preparation.
What am I doing wrong?
Thanks,
Footnotes:
[1]
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match(\\S- nil)
(not (string-match \\S- argument))
(if (not (string-match \\S- argument)) (cond ((eql type (quote action))
(if (string-match \\`.*\\' argument) argument (format %s argument)))
((eql type (quote defaction)) (cond ((string-match \\`\\[.*\\]\\' argument)
argument) ((string-match \\`.*\\' argument) (format [%s] argument))
((string-match \\`\\[\\(.*\\)\\]\\' argument) (format [%s] (match-string
1 argument))) (t (format [%s] argument ((eql type (quote option)) (if
(string-match \\`\\[.*\\]\\' argument) argument (format [%s] argument))) (t
argument)))
org-beamer--normalize-argument(nil option)
(format \\begin{frame}%s{%s}\n (org-beamer--normalize-argument
org-beamer-outline-frame-options (quote option)) org-beamer-outline-frame-title)
(concat (format \\begin{frame}%s{%s}\n (org-beamer--normalize-argument
org-beamer-outline-frame-options (quote option))
org-beamer-outline-frame-title) (if (wholenump depth) (progn (format
\\setcounter{tocdepth}{%d}\n depth))) \\tableofcontents\n
\\end{frame}\n\n)
(progn (concat (format \\begin{frame}%s{%s}\n
(org-beamer--normalize-argument org-beamer-outline-frame-options (quote
option)) org-beamer-outline-frame-title) (if (wholenump depth) (progn (format
\\setcounter{tocdepth}{%d}\n depth))) \\tableofcontents\n
\\end{frame}\n\n))
(if depth (progn (concat (format \\begin{frame}%s{%s}\n
(org-beamer--normalize-argument org-beamer-outline-frame-options (quote
option)) org-beamer-outline-frame-title) (if (wholenump depth) (progn (format
\\setcounter{tocdepth}{%d}\n depth))) \\tableofcontents\n
\\end{frame}\n\n)))
(let ((depth (plist-get info :with-toc))) (if depth (progn (concat (format
\\begin{frame}%s{%s}\n (org-beamer--normalize-argument
org-beamer-outline-frame-options (quote option))
org-beamer-outline-frame-title) (if (wholenump depth) (progn (format
\\setcounter{tocdepth}{%d}\n depth))) \\tableofcontents\n
\\end{frame}\n\n
[...]
(if async (let ((with-temp-message Initializing asynchronous export
process) (current-message)) (unwind-protect (progn (if with-temp-message
(progn (setq current-message (current-message)) (message %s
with-temp-message))) (let ((--copy-fun (org-export--generate-copy-script ...))
(--temp-file (make-temp-file org-export-process)) (--coding
buffer-file-coding-system)) (let ((temp-file --temp-file) (temp-buffer ...))
(unwind-protect (prog1 ... ...) (and ... ...))) (let* ((process-connection-type
nil) (--proc-buffer ...) (--process ...)) (org-export-add-to-stack (get-buffer
--proc-buffer) nil --process) (set-process-sentinel --process (let ... ...)
(and with-temp-message (if current-message (message %s current-message)
(message nil) (org-export-to-file (quote beamer) outfile subtreep
visible-only body-only ext-plist))
(let ((outfile (org-export-output-file-name .tex subtreep))) (if async (let
((with-temp-message Initializing asynchronous export process)
(current-message)) (unwind-protect (progn (if with-temp-message (progn (setq
current-message ...) (message %s with-temp-message))) (let ((--copy-fun ...)
(--temp-file ...) (--coding buffer-file-coding-system)) (let (... ...)
(unwind-protect ... ...)) (let* (... ... ...) (org-export-add-to-stack ... nil
--process) (set-process-sentinel --process ... (and with-temp-message (if
current-message (message %s current-message) (message nil)
(org-export-to-file (quote beamer) outfile subtreep visible-only body-only
ext-plist)))
org-beamer-export-to-latex(nil nil nil nil nil)
(org-latex-compile (org-beamer-export-to-latex nil subtreep visible-only
body-only ext-plist))
(if async (let ((outfile (org-export-output-file-name .tex subtreep))) (let
((with-temp-message Initializing asynchronous export process)
(current-message)) (unwind-protect (progn (if with-temp-message (progn (setq
current-message ...) (message %s with-temp-message))) (let ((--copy-fun ...)
(--temp-file ...) (--coding buffer-file-coding-system)) (let (... ...)
(unwind-protect ... ...)) (let* (... ... ...) (org-export-add-to-stack ... nil
--process) (set-process-sentinel --process ... (and with-temp-message (if
current-message (message %s current-message) (message nil))
(org-latex-compile (org-beamer-export-to-latex nil subtreep visible-only
body-only ext-plist)))
org-beamer-export-to-pdf(nil nil nil nil)
org-export-dispatch(nil)
call-interactively(org-export-dispatch nil nil)
--
Eric Schulte
http://cs.unm.edu/~eschulte
Re: [O] #attr_latex :width \textwidth
Anyhow, this works: #+attr_latex: :environment tabulary :width \textwidth :align L|RR What was the fix? Using =:environment tabulary= ? Or was it a syntax error? I don't know actually :). I guess I was trying various things, quoting the strings, using :options, etc. It was a bit of a trial and error that I did. Vikas
Re: [O] Adding date to displayed results of org-search-view
Thanks, Bastien! Column view is very nice. The easiest way to achieve this is to have a column view in your Org file like this: #+COLUMNS: %30ITEM %TODO %PRIORITY %15SCHEDULED %15DEADLINE Then in the agenda, C-c C-x C-c will display the column view. This allows me to do most of what I want, but how do I filter so that only the items with :RESEARCH: tag are displayed. Perhaps I missed it, but I didn't see it in your short introduction, here: http://orgmode.org/worg/org- tutorials/org-column-view-tutorial.html Any tips?
Re: [O] Fix info manual compilation
Hi Nicolas, On Sat, Apr 13, 2013 at 10:42:12PM +0200, Nicolas Goaziou wrote: Hello, Suvayu Ali fatkasuvayu+li...@gmail.com writes: The info manual does not compile because of a wrong next node entry in org.texi. A fix is attached. Thank you for the patch. You need to add TINYCHANGE at the end of the commit message before I can apply it. I actually signed the FSF papers quite a while back; just forgot to mention it on the list :-p. My assignment number is: RT704245. In the form I had mentioned I submitted changes to doc/org.texi so this patch should be covered. Do I need to send a copy of the assignment to the list? I have a scan of the assignment. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] blank todo kw does not delete closed ts
On 12 Apr 2013 11:58, Bastien b...@gnu.org wrote: Hi Samuel, I'm convinved now, and switching to state without any TODO keyword will now remove the CLOSED planning information. Thanks, -- Bastien Hi Bastien and all, I am afriad you saw this coming: Could that be an option? I actively would want to preserve the closed note to keep an accurate history of my work with the task. Best, Brian vdB
Re: [O] Adding date to displayed results of org-search-view
how do I filter so that only the items with :RESEARCH: tag are displayed.
Just a quick follow-up to my own post. I realize now that I need to run C-C-c
C-x C-c *after* running C-c a s +{research} -done
Thanks for the help!
