Re: [O] phone links...
Hi Simon, Simon Thum writes: > Since you're at it: I keep the attached patch personally. I use it to sync > org-contacts entries to my phone. I applied Feng's patches against org-contacts.el, maybe you don't need your patch anymore. Best, -- Bastien
Re: [O] [patch] add 'tel' and 'note' property
Applied, thanks. -- Bastien
Re: [O] phone links...
On 4/4/13 Apr 4 -3:38 PM, Simon Thum wrote: > Since you're at it: I keep the attached patch personally. I use it to > sync org-contacts entries to my phone. > > I didn't sign up to the FSF so far, and suck at maintaining emacs commit > msg conventions. If the patch is interesting I'll do what is required. I'm afraid I don't use org-contacts, so I don't exactly understand how this relates. Are "phone:" links desired? I.e., would you make the values of the phone fields be phone-type org hyperlinks? Or would you just expect to be able to push phone numbers directly into the org-phone-call function, without having to make the contact entries explicitly be hyperlinks? I suppose one should also attempt to make this compatible with the org/BBDB integration, another thing about which I'm quite ignorant Best, r P.S. I note that the contacts databases I have access typically have FAX and mobile entries as well as home and work. Many also allow "custom" phone number types.
Re: [O] phone links...
On 4/4/13 Apr 4 -7:15 AM, Bastien wrote: > Hi Robert, > > Robert Goldman writes: > >> The two files are below, in hopes of getting suggestions for improvement >> so that someday this could find itself into contrib/. > > Looks like a good start -- please keep us updated about your progress > and your will to include this in contrib/, I'm sure many users would > enjoy it. I will be happy to include this into contrib (and do the relevant assignment) at any time when people think that it is sufficiently ready to go. I have been testing it in contrib/ in a testing branch in my git repo. I think a minor refactoring would make it more general: split the phone handler into two components: a filter function (like the one for linphone), defaulting to identity; and a command, probably revised to be a format string (so that the dialed number could be place in an arbitrary location). I will try to have a new version with these changes very soon. Best, r
[O] [patch] add 'tel' and 'note' property
>From 94cb96299561618ec237e8cb17cc27bdb38218ac Mon Sep 17 00:00:00 2001 From: Feng Shu Date: Fri, 5 Apr 2013 09:47:04 +0800 Subject: [PATCH 1/3] Let org-contacts.el has the ability which can export email-address list * org-contacts.el (org-contacts-vcard-format): let the function work with email-address list. The org-contact file is : * Name :PROPERTIES: :EMAIL: na...@test.org; na...@test.org, na...@test.org na...@test.org :END: The export result is like: BEGIN:VCARD VERSION:3.0 N:Name;;; FN:Name EMAIL:na...@test.org EMAIL:na...@test.org EMAIL:na...@test.org EMAIL:na...@test.org END:VCARD --- contrib/lisp/org-contacts.el | 10 -- 1 个文件被修改，插入 8 行(+)，删除 2 行(-) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index e78b9da..b85ae2d 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -819,13 +819,19 @@ to do our best." (let* ((properties (caddr contact)) (name (org-contacts-vcard-escape (car contact))) (n (org-contacts-vcard-encode-name name)) - (email (org-contacts-vcard-escape (cdr (assoc-string org-contacts-email-property properties + (email (cdr (assoc-string org-contacts-email-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 "BEGIN:VCARD\nVERSION:3.0\nN:%s\nFN:%s\n" n name))) (concat head - (when email (format "EMAIL:%s\n" email)) + (when email (progn + (setq emails-list (split-string email "[,;: ]+")) + (setq result "") + (while emails-list + (setq result (concat result "EMAIL:" (car emails-list) "\n")) + (setq emails-list (cdr emails-list))) + result)) (when addr (format "ADR:;;%s\n" (replace-regexp-in-string "\\, ?" ";" addr))) (when bday -- 1.7.10.4 >From fee9e6afbf38db8dcf94763d1e07ca2b35342dea Mon Sep 17 00:00:00 2001 From: Feng Shu Date: Fri, 5 Apr 2013 09:54:06 +0800 Subject: [PATCH 2/3] org-contacts.el, add note property * org-contacts.el (org-contacts-note-property): New varible which add note property (org-contacts-vcard-format): Add the ability exporting note property --- contrib/lisp/org-contacts.el |6 ++ 1 个文件被修改，插入 6 行(+) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index b85ae2d..5f16d41 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -71,6 +71,11 @@ When set to nil, all your Org files will be used." :type 'string :group 'org-contacts) +(defcustom org-contacts-note-property "NOTE" + "Name of the property for contact note." + :type 'string + :group 'org-contacts) + (defcustom org-contacts-birthday-format "Birthday: %l (%Y)" "Format of the anniversary agenda entry. The following replacements are available: @@ -841,6 +846,7 @@ to do our best." (calendar-extract-month cal-bday) (calendar-extract-day cal-bday (when nick (format "NICKNAME:%s\n" nick)) + (when note (format "NOTE:%s\n" note)) "END:VCARD\n\n"))) (defun org-contacts-export-as-vcard (&optional name file to-buffer) -- 1.7.10.4 >From 38ef150badd21eb0c5d9159e6444cdeeb1252380 Mon Sep 17 00:00:00 2001 From: Feng Shu Date: Fri, 5 Apr 2013 09:59:55 +0800 Subject: [PATCH 3/3] org-contacts.el, add tel property * org-contacts.el (org-contacts-tel-property): New variable, add tel property (org-contacts-vcard-format): Add the ability exporting tel property --- contrib/lisp/org-contacts.el | 12 1 个文件被修改，插入 12 行(+) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index 5f16d41..8172c80 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -61,6 +61,11 @@ When set to nil, all your Org files will be used." :type 'string :group 'org-contacts) +(defcustom org-contacts-tel-property "PHONE" + "Name of the property for contact phone number." + :type 'string + :group 'org-contacts) + (defcustom org-contacts-address-property "ADDRESS" "Name of the property for contact address." :type 'string @@ -839,6 +844,13 @@ to do our best." result)) (when addr (format "ADR:;;%s\n" (replace-regexp-in-string "\\, ?" ";" addr))) + (when tel (progn + (setq phones-list (split-string tel "[,;: ]+")) + (setq result "") + (while phones-list + (setq result (concat result "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" -- 1.7.10.4 --
Re: [O] avoid subscripting text
On Apr 3, 2013, at 9:30 PM, Gary Oberbrunner wrote: > I use LaTeX export all the time, but almost always with words with > underscores in them (data from external tables, variable names and so on). > So I never want _ to turn into a subscript. Just one data point, but that's > how I use it. I have to echo this use case. I have variable names and what not with underscores in the name about 100 times as much as I have a need for a subscript.
Re: [O] looking for advice on where/how to store org realted files (attachments/images etc)
I have a few different ways I organize my files: 1) I work a lot of tickets in specific source-code directories. Each directory has a .capture.org file in it w/capture templates for TODOs and NOTES. These typically get archived with the ticket is finished 2) I also use emacs/org on my tablet for note-taking in class. These org files all go in a subdir off my Dropbox directory: ~/Dropbox/ClassNotes with a classname-date naming scheme 3) I also have a org directory off my home director (~/org) that holds all my more general org files such as more general TODO & NOTES, my daily work log file, and so forth. But really, the big thing is that whatever order you use, that it work for you. Plus, it can always be changed later if it doesn't work quite right, or needs expanded. Subhan On Thu, Apr 4, 2013 at 7:16 AM, Itai kloog wrote: > Hi all > > After my first week or so with org im finally starting to switch to it > full time. Im also in the process of migrating all my notebooks from all > other apps. previous note apps ive used stored attachments/images inside > the notes/databases. this made me wonder how i should approach this with > org. > > I take alot of screenshots and attach alot of PDF's/ scrips to my notes. > I would love to hear back from the community on how people organize these " > realted" org files. do they go to separate folder per org note file, IE > having a research2000.org file and then a research2000 folder for all > related files? is it better to just dump all files into one big repository > for ALL org notes? are there better solution? > > thanks alot in advance > > z. > > > -- Subhan Michael Tindall | Software Developer | s...@rentrakmail.com RENTRAK | www.rentrak.com | NASDAQ: RENT
Re: [O] org-html-postamble-format and #+DATE: specification in 8.0pre
Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> Dieter Wilhelm writes:
>>
>>> Dear list,
>>>
>>> I changed the html postamble
>>>
>>> org-html-postamble-format is a variable defined in `ox-html.el'.
>>> Its value is
>>> (("en" "Author: %a (%e)\nDate: %d
>>> \nGenerated by %c \n")
>>> ("de" "Autor: %a (%e)\nDatum: %d
>>> \nGeneriert von %c \n")
>>> ("fr" "Auteur: %a (%e)\nDate: %d
>>> \nGenerated by %c \n"))
>>>
>>> Original value was
>>> (("en" "Author: %a (%e)\nDate:
>>> %d\nGenerated by %c\n>> class=\"xhtml-validation\">%v"))
>>>
>>> but now I can't specify a date in the form
>>>
>>> #+DATE: "%Y-%m-%d"
>>>
>>> Formerly an empty specification meant the current date, but now in the
>>> preamble the date remains empty.
>>
>> I'm having the same issue. Did you find a way around it?
>
> I didn't try to reproduce the problem, but specifying a format time
> string as a DATE value is not possible anymore. You still can provide
> a timestamp and tweak `org-export-date-timestamp-format' (or BIND it) to
> format it.
Sorry I don't get it completely.
I'd like to have as the DATE value the current change time of the file.
You mean that I should set this with the Emacs timestamp facility? Like:
#+DATE: Time-stamp: " "
>
> Regards,
--
Best wishes
H. Dieter Wilhelm
Darmstadt
Germany
[O] iCalendar export problem
Hi all, I have a strange problem that seems related to the iCalendar exporter. I have an event which has the date spec <2013-02-07 Th 12:00-14:00 +1w> but shows up on 13:00 my phone calendar (fed by ox-icalendar), CEST. Fun thing is, I did not experience lag with other entries. The org entry becomes: BEGIN:VEVENT DTSTAMP:20130207T11Z UID:TS1-d36d5eb9-e2db-42a3-866f-7442becadef0 DTSTART:20130207T12 DTEND:20130207T14 RRULE:FREQ=WEEKLY;INTERVAL=1 SUMMARY:Brown Bag Meeting DESCRIPTION:Location: R 103\n\nRecurs: <2013-02-07 Do 12:00 +1w>–<2013-02-07 Do 14:00 +1w> ... Another one (shown right this time) is: BEGIN:VEVENT DTSTAMP:20130404T15Z UID:TS1-441e317c-7b52-4910-bbd3-0949a5c1bdd7 DTSTART:20130404T17 DTEND:20130404T19 The difference seems to be the DTSTAMP which is "correctly" aligned with DTSTART. However, that's not what DTSTAMP is for. Actually, it should be set to the date-time the export happens. At least, that's what they say: http://stackoverflow.com/questions/11594921/whats-the-difference-between-created-and-dtstamp-in-the-icalendar-format Changing that probably does not help my problem, but seems better than the cooked-up values now ending up in DTSTAMP. I could not see any other candidate problems, though the analysis is weak so far. Cheers, Simon
Re: [O] [PATCH] Process hlines in imported tables
Hi Rick, Rick Frankel wrote: >> IIUC, wouldn't that be changing the default answer to "how to interpret the >> results" just for Perl? While the default answer for all languages seems to >> be "table"? > > It's not. only shell (which doesn't have _value_ results), Is this statement really true, btw? Wouldn't the value result of a sh code block be the return code? > and sql, force the results to be interpreted as a table. Because table is the default option... > elisp, ruby and python seem to treat raw results as scalars. For ELisp, Eric told that it was an exception. For Ruby and Python, I dunno, as I don't know the languages and have no environment ready to test them (under Windows). Best regards, Seb -- Sebastien Vauban
Re: [O] Incompatible agenda commands
Bastien,
Bastien wrote:
> "Sebastien Vauban" writes:
>
>> While a custom agenda command such as the following used to work some time
>> ago, it does not anymore.
>>
>> (add-to-list 'org-agenda-custom-commands
>>'("D" "Stuck + agenda"
>> ((stuck "")
>> (agenda ""
>> ((org-agenda-span 'week) t)
>>
>> Now, it seems that the "stuck" block view inhibits any extra view to be
>> displayed afterward.
>
> do I understand correctly that you only get the stuck view and not the
> agenda view?
Yes, you do understand what I meant.
> If so, I cannot reproduce it.
I hate those! I'll try to provide you with a reproducible recipe, then.
Thanks for looking at it.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [PATCH] Process hlines in imported tables
Eric, Eric Schulte wrote: > I would agree that this (meaning raw implies scalar) should either occur > for all languages or for none. I think this is something interesting, but I wonder now if we wouldn't loose more than we would win. I mean: how would one be able to output a real "raw" result, then, that is one where pipes are not interpreted as table field separator which have to be aligned in some specific way. Do we need another argument for that? I mean: at the end, raw should really be raw (no interpretation). If we want some cycling for table alignment purpose (BTW, do you have lots of such code blocks?), maybe it'd be better to introduce a `cycle' argument or so? > If we do have such header argument implications, then we'd want to put them > into the weakest portion of the default header argument hierarchy. Currently > this hierarchy looks something like > > 1. default header arguments shipped with Org-mode > 2. user-set default header arguments > 3. default languages-specific header arguments shipped with Org-mode > 4. user-set default language-specific header arguments > 5. buffer or file level header arguments > 6. subtree header arguments > 7. code block header arguments > > I think this raw implies verbatim action should probably take place > somewhere between 3 and 4, but there could be arguments for other > positions. Also, without looking at the code, I'm not sure how > difficult adding such implications would be. Maybe I don't understand the problem correctly, but I'd think this "raw implies verbatim" would have to take place after _each_ above step. If between 3 and 4, then a raw specified on the block level (step 7) wouldn't imply verbatim? Does that make sense? I think every raw (be it default, language, buffer, subtree or block-local) would have to imply the same reasoning. > Are there other header argument implication rules which would make code > blocks "do what I mean" more naturally in more situations? Best regards, Seb -- Sebastien Vauban
Re: [O] phone links...
Since you're at it: I keep the attached patch personally. I use it to sync org-contacts entries to my phone. I didn't sign up to the FSF so far, and suck at maintaining emacs commit msg conventions. If the patch is interesting I'll do what is required. Cheers, Simon On 04/04/2013 02:15 PM, Bastien wrote: Hi Robert, Robert Goldman writes: The two files are below, in hopes of getting suggestions for improvement so that someday this could find itself into contrib/. Looks like a good start -- please keep us updated about your progress and your will to include this in contrib/, I'm sure many users would enjoy it. Thanks! >From c3b151d30a45f32679a166ac9fb220f85ad39dd0 Mon Sep 17 00:00:00 2001 From: Simon Thum Date: Sat, 27 Oct 2012 18:25:24 +0200 Subject: [PATCH 3/3] add telephone capability to org-contacts Signed-off-by: Simon Thum --- contrib/lisp/org-contacts.el | 14 ++ 1 files changed, 14 insertions(+), 0 deletions(-) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index 30b9ed0..dba717f 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -64,6 +64,16 @@ If set to nil, all your Org files will be used." :type 'string :group 'org-contacts) +(defcustom org-contacts-private-telephone-property "TEL" + "Name of the property for contact private/home telephone." + :type 'string + :group 'org-contacts) + +(defcustom org-contacts-work-telephone-property "WORKTEL" + "Name of the property for contact work/office telephone." + :type 'string + :group 'org-contacts) + (defcustom org-contacts-birthday-property "BIRTHDAY" "Name of the property for contact birthday date." :type 'string @@ -565,11 +575,15 @@ Org-contacts does not specify how to encode the name. So we try to do our best." (email (org-contacts-vcard-escape (cdr (assoc-string org-contacts-email-property properties (bday (org-contacts-vcard-escape (cdr (assoc-string org-contacts-birthday-property properties (addr (cdr (assoc-string org-contacts-address-property properties))) + (telpriv (org-contacts-vcard-escape (cdr (assoc-string org-contacts-private-telephone-property properties + (telwork (org-contacts-vcard-escape (cdr (assoc-string org-contacts-work-telephone-property properties (nick (org-contacts-vcard-escape (cdr (assoc-string org-contacts-nickname-property properties (head (format "BEGIN:VCARD\nVERSION:3.0\nN:%s\nFN:%s\n" n name))) (concat head (when email (format "EMAIL:%s\n" email)) + (when telpriv (format "TEL;TYPE=HOME,VOICE:%s\n" telpriv)) + (when telwork (format "TEL;TYPE=WORK,VOICE:%s\n" telwork)) (when addr (format "ADR:;;%s\n" (replace-regexp-in-string "\\, ?" ";" addr))) (when bday -- 1.7.8.6
Re: [O] Incompatible agenda commands
Hi Sébastien,
"Sebastien Vauban"
writes:
> While a custom agenda command such as the following used to work some time
> ago, it does not anymore.
>
> (add-to-list 'org-agenda-custom-commands
>'("D" "Stuck + agenda"
> ((stuck "")
> (agenda ""
> ((org-agenda-span 'week) t)
>
> Now, it seems that the "stuck" block view inhibits any extra view to be
> displayed afterward.
do I understand correctly that you only get the stuck view and not the
agenda view? If so, I cannot reproduce it.
Thanks,
--
Bastien
[O] looking for advice on where/how to store org realted files (attachments/images etc)
Hi all After my first week or so with org im finally starting to switch to it full time. Im also in the process of migrating all my notebooks from all other apps. previous note apps ive used stored attachments/images inside the notes/databases. this made me wonder how i should approach this with org. I take alot of screenshots and attach alot of PDF's/ scrips to my notes. I would love to hear back from the community on how people organize these " realted" org files. do they go to separate folder per org note file, IE having a research2000.org file and then a research2000 folder for all related files? is it better to just dump all files into one big repository for ALL org notes? are there better solution? thanks alot in advance z.
Re: [O] [PATCH] Process hlines in imported tables
Rick, Achim, Eric, Rick Frankel wrote: > I agree. "raw" results should probably be treated as scalar (with > cycling of the output to reformat an table :). I think (!) I fully agree with that as well. Just that I wouldn't like more exceptions in the supported languages. So, if it's kindof the new default, great. > BTW, I am having problems wrapping my head around verbatim. > From testing, it seems that verbatim acts the same as scalar. 100% true; they're just synonyms [1]. FYI, so are `table' and `vector'... Best regards, Seb [1] I hate synonyms. I'd be in favor of just keeping one syntax... -- Sebastien Vauban
Re: [O] Help with beamer
Hi Erich, Neuwirth Erich wrote: > I am preparing a presentation with or-mode and beamer. > I am using > :PROPERTIES: > :BEAMER_envargs: [<+->] > :END: > to make list elements appear one by one. > > When creating handouts, I want to supress the build effect (it works by > creatin many slides > unnecessary in printout) > > Is there a way of using a global variable to enable or disable all these > blocks controlling > the build effects so I can avoid changing them all one by one? #+LaTeX_CLASS_OPTIONS: [presentation] should do it. Best regards, Seb -- Sebastien Vauban
Re: [O] Org-mode outside Org-mode
Hi Thorsten, IIUC, I don't think this is related. The idea is not to edit source code in Org buffers, and it is not to use a Navi buffer or to do navigation. The idea is to be in my-lisp.el, and do C-c ', and get to a canonical entry in my-org.org, then do C-c ' again and get back to my-lisp.el. The navi buffer seems like it wouldn't do that. 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 as a metalanguage: calling SQL "functions"
Eric, Eric Schulte wrote: > "Sebastien Vauban" writes: >> Eric Schulte wrote: > At this point I'm not sure if the documentation or the code should be > amended. I've personally never liked the args-in-block-name syntax, but > I don't recall if we formally decided to abandon it, or if it has simply > been broken in a recent commit. I am not sure if I have any say here, but I agree that the args in name notation looks not as good and might be considered for abolishment. >>> >>> Great, I agree wholeheartedly and I'll update the documentation >>> accordingly (and take a look at lob-ingest to ensure it no longer uses >>> this var-in-name style). >> >> I confirm that, following a discussion we had, you had decided to drop the >> alternate syntax, a couple of months ago (more than 2 ;-)). > > Great, so I'm not imagining things. Thanks Seb. For the sake of clarity, it all began (in September 2011) with the fact it was more difficult to trap errors such as missing default value, in the functional-syntax style. See http://article.gmane.org/gmane.emacs.orgmode/46888. This also lead, a couple of weeks later (October 2011), to questionning the multiple keywords used for code blocks, such as #+source: and #+srcname:. See http://article.gmane.org/gmane.emacs.orgmode/48399. Best regards, Seb -- Sebastien Vauban
Re: [O] Export a Subtree to an other .org file
* On Thu 03:13PM, 04 Apr 2013, Bastien (b...@altern.org) wrote: > Nicolas Goaziou writes: > > > What about the following? > > Looks gret! Feel free to apply it, > > -- > Bastien > Hi Nicolas and Bastien, I've updated to the latest git version and tested this. Works like a charm -- thank you! -- Best, Hsiu-Khuern.
Re: [O] [PATCH] Process hlines in imported tables
Sebastien Vauban writes: > Achim Gratz wrote: >> Elisp is different from all other languages: it doesn't do any >> processing of strings to begin with for value returns. The reason that >> Perl processes "raw" results is that org-babel-result-cond does not >> switch to the "scalar" path for this condition, which is why you need >> the extra "verbatim". It probably should, though, so if Eric agrees >> then I will push a change that does this. > > IIUC, wouldn't that be changing the default answer to "how to > interpret the results" just for Perl? While the default answer for > all languages seems to be "table"? Again, org-babel-result-cond doesn't interpret "raw" at all at the moment, which I think is a bug. This leads to the interpretation of multiline strings and strings with separators in the return value as tables. Not all Babel languages are using that macro, so these implementations might have a different interpretation (which may or may not be a bug in itself). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
[O] need file+function help
There's really very little documentation about how this works, could use a
pointer to an example or two, or even a bit of help.
Here's my goal:
Using a capture temple of file+function to do the following: (basically
enhancing file+datetree)
user enters a bit of information (ticket ID, description, etc) using normal
capture template stuff (prompt for tags or prompt{enter ticket ID}
the ticket number is used as a parameter to file+function to:
a) find the current date in the tree
b) find or create a subtree based on the ticket ID
c) add an entry below this subtree with the ticket ID as a tag, and the
description as the headline, plus possible links to the file where capture
was initiated etc.
d) 'clock in' to the task (:clock-in property works great)
I have all of this working fine using file+datetree EXCEPT the subtree
create or add
questions:
1) are the values gathered by capture available to the function specified
for file+function, & if so what are their names?
2) what is the general template for a function for use with file+function,
cleanup, return values, etc that would be expected?
3) would it be better to extend datetree to datetree+headline for entries
of this type? it seems like it a pretty usefully functionality to have (I
can think of 2 or 3 instances i'd regularly use this just off the top of my
head
Thanks, all!
Subhan
--
Subhan Michael Tindall | Software Developer
| s...@rentrakmail.com
RENTRAK | www.rentrak.com | NASDAQ: RENT
Re: [O] [PATCH] Process hlines in imported tables
On Thu, Apr 04, 2013 at 03:59:36PM +0200, Sebastien Vauban wrote: > Hi Achim, > > Achim Gratz wrote: > > Rick Frankel writes: > >> Missed verbatim. Thanks for the pointer, it works, but i think that > >> perl is double-processing returned values. If we do the same things in > >> elisp i get (my) expected results: > >> > >> #+begin_src elisp :results raw > >> "|c1|c2| > >> |- > >> |a|1| > >> |b|2|"; > >> #+end_src > > > > Elisp is different from all other languages: it doesn't do any > > processing of strings to begin with for value returns. The reason that > > Perl processes "raw" results is that org-babel-result-cond does not > > switch to the "scalar" path for this condition, which is why you need > > the extra "verbatim". It probably should, though, so if Eric agrees > > then I will push a change that does this. > > IIUC, wouldn't that be changing the default answer to "how to interpret the > results" just for Perl? While the default answer for all languages seems to > be "table"? It's not. only shell (which doesn't have _value_ results), and sql, force the results to be interpreted as a table. elisp, ruby and python seem to treat raw results as scalars. rick
Re: [O] [PATCH] Process hlines in imported tables
On Wed, Apr 03, 2013 at 08:21:01PM +0200, Achim Gratz wrote: > Rick Frankel writes: > > Missed verbatim. Thanks for the pointer, it works, but i think that > > perl is double-processing returned values. If we do the same things in > > elisp i get (my) expected results: > > > > #+begin_src elisp :results raw > > "|c1|c2| > > |- > > |a|1| > > |b|2|"; > > #+end_src > > Elisp is different from all other languages: it doesn't do any > processing of strings to begin with for value returns. The reason that > Perl processes "raw" results is that org-babel-result-cond does not > switch to the "scalar" path for this condition, which is why you need > the extra "verbatim". It probably should, though, so if Eric agrees > then I will push a change that does this. I agree. "raw" results should probably be treated as scalar (with cycling of the output to reformat an table :). BTW, I am having problems wrapping my head around verbatim. >From testing, it seems that verbatim acts the same as scalar. rick
[O] Question about reftex mode in org-mode
Quite some time ago, I incorporated reftex into my use of org mode, per a suggestion on Worg: ;;;--- ;;; Use reftex with org-mode, per Worg ;;;--- (autoload 'turn-on-reftx "reftex" "Turn on RefTeX mode." t) (defun org-mode-reftex-setup () (turn-on-reftex)) (add-hook 'org-mode-hook 'org-mode-reftex-setup) Now I find that this has a bad behavior at least with Aquamacs: it can cause attempts to use the menu bar to be interrupted by a cryptic popup file selector that says "Master file:" This seems to be reftex trying to set a value for TeX-master. So maybe reftex is unhappy when it's not invoked inside of AucTeX (where TeX-master is defined and set). Anyone else seen this? Have a solution (e.g., have org files assume that TeX-master is t)? Thanks! r
Re: [O] babel results handling
On Wed, Apr 03, 2013 at 08:18:09AM -0600, Eric Schulte wrote:
> Rick Frankel writes:
>
> > On Sun, Mar 31, 2013 at 07:37:38AM -0600, Eric Schulte wrote:
> > `sh' is probably not the best choice as a "gold standard" due to the
> > fact that it only supports STDOUT ("output" and not "value").
> >
> > Many of the languages are obviously not general purpose, or do not
> > support (like shell), wrapped values (only STDOUT), or don't generate
> > text, so consistency does not matter (e.g., css, sass, sql, sqlite,
> > plantuml, dot).
> >
> > Regardless, the attached org file is a first step an comparing the
> > result processing of some languages (specifically, sh, emacs-lisp,
> > perl and ruby), which, I think, covers a good portion of the babel use
> > of general purpose languages.
> >
>
> This is a great file. Thanks for generating it and sharing it.
> Although I think it would be more useful if languages were the smallest
> scale of organization rather than the largest to make cross-language
> comparison easier.
I will try it this way over the weekend. I kept going back-and-forth
with the nesting, never really liked any of the output...
> Would it be difficult to add another set of code blocks which
> automatically compare the output of these automatically generated code
> blocks, indicating when there are differences.
I'll try an add (i think Achim suggested adding it to the test
infrastructure in a later email, will take a look, but don't hold your
breath :).
> > The upshot, is that perl value results match shell value/output
> > results and emacs-lisp, python and ruby all return about the same
> > results (elisp returns the quote characters from a verbatim string).
> >
>
> What are the perl-shell vs. python-ruby-elisp differences?
Again, Achim has covered it in a later email, but it's that sh (which
is using _output_ and not _value_), and perl (as _value_) are
post-processing the raw results through org-table-convert-region.
> If you want to use pipes to delimit data, then I'd suggest *not*
> interpreting the data as a value, but rather doing something like
> ":results verbatim drawer". Generally pipes aren't considered to be
> table column delimiters, I'd try tabs or spaces instead.
Agreed, i was just setting up a test to compare results among
different processors.
> > Also, looking at the manual
> > (http://orgmode.org/manual/results.html#results) vs. the code, are
> > there are actually four classes of :results arguments with type broken
> > into type and format?
> >
> > - Type :: (file list vector table scalar verbatim)
> > - Format :: (raw html latex org code pp drawer)
> >
>
> Yes, this does seem to be more clear. If you're willing to supply a
> documentation patch I'd be very happy to apply it.
I will make the change this weekend -- I have commit privileges but
wanted to make sure my interpretation was correct.
rick
Re: [O] Nice blog post - Org-mode in Your Pocket Is a GNU-Shaped Devil
On Thu, Apr 04, 2013 at 07:48:50AM -0400, François Pinard wrote: > If I write "sad to say", this is because Gnus coupled me more intimately > with Emacs, while I tried hard to run away of it, to recover some sanity. [...] > In the meantime, despite I found some MUAs quite impressive, I knew deep > down that none really match Gnus. For me it is the other way around. I want to couple with Emacs more closely, but Gnus prevents me from doing so. A few gripes follow. 1. Emacs is single threaded, so a network interruption while reading my email over IMAP means my emacs server is stuck! 2. Oh that's easy to solve, use maildirs (sync with OfflineIMAP). That does not work well because Gnus uses its own flags (an example where Gnus actually breaks standards)! There are some hacks around that out in the wild, so let's let it slide. 3. Gnus stores some meta information/cache for maildirs in a .nnmaildir folder *inside* the maildir directory tree! maildir ├── .nnmaildir ├── cur ├── new └── tmp I do not know how, but this supposed meta information or cache takes about 2/3 of disk space as the original maildir! Obviously that is a problem for large mailboxes. Apart from this I often notice broken threads from posters using Gnus, not sure if Gnus or the user is to blame there. I use mutt-kz (mutt with notmuch integration) and emacsclient. With support for linking using org-notmuch, I couldn't be happier. -- Suvayu Open source is the future. It sets us free.
Re: [O] Bug: SETUPFILE directive not working [8.0-pre (release_8.0-pre-10873-gafb59b @ /home/mrb/dev/emacs/packages/org-mode/lisp/)]
On do 04-apr-2013 18:57
Nicolas Goaziou wrote:
> Also, "#+SETUPFILE directive has stopped working for me" isn't very
> informative. Would you care to elaborate?
Given the line:
#+SETUPFILE: "/path/to/settings.org"
in an orgmode buffer.
C-c C-c on that line says "Local setup has been refreshed" but at least
some of the settings do not get applied. Notably i have several lines
in that 'settings.org' file like this:
#+TAGS: { buy(b) sell(s) } build(u) fix(f) clean(n)
or
#+TAGS: call(c) check(e) mail(m) read(r) write(w) learn(l)
The shortcuts nor grouping is available after refreshing the config.
Also reloading org-mode or restarting Emacs does not make a difference.
Trying the same setup with the minimal org loading as suggested on the
Feedback page [1] shows the same behaviour.
[1] http://orgmode.org/org.html#Feedback
--
Marcel van der Boom -- http://hsdev.com/mvdb.vcf
HS-Development BV-- http://www.hsdev.com
We use bitcoin! -- http://bitcoin.org
Re: [O] Bug: SETUPFILE directive not working [8.0-pre (release_8.0-pre-10873-gafb59b @ /home/mrb/dev/emacs/packages/org-mode/lisp/)]
Hello, Marcel van der Boom writes: > On do 04-apr-2013 15:22 > Carsten Dominik wrote: > >> I think the change is that you now need to put the file names into >> quotes. I am not entirely sure why, but I guess Nicolas had a reason >> for it. > > This does not make a difference for me. I should have been added that > in the first place in the bug report. Also, "#+SETUPFILE directive has stopped working for me" isn't very informative. Would you care to elaborate? Regards, -- Nicolas Goaziou
Re: [O] Bug: SETUPFILE directive not working [8.0-pre (release_8.0-pre-10873-gafb59b @ /home/mrb/dev/emacs/packages/org-mode/lisp/)]
Hello, Carsten Dominik writes: > On 4 apr. 2013, at 14:51, Marcel van der Boom wrote: > >> >> 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. >> >> >> Using the #+SETUPFILE directive has stopped working for me in version >> 8.x. I use a line at the bottom of moste of my org files like so: >> >> #+SETUPFILE: ~/etc/org-config.org >> >> This works fine in 7.9.4. > > > I think the change is that you now need to put the file names into quotes. > I am not entirely sure why, but I guess Nicolas had a reason for it. IIRC, it was so SETUPFILE and INCLUDE keywords would be more alike (quotes are mandatory in include keyword). Regards, -- Nicolas Goaziou
Re: [O] Nice blog post - Org-mode in Your Pocket Is a GNU-Shaped Devil
Bastien writes: > Hi François, > > François Pinard writes: > >> It took me about one hour (my Gnus programming >> is rather rusty) for adding a Gnus command opening many tabs at once, in >> a graphical browser, for all articles I retain in Gnus for reading. > > That looks nice, is your hack public somewhere? Not exactly the above, but I have the following my-gnus-browse bound to ; in gnus-summary-mode-map, which opens up a browser with the right links for gwene, gmane and nnrss groups. I think the browse-nnrss-url is untouched from the gnus manual. (defun browse-nnrss-url( arg ) (interactive "p") (let ((url (assq nnrss-url-field (mail-header-extra (gnus-data-header (assq (gnus-summary-article-number) gnus-newsgroup-data)) (if url (progn (browse-url (cdr url)) (gnus-summary-mark-as-read-forward 1)) (gnus-summary-scroll-up arg (add-to-list 'nnmail-extra-headers nnrss-url-field) (defun rs-gnus-browse-archived-at () "Browse \"Archived-at\" URL of the current article." (interactive) (let (url) (with-current-buffer gnus-original-article-buffer (setq url (gnus-fetch-field "Archived-at"))) (if (not (stringp url)) (gnus-message 1 "No \"Archived-at\" header found.") (setq url (gnus-replace-in-string url "^<\\|>$" "")) (browse-url url (defun my-gnus-browse (arg) (interactive "p") (cond ((string-match ":\\(gwene\\|gmane\\)\\." gnus-newsgroup-name) (rs-gnus-browse-archived-at)) ((string-match "^nnrss\." gnus-newsgroup-name) (browse-nnrss-url arg Regards, -- Haider
Re: [O] Help with beamer
Additional question How can I set the BEAMER_envargs property for the whole file? On Apr 4, 2013, at 2:16 PM, Neuwirth Erich wrote: > I am preparing a presentation with or-mode and beamer. > I am using > :PROPERTIES: > :BEAMER_envargs: [<+->] > :END: > to make list elements appear one by one. > > When creating handouts, I want to supress the build effect (it works by > creatin many slides > unnecessary in printout) > > Is there a way of using a global variable to enable or disable all these > blocks controlling > the build effects so I can avoid changing them all one by one? > > > >
Re: [O] [PATCH] Process hlines in imported tables
"Sebastien Vauban" writes: > Hi Achim, > > Achim Gratz wrote: >> Rick Frankel writes: >>> Missed verbatim. Thanks for the pointer, it works, but i think that >>> perl is double-processing returned values. If we do the same things in >>> elisp i get (my) expected results: >>> >>> #+begin_src elisp :results raw >>> "|c1|c2| >>> |- >>> |a|1| >>> |b|2|"; >>> #+end_src >> >> Elisp is different from all other languages: it doesn't do any >> processing of strings to begin with for value returns. The reason that >> Perl processes "raw" results is that org-babel-result-cond does not >> switch to the "scalar" path for this condition, which is why you need >> the extra "verbatim". It probably should, though, so if Eric agrees >> then I will push a change that does this. > > IIUC, wouldn't that be changing the default answer to "how to interpret the > results" just for Perl? While the default answer for all languages seems to > be "table"? > I would agree that this (meaning raw implies scalar) should either occur for all languages or for none. If we do have such header argument implications, then we'd want to put them into the weakest portion of the default header argument hierarchy. Currently this hierarchy looks something like 1. default header arguments shipped with Org-mode 2. user-set default header arguments 3. default languages-specific header arguments shipped with Org-mode 4. user-set default language-specific header arguments 5. buffer or file level header arguments 6. subtree header arguments 7. code block header arguments I think this raw implies verbatim action should probably take place somewhere between 3 and 4, but there could be arguments for other positions. Also, without looking at the code, I'm not sure how difficult adding such implications would be. Are there other header argument implication rules which would make code blocks "do what I mean" more naturally in more situations? Cheers, > > Best regards, > Seb -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] No dot in datepicker dialog
Hi Bastien, * Bastien [04. Apr. 2013]: > Karl Voit writes: >> A couple of weeks ago[1] the datepicking dialog got modified such >> that a dot "." jumps to the current day. Handy for most Org-mode >> users I guess. > > "." is also the character used in M-x calendar RET to jump to today's > date. >> However, this interferes with another feature I used quite often: I >> was able to enter "31.12." to quickly select 31st of December, for >> example. >> >> Please notice that (at least) in German speaking countries, it is >> common to use "31.12." and not "12/31" or similar. >> >> So in current Org-mode (git), I can not enter the character "." >> because it does not end up with a dot in the bottom line. I think here two different usages collide: 1) user of org-mode controls the date picker via keystrokes 2) enter dates (and times) via cut/paste from other sources (which were not created with the org-mode date picker in mind) and let the date picker parse them I for instance heavily rely on the second usage scenario. While I see that the usage of `.' for jump-to-today is long-standing tradition in Emacs calendar (first usage scenario), it's also a very common character to separate date fields in many countries (see http://en.wikipedia.org/wiki/Date_format_by_country) (important for second usage scenario). Therefore if we give `.' a special meaning in the date picker it is no longer possible to paste dates e.g. from emails if these happen to use `.' as date field separator. >> Is there a way to customize this behavior? > > You can insert a dot with C-q . in the calendar. This won't work with pasted text snippets containing dates. > You can also customize the local map: > > ;; Unbind "." in Org's calendar: > (define-key org-read-date-minibuffer-local-map (kbd ".") nil) > > ;; Bind "@" to `calendar-goto-today': > (define-key org-read-date-minibuffer-local-map > (kbd "@") > (lambda () (interactive) (org-eval-in-calendar > '(calendar-goto-today Using a character which usually is not used in sentences which refer to dates and times would help both usage scenarios. While I can't find an example ATM, I remember to have seen combined date-time representations like "2013-03-04@12:30". Characters typically not used in date/time representations are (to my little knowledge): `§', `$', `%', `&', `=', `#', `\', `_', `´', ``' these are normally not used in normal sentences which contain date/time information (as opposed to e.g. `,', `:', `;') and most of them are typically present on keyboards (perhaps not the `§' which is part of German keyboards, which says a lot about German culture I guess). These characters are also not mentioned with special meaning in the org manual on this topic ((org)Top > Dates and Times > Creating timestamps > The date/time prompt). Wouldn't it be better to have one of these as a *default* setting for calendar-goto-today? Or: would it help to restrict the special meaning of `.' as a reference for `today' only for the first character of the date picker input? This would correspond with the usage advise "Generally, the information should start at the beginning of the string" in the org-mode manual and at the same time with the long-standing meaning of `.' for `today' for Emacs calendar users while still allowing to paste date/time information from sources outside the Emacs/org-mode universe. Sorry for my lousy command of the English language and thanks for considering this anyway, Gregor
Re: [O] Org-mode outside Org-mode
Samuel Wales writes: > Great write-up, Thorsten. thanks > There is a whole other set of options also. I don't know if they are > close enough for you to include, but it's worth pointing them out. > > These are in the general category of Org annotations. Instead of > editing Org in a temporary buffer, you use a real, permanent Org file > (can include an agenda file). > > There are two types of options: those that allow you to use Org to > annotate external files without changing those files, and those that > allow you to annotate external files by putting persistent markers in > them. > > In both types, you can in principle do C-c ' to get to your Org agenda > files location from your external files, and the same thing in > reverse. > > The existing mechanisms include org-pua.el, org-registry.el, and > org-annotate.el. > > In principle, you should be able to annotate web pages in w3m.el and > dired entries and info notes also. > > To me, there is a lot of possibility here. > It should also be possible to put an ID marker in an external file, > which corresponds exactly to the Org IDs in a canonical entry in your > agenda files. Then C-c ' can bounce between the external file and > your agenda file. please see my recent post about 'navi-mode' for Org-mode buffers. 'navi-mode' actually is a kind of permanent associated buffer tightly coupled to the original Org-mode or source code buffer. It uses markers to allow bouncing between the associated 'twin-buffers', but non of the libraries you mention. However, I worked out my own system to ensure that the *Navi* buffer is always up-to-date after modifying the original-buffer, and to locate point at a logical position in the navi-buffer even when the view (on the original-buffer has changed drastically). The temporary editing of source-code in Org-mode buffers is inspired by org-src.el (or Org Babel), its very fast and convenient, just like editing source-code blocks in Org-mode. Just try it out, maybe it is similar to what you imagine (only with different implementation). -- cheers, Thorsten
Re: [O] [PATCH] Process hlines in imported tables
Hi Achim, Achim Gratz wrote: > Rick Frankel writes: >> Missed verbatim. Thanks for the pointer, it works, but i think that >> perl is double-processing returned values. If we do the same things in >> elisp i get (my) expected results: >> >> #+begin_src elisp :results raw >> "|c1|c2| >> |- >> |a|1| >> |b|2|"; >> #+end_src > > Elisp is different from all other languages: it doesn't do any > processing of strings to begin with for value returns. The reason that > Perl processes "raw" results is that org-babel-result-cond does not > switch to the "scalar" path for this condition, which is why you need > the extra "verbatim". It probably should, though, so if Eric agrees > then I will push a change that does this. IIUC, wouldn't that be changing the default answer to "how to interpret the results" just for Perl? While the default answer for all languages seems to be "table"? Best regards, Seb -- Sebastien Vauban
Re: [O] Item task_id not being used in taskjuggler export & tj prefixing
Hi John, regarding your "potential" IRC date with Christian Egli, I would like to join, if I*ll find the time. For when is it scheduled? I have also posted a base for discussion here on the list. Thanks and best regards, Matt Am 01.04.2013 23:53, schrieb John Hendy: > On Mon, Apr 1, 2013 at 3:56 PM, Buddy Butterfly > wrote: >> Hi, >> >> regarding your example >> >> ** Milestones :M: >> *** Task >> :PROPERTIES: >> :task_id: M2 >> :depends: T8 >> :END: >> >> ** Technical :T: >> :PROPERTIES: >> :task_id: T >> :END: >> *** Task >> :PROPERTIES: >> :task_id: T8 >> :duration: 1d >> :END: >> >> >> I would like to discus what I mean with a prefix. >> At the moment oex tries to mirror some functionality of >> tj to org mode. From an architectural point of view I >> would do this only for few selected functionalities. >> Otherwise you developers have to always adapt code to >> tj. If you would implement generic tj properties that >> will be exported as is, then one could easily write >> the tj stuff itself. >> >> The problem becomes obvious with your example above. >> Herr you expect that T8 would be unique across all >> tasks. If there are some other task paths with a task of >> T8 then this will not work. You will always run after >> tj implementing what they have implemented. Why not >> write: >> >> :depends: !!T.T8 >> >> directly? This is what should be done. Leave the tj >> logic to tj and do not try to map it to org-mode. >> The more you map the more difficult to maintain, etc. >> > I agree and would prefer this. Especially since folks wanting to > export and being allowed to access tj functionality through drawers > are probably going to anticipate using actual tj syntax in those > drawers. Since tj only forces unique global ids (one can have M.T8, > T.T8, etc.), this would solve the issue of ambiguity should one decide > to use non-globally unique task ids. In fact, many projects may very > well use a lot of repetitive tasks with the same properties. > > In mine, I have some tasks regarding shipping products to various > countries. This way I could just have a bunch of country-specific > headlines like: > > * Country > ** Ship product > > * Country 2 > ** Ship product > > And could give all the ** Ship... tasks the same id since their > Country parent would make it globally unique. > > For now, I'm just happy to have functionality restored so I can use > Org and not hand-edit the files after exporting :) I have a potential > IRC date with Christian Egli sometime this week... perhaps you should > join and add your feedback? One of my other points of input would be > that something like C-c l (Org store link at point) would be great. > Unique ids could be inserted as depends with some simple key strokes > and I would't have to use numbered IDs at all. They'd stay with the > tasks no matter where I moved them. > > For that... I'd actually prefer *not* to have to explicitly name the > parent since they could move wherever I put them with no consequence. > > > John
Re: [O] #+bind: org-html-preamble
Hi Nicolas, Nicolas Goaziou writes: > Bastien writes: > >> Hi Nicolas, >> >> Nicolas Goaziou writes: >> >>> It is replacing old `org-export-allow-BIND' (note that they do not share >>> the same set of possible values). >> >> Is there a reason for not allowing 'confirm? > > Yes. It is a pain in the neck to implement, and not vital since you can > specify it as a buffer-local variable anyway. But it *was* implemented? If re-using the previous implementation is not a pain in the neck, I'd favor re-using it. >> Also, I'd rather stick to the old name since it is good enough >> and will spare many users with the hassle of finding out how to >> correctly set the new variable, which is very sensitive. > > It isn't sensitive: it defaults to nil. Therefore a user unable to find > it is still safe. Moreover, it will be documented, won't it? See below. >> What do you think? > > I didn't like gratuitous caps in the old name. I prefer the new one. > Other than dubious aesthetics reason, I don't mind its name. I'd like to re-use the old name. I don't like gratuitous caps in variable names too, but here they directly refer to the normal appearance of #+BIND. If we re-introduce the old name, whether it defaults to nil or not will potentially break users configuration, since a 'confirm value will either throw an error or (more dangerously) be interpreted as t. So, if we can re-use the old implementation and the old name, I'm for it as it is more flexible. -- Bastien
Re: [O] phone links...
On Thu, Apr 04, 2013 at 10:26:53AM +0200, Michael Strey wrote: [...] > Usually my phone links look like [[tel:+49 351 4129535]]; but since I > imported data sets from a larger contact data base that had evolved over > time, I ended up with stuff like this in my data base: > 1. [[tel:0033 (0) 4568-33]] > 2. [[tel:+49 (0)3 8899 66]] > 3. [[tel:0351 41295-35]] > 4. [[tel:0351/4129535]] > 5. [[tel:(0351) 412 95-35]] > > My filter function currently handles the cases 1. to 4. but (for no > other reason than carelessness) not 5. [...] Here is a re-work of the filter function that handles all off the above cases correctly. #+BEGIN_SRC emacs-lisp (defun trim-phone-number (phonenumber) "Remove whitespaces from a telephone number" (setq trimmed_phonenumber (mapconcat 'identity (split-string (mapconcat 'identity (split-string phonenumber "(0)") "") "[()/ -]") ""))) #+END_SRC I'm a Elisp newbie. I'm sure that there are smarter solutions to solve this problem. Regards -- Michael Strey www.strey.biz
[O] [NEW] navi-mode for org files
Hi List, I made navi-mode (=> super-fast buffer navigation, visibility-cycling, structure-editing, and much more, with one-key commands in an associated read-only *Navi* buffer) work with Org-mode buffers too. The basic things work, but there are still keyword-searches and keybindings to define. To check it out and get an idea what its all about, do the following: 1. Download these files to a place where Emacs can find them and do 'M-x load-file' on navi-mode.el ,- | https://github.com/tj64/navi/blob/master/navi-mode.el | https://github.com/tj64/outorg/blob/master/outorg.el | https://github.com/tj64/outshine/blob/master/outshine.el `- 2. Download Bernt Hansen's amazing Org-tutorial and switch to its Org-mode buffer (we use it as example Org-mode buffer) ,-- | http://doc.norang.ca/org-mode.org `-- 3. Type 'M-s n' (or 'M-x navi-search-and-switch') 4. do 'M-x menu-bar-mode' if menus are disabled for your Emacs and have a look at the "navi" menu 5. Play around in the *Navi:<>* buffer: - use 'n' and 'p' to move down and up on the 1st-level headers shown - use '1' '2' and '3' to switch between visible header levels - use 'SPC' and 'DEL' to move page-up and page-down - use to cycle visibility of whole original-buffer - use to cycle visibility of subtree at point - use 'd' to display subtree at point in original-buffer - use 'o' to switch to subtree at point in original-buffer - use 'M-s M-s' to switch back to *Navi* buffer - use 'b' to show all src-block headlines (and 'd' and 'o' on them) - use 'C-1 b', 'C-2 b' and 'C-3 b' to show the source blocks embedded in the headlines (level 1 to 3) - use 'E' to make the *Navi* buffer editable (changes are applied immediately to the original buffer (great in combination with - keyboard-macros) - type C-c C-c to make *Navi* buffer read-only again (6. Want more? - check the 'navi-menu' for more commands - type 'h' to see the (customizable) user-defined keyword-searches and their keybindings - read the comment sections of the three libraries 'outshine', 'outorg' and 'navi-mode' or the README-files on Github - read the Worg article: http://orgmode.org/worg/org-tutorials/org-outside-org.html) , | PS | | Please note that all this is available for your source code buffers | too (e.g. in Emacs Lisp) when you structure them the 'outshine' way. | | Use outorg.el, outshine.el or navi-mode.el as example files to see what | I mean (read comment-section of outshine.el for installation tips). | | Do 'M-s n' on one of them to open a *Navi* buffer. Try the the | commands from list item (5) above and don't forget to checkout command | 'e' - it is extremely useful since it opens the subtree at point (or, | with prefix, the whole Emacs Lisp buffer) in a temporary Org-mode edit | buffer. ` -- cheers, Thorsten
Re: [O] Bug: SETUPFILE directive not working [8.0-pre (release_8.0-pre-10873-gafb59b @ /home/mrb/dev/emacs/packages/org-mode/lisp/)]
On do 04-apr-2013 15:22 Carsten Dominik wrote: > I think the change is that you now need to put the file names into > quotes. I am not entirely sure why, but I guess Nicolas had a reason > for it. This does not make a difference for me. I should have been added that in the first place in the bug report. marcel -- Marcel van der Boom -- http://hsdev.com/mvdb.vcf HS-Development BV-- http://www.hsdev.com We use bitcoin! -- http://bitcoin.org
Re: [O] #+bind: org-html-preamble
Hello, Bastien writes: > Hi Nicolas, > > Nicolas Goaziou writes: > >> It is replacing old `org-export-allow-BIND' (note that they do not share >> the same set of possible values). > > Is there a reason for not allowing 'confirm? Yes. It is a pain in the neck to implement, and not vital since you can specify it as a buffer-local variable anyway. > Also, I'd rather stick to the old name since it is good enough > and will spare many users with the hassle of finding out how to > correctly set the new variable, which is very sensitive. It isn't sensitive: it defaults to nil. Therefore a user unable to find it is still safe. Moreover, it will be documented, won't it? > What do you think? I didn't like gratuitous caps in the old name. I prefer the new one. Other than dubious aesthetics reason, I don't mind its name. Regards, -- Nicolas Goaziou
Re: [O] Bug: SETUPFILE directive not working [8.0-pre (release_8.0-pre-10873-gafb59b @ /home/mrb/dev/emacs/packages/org-mode/lisp/)]
On 4 apr. 2013, at 14:51, Marcel van der Boom wrote: > > 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. > > > Using the #+SETUPFILE directive has stopped working for me in version > 8.x. I use a line at the bottom of moste of my org files like so: > > #+SETUPFILE: ~/etc/org-config.org > > This works fine in 7.9.4. I think the change is that you now need to put the file names into quotes. I am not entirely sure why, but I guess Nicolas had a reason for it. - Carsten
Re: [O] [PATCH 0/3] synctex support for pdf export
Hello, Aaron Ecay writes: > Now that this has come up, I have looked at it more. It appears that > the /usr/share/emacs/site-lisp directory is not added to load-path in > the async export process. I guess that it should be, since users’ > init.el files could rely on libraries that are found there. This is debatable. I think that the sub-process shouldn't load too much libraries. In your case, you effectively need to tweak `org-export-async-init-file'. > This will make the problem very difficult, if not impossible. Generally > speaking, the buffer that the export functions see bears only a loose > relationship to the original buffer, since babel blocks, #+include > directives, etc. have changed the text. I have tried to think of ways > to get around this fact, since working with the synctex file requires > knowing the original line number. This is the best I could do. [...] > Do you have any ideas about how this might be overcome? What is needed > is to know, for any line in the exported output, which line of the org > file it corresponds to (within some small margin of error). I don't think there is a complete solution to this problem. Though `org-export-before-processing-hook' allows to work on an exact copy of the buffer being exported before any file is included and any Babel block executed. You can add text properties there. And with `org-export-before-parsing-hook', you can check what parts of the buffer are new (generated from include keywords, macros and blocks). From there it may be possible to implement a lookup function which would find the appropriate line in the original buffer. Regards, -- Nicolas Goaziou
Re: [O] No dot in datepicker dialog
* Bastien wrote: > Hi Karl, Hi Bastien! > Karl Voit writes: > >> A couple of weeks ago[1] the datepicking dialog got modified such >> that a dot "." jumps to the current day. Handy for most Org-mode >> users I guess. > > "." is also the character used in M-x calendar RET to jump to today's > date. Ack. However, AFAIR I was able to use "." (to jump to $today) *and* type "31.12." (without C-q . or similar) before. So in my opinion, it is not interfering at all: It can be solved by interpreting "." (as goto-today) *only* if nothing else has been written into the minibuffer. This way, "." jumps to today *and* the user is able to enter "31.12." in the minibuffer in order to jump to the last day of December. > You can insert a dot with C-q . in the calendar. Thanks! This workaround solves my issue for now. > You can also customize the local map: Thanks for the pointer! Copied to my Emacs notes section :-) -- 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] Export a Subtree to an other .org file
Nicolas Goaziou writes: > What about the following? Looks gret! Feel free to apply it, -- Bastien
Re: [O] Export a Subtree to an other .org file
Hello, Bastien writes: > Nicolas Goaziou writes: > >> Anyway, it's possible to (require 'ox-org) and (org-export-to-file 'org >> "my-file.org"). > > I can see how useful it would be to have an interactive function and > keybindings for it. I can implement it if you want, but feel free to > beat me on this one. What about the following? Regards, -- Nicolas Goaziou >From 3d65b46c0cefb37808507ba1cc61c6c35e3230f2 Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou Date: Thu, 4 Apr 2013 15:09:22 +0200 Subject: [PATCH] ox-org: Add interactive functions to back-end * lisp/ox-org.el (org): Add a menu entry for the back-end. (org-org-export-as-org, org-org-export-to-org): New functions. * lisp/org.el (org-export-backends): Accept `org' as a loadable back-end. --- lisp/org.el| 1 + lisp/ox-org.el | 101 ++--- 2 files changed, 98 insertions(+), 4 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 06ba60a..1c15afd 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -495,6 +495,7 @@ depends on, if any." (const :tag " man Export buffer to MAN format" man) (const :tag " md Export buffer to Markdown format" md) (const :tag " odt Export buffer to ODT format" odt) + (const :tag " org Export buffer to Org format" org) (const :tag " texinfo Export buffer to Texinfo format" texinfo) (const :tag "C confluence Export buffer to Confluence Wiki format" confluence) (const :tag "C deckExport buffer to deck.js presentations" deck) diff --git a/lisp/ox-org.el b/lisp/ox-org.el index fdd009a..18925c5 100644 --- a/lisp/ox-org.el +++ b/lisp/ox-org.el @@ -20,9 +20,13 @@ ;;; Commentary: -;; This library implements an Org back-end for Org exporter. Since -;; its usage is mainly internal, it doesn't provide any interactive -;; function. +;; This library implements an Org back-end for Org exporter. +;; +;; It introduces two interactive functions, `org-org-export-as-org' +;; and `org-org-export-to-org', which export, respectively, to +;; a temporary buffer and to a file. +;; +;; A publishing function is also provided: `org-org-publish-to-org'. ;;; Code: (require 'ox) @@ -102,7 +106,15 @@ setting of `org-html-htmlize-output-type' is 'css." (timestamp . org-org-identity) (underline . org-org-identity) (verbatim . org-org-identity) -(verse-block . org-org-identity))) +(verse-block . org-org-identity)) + :menu-entry + '(?O "Export to Org" + ((?O "As Org buffer" org-org-export-as-org) + (?o "As Org file" org-org-export-to-org) + (?v "As Org file and open" + (lambda (a s v b) + (if a (org-org-export-to-org t s v b) + (org-open-file (org-org-export-to-org nil s v b (defun org-org-identity (blob contents info) "Transcode BLOB element or object back into Org syntax." @@ -132,6 +144,86 @@ Ignore keywords targeted at other export back-ends." (org-element-keyword-interpreter keyword nil))) ;;;###autoload +(defun org-org-export-as-org (&optional async subtreep visible-only ext-plist) + "Export current buffer to an Org buffer. + +If narrowing is active in the current buffer, only export its +narrowed part. + +If a region is active, export that region. + +A non-nil optional argument ASYNC means the process should happen +asynchronously. The resulting buffer should be accessible +through the `org-export-stack' interface. + +When optional argument SUBTREEP is non-nil, export the sub-tree +at point, extracting information from the headline properties +first. + +When optional argument VISIBLE-ONLY is non-nil, don't export +contents of hidden elements. + +EXT-PLIST, when provided, is a property list with external +parameters overriding Org default settings, but still inferior to +file-local settings. + +Export is done in a buffer named \"*Org ORG Export*\", which will +be displayed when `org-export-show-temporary-export-buffer' is +non-nil." + (interactive) + (if async + (org-export-async-start + (lambda (output) + (with-current-buffer (get-buffer-create "*Org ORG Export*") + (erase-buffer) + (insert output) + (goto-char (point-min)) + (org-mode) + (org-export-add-to-stack (current-buffer) 'org))) + `(org-export-as 'org ,subtreep ,visible-only nil ',ext-plist)) +(let ((outbuf + (org-export-to-buffer + 'org "*Org ORG Export*" subtreep visible-only nil ext-plist))) + (with-current-buffer outbuf (org-mode)) + (when org-export-show-temporary-export-buffer + (switch-to-buffer-other-window outbuf) + +;;;###autoload +(defun org-org-export-to-org (&optional async subtreep visible-only ext-plist) + "Export current buffer to an org file. + +If narrowing is active in the current buffer, only export its +narrowed part. + +If a region is active, export that region. + +A non-nil optional argument ASYNC means the process should happen +asynchronously. The r
Re: [O] [PATCH] Was: How to apply multiple TBLFM rules?
Hi Ippei, Ippei FURUHASHI writes: > This patch enables user to applies a temporal TBLFM line where you are in. > It is useful when you switch a formula to another. > I hope you liked this. I do! I've applied the patches (with some minor changes) on my local branch, it will be available when I push it later today. Thanks a lot for this new feature, -- Bastien
[O] org-outlook with Outlook 2010 on Windows 7
Hello, I have been trying to get org-outlook to work without any success. I am running Windows 7 and Outlook 2010. Yes, I wish didn't have to. I have put the VBA code generated by org-outlook-generate-vba into Outlook and then I changed the org-outlook-location to "c:/Program Files (x86)/Microsoft Office/Office14/OUTLOOK.EXE" in org-outlook.el. I didn't seem to work when I tried to change it through customize-group. I apparently get a link into an org document, but when click this link I get "ShellExecute failed: w32 error 2147749890". I have set up org-protocol according to the Org Manual (http://orgmode.org/worg/org-contrib/org-protocol.html). I later came across this setup: http://denihow.com/can-i-create-a-link-to-a-specific-email-message-in-outlook/ Which seems much simpler and looks to be sufficient for what I want, but this doesn't work either. It seems there is a problem with Dim doClipboard As New DataObject I have tried to search for help on VBA, that I have no prior experience with, for a clue as for what the problem is, but that has so far been a very frustrating experience. I am therefore hoping someone here has a working setup with Outlook 2010 and could point me in the right direction. I doesn't have to be with org-outlook, I just want have working links to Outlook messages in my org files. -- Cheers, Per
Re: [O] No dot in datepicker dialog
Hi Karl, Karl Voit writes: > A couple of weeks ago[1] the datepicking dialog got modified such > that a dot "." jumps to the current day. Handy for most Org-mode > users I guess. "." is also the character used in M-x calendar RET to jump to today's date. > However, this interferes with another feature I used quite often: I > was able to enter "31.12." to quickly select 31st of December, for > example. > > Please notice that (at least) in German speaking countries, it is > common to use "31.12." and not "12/31" or similar. > > So in current Org-mode (git), I can not enter the character "." > because it does not end up with a dot in the bottom line. > > Is there a way to customize this behavior? You can insert a dot with C-q . in the calendar. You can also customize the local map: ;; Unbind "." in Org's calendar: (define-key org-read-date-minibuffer-local-map (kbd ".") nil) ;; Bind "@" to `calendar-goto-today': (define-key org-read-date-minibuffer-local-map (kbd "@") (lambda () (interactive) (org-eval-in-calendar '(calendar-goto-today HTH, -- Bastien
Re: [O] [RFC] new :post header argument for post-processing of code block results
Eric Schulte writes: > Done. Thanks! -- Bastien
[O] Bug: SETUPFILE directive not working [8.0-pre (release_8.0-pre-10873-gafb59b @ /home/mrb/dev/emacs/packages/org-mode/lisp/)]
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. Using the #+SETUPFILE directive has stopped working for me in version 8.x. I use a line at the bottom of moste of my org files like so: #+SETUPFILE: ~/etc/org-config.org This works fine in 7.9.4. Emacs : GNU Emacs 24.3.4 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.0) of 2013-03-30 on mrb Package: Org-mode version 8.0-pre (release_8.0-pre-10873-gafb59b @ /home/mrb/dev/emacs/packages/org-mode/lisp/) -- Marcel van der Boom -- http://hsdev.com/mvdb.vcf HS-Development BV-- http://www.hsdev.com We use bitcoin! -- http://bitcoin.org
Re: [O] Org-mode as a metalanguage: calling SQL "functions"
"Sebastien Vauban" writes: > Hello Eric, > > Eric Schulte wrote: At this point I'm not sure if the documentation or the code should be amended. I've personally never liked the args-in-block-name syntax, but I don't recall if we formally decided to abandon it, or if it has simply been broken in a recent commit. >>> >>> I am not sure if I have any say here, but I agree that the args in >>> name notation looks not as good and might be considered for >>> abolishment. >> >> Great, I agree wholeheartedly and I'll update the documentation >> accordingly (and take a look at lob-ingest to ensure it no longer uses >> this var-in-name style). > > I confirm that, following a discussion we had, you had decided to drop the > alternate syntax, a couple of months ago (more than 2 ;-)). > > Best regards, > Seb Great, so I'm not imagining things. Thanks Seb. -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [RFC] new :post header argument for post-processing of code block results
Bastien writes: > Hi Eric, > > Eric Schulte writes: > >> Bastien, please commit these whenever you want, or let me know and I can >> commit them. > > Please go ahead. > Done. > > If you have one minute, you can clone orgweb.git and send a patch > against Changes.org: > > ~$ git clone org...@orgmode.org:orgweb.git > > Otherwise I'll do it myself, with a small description of the new > feature. > Committed. Cheers, > > Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Nice blog post - Org-mode in Your Pocket Is a GNU-Shaped Devil
François Pinard writes: > rai...@krugs.de (Rainer M. Krug) writes: > >> Sanity - never heard of it. I am giving gnus a few weeks and then I wil >> see - I think I am getting used to it (*not* understanding it!) > > Hi Rainer! > > I surely tried many mail user agents (MUAs) in my life and, sad to say > :-), Gnus is undoubtedly the most featured and flexible, while being the > one which best respects various standards in the field. > > If I write "sad to say", this is because Gnus coupled me more intimately > with Emacs, while I tried hard to run away of it, to recover some sanity. > To no avail: after many years of abstinence, and with reluctance and > dismay, Org got me back in it. Org is so good that I could not resist. I used org more or less exclusively for literate programming in R, and I never really got used to emacs and elisp - but even though, org kept me with emacs - I don't want to miss org and babel with ess when writing code! And now it is gnus... > > In the meantime, despite I found some MUAs quite impressive, I knew deep > down that none really match Gnus. So, when Org thrown me back in Emacs, > and given Org and Gnus integrate rather well with one another, Gnus was > the next logical step, which I do not regret yet. After two days, I was frustrated with gnus, andstarted thunderbird again... When after five minutes thunderbird was still unresponsive and using one of my two cores, I decided that's it - gnus is so much faster and when I search with notmuch, I have everything I need for now (well - next step is the google calendar...). > > A tiny example from yesterday. Knowing that Google Reader is soon going > to leave us, and after a few other unsatisfying tries, I finally opted > for Gwene + Gnus, and found out that the UI is even more efficient than > Google Reader, at least for me, to sort out what I want to read and what > I want to ignore. Some groups (Hacker News is typical) only yield links > in Gnus, with no text. It took me about one hour (my Gnus programming > is rather rusty) for adding a Gnus command opening many tabs at once, in > a graphical browser, for all articles I retain in Gnus for reading. Interesting. But As I read my news mainly on my iPad at home (to not distract me even more from work then gnus is already doing) I am trying feedly. > > I do not see any other environment in which such tiny projects would > stay reasonably small and tractable. Well - at the moment I don't see the end of gnus yet... Cheers and happy orging, Rainer > > François > <#secure method=pgpmime mode=sign> -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug
Re: [O] #+bind: org-html-preamble
Hi Nicolas, Nicolas Goaziou writes: > It is replacing old `org-export-allow-BIND' (note that they do not share > the same set of possible values). Is there a reason for not allowing 'confirm? Also, I'd rather stick to the old name since it is good enough and will spare many users with the hassle of finding out how to correctly set the new variable, which is very sensitive. What do you think? -- Bastien
Re: [O] Nice blog post - Org-mode in Your Pocket Is a GNU-Shaped Devil
Hi François, François Pinard writes: > It took me about one hour (my Gnus programming > is rather rusty) for adding a Gnus command opening many tabs at once, in > a graphical browser, for all articles I retain in Gnus for reading. That looks nice, is your hack public somewhere? I've been using Gwene + Gnus for feeds since one year or so now, and it is a clear win. And Gnus as the most funny manual ever. Another reason to stick to it. -- Bastien
Re: [O] Export a Subtree to an other .org file
Hi Nicolas, Nicolas Goaziou writes: > Anyway, it's possible to (require 'ox-org) and (org-export-to-file 'org > "my-file.org"). I can see how useful it would be to have an interactive function and keybindings for it. I can implement it if you want, but feel free to beat me on this one. Thanks, -- Bastien
Re: [O] Org-mode as a metalanguage: calling SQL "functions"
Hello Eric, Eric Schulte wrote: >>> At this point I'm not sure if the documentation or the code should be >>> amended. I've personally never liked the args-in-block-name syntax, but >>> I don't recall if we formally decided to abandon it, or if it has simply >>> been broken in a recent commit. >> >> I am not sure if I have any say here, but I agree that the args in >> name notation looks not as good and might be considered for >> abolishment. > > Great, I agree wholeheartedly and I'll update the documentation > accordingly (and take a look at lob-ingest to ensure it no longer uses > this var-in-name style). I confirm that, following a discussion we had, you had decided to drop the alternate syntax, a couple of months ago (more than 2 ;-)). Best regards, Seb -- Sebastien Vauban
Re: [O] Export a Subtree to an other .org file
Hello, Hsiu-Khuern Tang writes: > * On Wed 03:35PM, 03 Apr 2013, John Hendy (jw.he...@gmail.com) wrote: >> On Wed, Apr 3, 2013 at 2:31 PM, Steve Prud'Homme wrote: >> > Message : >> > No command associated with key ^S >> > >> >> Bastien's response was for the new exporter and your C-e 1 command >> indicates you're not using that version yet. I'm on the new exporter, >> so I can't recall what old options looked like, but from the manual >> could you try ASCII? >> - >> http://orgmode.org/manual/ASCII_002fLatin_002d1_002fUTF_002d8-export.html#ASCII_002fLatin_002d1_002fUTF_002d8-export >> >> Perhaps you could just export that to a buffer and then save as *.org >> instead of the default export format of .txt? > > I think the ascii export does not produce a file in Org format. > > The old exporter function org-export-as-org may do the trick for Steve. > > I too find it useful to export to org, and would love to see this implemented > in the new exporter. I rely on this together with the SELECT_TAGS and > EXCLUDE_TAGS keywords to create an Org file with a subset of the headings, not > just a subtree. Is there a new exporter function that does this? There's an org back-end for the new export framework (see ox-org.el). It doesn't provide any interactive function, though. Anyway, it's possible to (require 'ox-org) and (org-export-to-file 'org "my-file.org"). Regards, -- Nicolas Goaziou
Re: [O] Local footnotes -> inline
Hello, Bastien writes: > Hi Alan, > > Alan L Tyree writes: > >> G'day, >> Some time back there was mention of converting Local footnoted (defined >> at end of outline node) to inline footnotes and vice-versa. > > Yep, I suggested this. > >> Is there a way to do this? > > Not currently. > >> Or has anyone defined private functions to do it? >> >> Local footnotes are easier to read, but inline notes a easier to cut and >> paste. > > Help is welcome here, I hope someone can come up with a hack. Such a function would be fragile since inline footnotes contents are only a subset of regular footnotes contents. Regards, -- Nicolas Goaziou
Re: [O] phone links...
Hi Robert, Robert Goldman writes: > The two files are below, in hopes of getting suggestions for improvement > so that someday this could find itself into contrib/. Looks like a good start -- please keep us updated about your progress and your will to include this in contrib/, I'm sure many users would enjoy it. Thanks! -- Bastien
[O] Help with beamer
I am preparing a presentation with or-mode and beamer. I am using :PROPERTIES: :BEAMER_envargs: [<+->] :END: to make list elements appear one by one. When creating handouts, I want to supress the build effect (it works by creatin many slides unnecessary in printout) Is there a way of using a global variable to enable or disable all these blocks controlling the build effects so I can avoid changing them all one by one?
Re: [O] Nice blog post - Org-mode in Your Pocket Is a GNU-Shaped Devil
rai...@krugs.de (Rainer M. Krug) writes: > Sanity - never heard of it. I am giving gnus a few weeks and then I wil > see - I think I am getting used to it (*not* understanding it!) Hi Rainer! I surely tried many mail user agents (MUAs) in my life and, sad to say :-), Gnus is undoubtedly the most featured and flexible, while being the one which best respects various standards in the field. If I write "sad to say", this is because Gnus coupled me more intimately with Emacs, while I tried hard to run away of it, to recover some sanity. To no avail: after many years of abstinence, and with reluctance and dismay, Org got me back in it. Org is so good that I could not resist. In the meantime, despite I found some MUAs quite impressive, I knew deep down that none really match Gnus. So, when Org thrown me back in Emacs, and given Org and Gnus integrate rather well with one another, Gnus was the next logical step, which I do not regret yet. A tiny example from yesterday. Knowing that Google Reader is soon going to leave us, and after a few other unsatisfying tries, I finally opted for Gwene + Gnus, and found out that the UI is even more efficient than Google Reader, at least for me, to sort out what I want to read and what I want to ignore. Some groups (Hacker News is typical) only yield links in Gnus, with no text. It took me about one hour (my Gnus programming is rather rusty) for adding a Gnus command opening many tabs at once, in a graphical browser, for all articles I retain in Gnus for reading. I do not see any other environment in which such tiny projects would stay reasonably small and tractable. François
[O] MobileOrg app not available in the Belgian App Store?
Hi, I wanted to install the MobileOrg app on my iPhone, but iTunes claims that there is no such app in the Belgian App Store?! Did I miss something? Guido -- It was Penguin lust... at its ugliest. http://vanhoecke.org ... and go2 places!
Re: [O] Nice blog post - Org-mode in Your Pocket Is a GNU-Shaped Devil
Christian Moe writes: > Been there, nearly did that, then opted for mu4e over gnus, to > preserve remains of sanity. Sanity - never heard of it. I am giving gnus a few weeks and then I wil see - I think I am getting used to it (*not* understanding it!) I use notmuch for email indexing, so I liiked at notmuchs email capabilities, and I decided to look at gnus. Maybe mu4e is next - I will see. Cheers, Rainer > > Cheers, > Christian > > Rainer M. Krug writes: > >> Hi >> >> I stumbled upon this blog post : >> http://mph.puddingbowl.org/2010/02/org-mode-in-your-pocket-is-a-gnu-shaped-devil/ >> >> It is from 2010, but it describes my feelings perfectly - I just started >> using gnus. >> >> Cheers and thanks everybody for building and contributing to org-mode, >> >> Rainer > <#secure method=pgpmime mode=sign> -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug
Re: [O] Restore an archived subtree - Restauration d'une branche spécique archivée
Bastien writes: > Hi Steve, > > "Steve Prud'Homme" writes: > >> Hi, I archive with C-c C-x C-a on a .org_archive file. >> >> How can I restore a subtree. It is possible > > Right after C-c C-x C-a you can do C-/ to undo. > > But you cannot restore subtrees archived at arbitrary time in the > past. <#secure method=pgpmime mode=sign> I was thinking about this also for some time, as I sometimes use the archive in literal programming to store some code chunks which I might need later again. I understand that it is not possible to store in the archive a link to the location to which the subtree should be restored as edits will change the location. But what about assigning each archived subtree an ID which is stored together with the snippet in the archive file, and then put at the location in the original file a property giving the ID of the archived snippet? In this way one could a) easily see what was archived from where, and b) restore the subtree to the location of the ID in the original file? I think it would be a nice little extra in the process of archiving. Cheers, Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug
Re: [O] MACRO and HTML escapes and migration to org-mode 8
Adrian Tritschler writes: >> #+MACRO: datetime @@html:$2@@ > > > Aha, and so it does. > > I thought I'd tried that prior to my posting, I know I tried a few > variations, must have made some mistake along the way. It'll take some time before I remember to indicate the backend after the @@'s, but I generally like the new syntax much better. Yours, Christian
Re: [O] MACRO and HTML escapes and migration to org-mode 8
On Tue, Apr 2, 2013 at 10:33 PM, Christian Moe wrote: > > Hi, Adrian, > > The fine manual is not yet up to date with the new exporter, so when you're > bitten, check http://orgmode.org/worg/org-8.0.html. > > The "@" html-tag quoting has been replaced with a generalized "export > snippets" syntax (currently described at > http://orgmode.org/worg/org-8.0.html#sec-8-1). > > This works: > > #+MACRO: datetime @@html:$2@@ Aha, and so it does. I thought I'd tried that prior to my posting, I know I tried a few variations, must have made some mistake along the way. Many thanks. Adrian -- Adrian Tritschler Melbourne, Australia
Re: [O] global keys not working on version 20130401
Chris writes: > M-x package-list and installed the latest version of org and it went back to > the previour issue reported. If you are installing from ELPA, you need to install in a fresh Emacs session where no Org function has been called yet. HTH, -- Bastien
Re: [O] Local footnotes -> inline
Hi Alan, Alan L Tyree writes: > G'day, > Some time back there was mention of converting Local footnoted (defined > at end of outline node) to inline footnotes and vice-versa. Yep, I suggested this. > Is there a way to do this? Not currently. > Or has anyone defined private functions to do it? > > Local footnotes are easier to read, but inline notes a easier to cut and > paste. Help is welcome here, I hope someone can come up with a hack. Best, -- Bastien
Re: [O] I have terminated my assignment
> >> You also stated that the main reason for your current behavior > >> is to delay Org 8.0, to create chaos and to annoy me. > > > > Yes. > > > > I would suggest that further emails from Jambunathan be ignored. The > more effort expended "reasoning" with him, the more time wasted by > members of the Org-mode community who are valuable contributors. +1 Vikas
Re: [O] Effort Per Day
Hello, daya writes: > There are some tasks on which I would like spend a specified time of the day. > I > would like to set a per-day effort on these tasks. The current effort system > seem to support effort per task, not effort per day. What is the recommended > way of doing this? Using a daily repeater for your task should be enough. Also check `org-clock-mode-line-total' for more options. HTH, -- Bastien
Re: [O] Restore an archived subtree - Restauration d'une branche spécique archivée
Hi Steve, "Steve Prud'Homme" writes: > Hi, I archive with C-c C-x C-a on a .org_archive file. > > How can I restore a subtree. It is possible Right after C-c C-x C-a you can do C-/ to undo. But you cannot restore subtrees archived at arbitrary time in the past. -- Bastien
Re: [O] Effort Per Day
daya writes: > There are some tasks on which I would like spend a specified time of > the day. I would like to set a per-day effort on these tasks. The > current effort system seem to support effort per task, not effort per > day. What is the recommended way of doing this? What about something like: *** TODO [#C] Read Mail/News :LOGBOOK: [...] :END: <2013-04-03 Mi .+1d> :PROPERTIES: :Effort: 0:45 :LAST_REPEAT: [2013-04-02 Di 18:29] :END: ?
Re: [O] Nice blog post - Org-mode in Your Pocket Is a GNU-Shaped Devil
Been there, nearly did that, then opted for mu4e over gnus, to preserve remains of sanity. Cheers, Christian Rainer M. Krug writes: > Hi > > I stumbled upon this blog post : > http://mph.puddingbowl.org/2010/02/org-mode-in-your-pocket-is-a-gnu-shaped-devil/ > > It is from 2010, but it describes my feelings perfectly - I just started > using gnus. > > Cheers and thanks everybody for building and contributing to org-mode, > > Rainer
Re: [O] css link colors for Worg are difficult to spot
John Hendy writes: > Then all I did was reverse the scheme -- unvisited/visited are now > light/dark greenish and the hover color is rust (dark red). Thanks -- this is what I did first but Suvayu found this confusing, so I inverted the colors... Maybe the trick is to make them more visible by "lightening" the colors. I'm definitely no expert on this, so help is welcome. -- Bastien
Re: [O] Nice blog post - Org-mode in Your Pocket Is a GNU-Shaped Devil
On Thu, Apr 04, 2013 at 11:28:23AM +0200, Rainer M. Krug wrote: > http://mph.puddingbowl.org/2010/02/org-mode-in-your-pocket-is-a-gnu-shaped-devil/ > > It is from 2010, but it describes my feelings perfectly - I just started > using gnus. What a great summary! That certainly sums it up: "The genius of org-mode is that you will eventually impose more complex features on yourself." I need that last paragraph in a poster. I wonder if we can quote him on t-shirts? Thanks for sharing. -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] global keys not working on version 20130401
Bastien altern.org> writes: > > Hi Chris, > > Chris Henderson gmail.com> writes: > > > I have installed version 20130401 on emacs 24.3 on os x mountain lion > > via M-x package list. But my global keys don't seem to be working. I > > get an error: > > See this excerpt from http://orgmode.org/elpa.html: > > , > | By default, Emacs loads packages after it loads your Emacs init file. > | > | We recommend intializing packages as early as possible in your Emacs > | init file so that your Org configuration will be correctly handled: > | > | ;; -*- emacs-lisp -*- > | (package-initialize);; Initialize & Install Package > | ;; (setq org-...) ;; Your custom settings > | > | The package initialization should happen before you require Org and > | set any Org options. > ` > > You surely need to add (package-initialize) before Org options in your > .emacs. Otherwise, Emacs will load the built-in Org and you will end > up with mixed autoloads. I have added (package-initialize) at the top of my .emacs. Gone on to org with M-x org-version: Org-mode version 7.9.2 (7.9.2-120-g20839c-elpa @ /Users/chris/.emacs.d/elpa/org-20121217/) and everything was working fine. M-x package-list and installed the latest version of org and it went back to the previour issue reported. M-x org-version was showing: Org-mode version 7.9.4 (7.9.4-elpa @ /Users/chris/.emacs.d/elpa/org-20130401/) Not sure what I am doing wrong.
Re: [O] [RFC] new :post header argument for post-processing of code block results
Hi Eric, Eric Schulte writes: > Bastien, please commit these whenever you want, or let me know and I can > commit them. Please go ahead. If you have one minute, you can clone orgweb.git and send a patch against Changes.org: ~$ git clone org...@orgmode.org:orgweb.git Otherwise I'll do it myself, with a small description of the new feature. Thanks, -- Bastien
Re: [O] problem opening web links
Hi, 42 147 writes: > These links apparently require their own instance of Firefox. (setq browse-url-firefox-new-window-is-tab t) HTH, -- Bastien
[O] Nice blog post - Org-mode in Your Pocket Is a GNU-Shaped Devil
Hi I stumbled upon this blog post : http://mph.puddingbowl.org/2010/02/org-mode-in-your-pocket-is-a-gnu-shaped-devil/ It is from 2010, but it describes my feelings perfectly - I just started using gnus. Cheers and thanks everybody for building and contributing to org-mode, Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug pgpEhlEZMpblb.pgp Description: PGP signature
Re: [O] phone links...
Hi Robert, On Wed, Apr 03, 2013 at 10:05:57AM -0500, Robert Goldman wrote: > On 4/3/13 Apr 3 -9:52 AM, Michael Strey wrote: > > This gives me the opportunitie to publish my own attempt to implement > > telephone functionality into org. I'm using Linphone > > (http://www.linphone.org/) instead of Skype. > > Thanks! I am folding the linphone code in to make org-phone more generic. Great! > Question: why the removal of "(0)"? For international calls? Why "(0)" only, > instead of any 0 prefix? > > Also, do you ever want to remove it anywhere but as a prefix? > If so, maybe DELETE is the wrong function call. Linphone requires the numbers in form 0033456833 or +33456833 respectively. Usually my phone links look like [[tel:+49 351 4129535]]; but since I imported data sets from a larger contact data base that had evolved over time, I ended up with stuff like this in my data base: 1. [[tel:0033 (0) 4568-33]] 2. [[tel:+49 (0)3 8899 66]] 3. [[tel:0351 41295-35]] 4. [[tel:0351/4129535]] 5. [[tel:(0351) 412 95-35]] My filter function currently handles the cases 1. to 4. but (for no other reason than carelessness) not 5. #+BEGIN_SRC emacs-lisp (defun trim-phone-number (phonenumber) "Remove whitespaces from a telephone number" (setq trimmed_phonenumber (mapconcat 'identity (delete "(0)" (split-string phonenumber "[ /-]")) ""))) #+END_SRC Regards -- Michael Strey www.strey.biz
[O] Bug in orgtbl-to-generic (did only show up in Gmane list)
Hi, Using my new and unregistered email-address the message did only show up in gmane list (http://comments.gmane.org/gmane.emacs.orgmode/68915). And a solution was provided there. I did not see the change in the repository yet, so I send this message here to the original mailing list.
Re: [O] clock-out broken?
Hi Robert, Robert Eckl writes: > with some changes from today seems clocking out is broken: This is fixed now, thanks for reporting this. -- Bastien
Re: [O] css link colors for Worg are difficult to spot
Bastien altern.org> writes: > > The angry unicorn is still in worg though ... > > And it's back on orgmode.org too. Well let me say it again, I don't like it at all. The old unicorn seemed to be blissful, which I think is what it should feel like using Org. Besides, the new logo has some hard-not-to-notice problems with perspective and the anatomy of the unicorn head. Regards, Achim.
