[O] org-mode - export as folder structure possible?
Hello, I need to create a rather complex folder structure. It is OK to create that in dired but I think even nicer and faster it would be to create an org-mode outline which then exports this folder structure to the org document's directory. This could even be extended to create blank files with file extension within the directory - maybe communicated to the exporter with list items. Can the org-mode exporter be used or easily programmed for this kind of application? * Folder - Registry.xls - document.doc ** Subfolder *** Subsubfolder - some_document.txt ** Subfolder 2 * Another folder ** another one - document.file_extension - ListB.xlsx With that functionality I could really thoroughly create a decent folder structure. With many people working on the windows server it becomes quite chaotic. Thanks in advance for any answer.
Re: [O] [bug] timed repeater shows up in wrong place
hi nicolas, thanks for your reply. some things that i expected from org x<=8 to occur are not occurring on the dates i expected or in the time grid. so i wonder: 1) what changed in repeater agenda behavior from org 8 to org 9 - at least one and possibly several 2) where in the code the changes are so i can revert it in git until this is fixed. of course, this might in principle be explained by a single change (see below). On 11/13/16, Nicolas Goaziou wrote: > I mean that a variable ignoring all repeaters in agenda is useful. It > means that, e.g., > > <2016-11-13 Sun +1d> > > is seen as > > <2016-11-13 Sun> > > To put it differently, this would ignore repeaters until the task is > marked as done, which is repeaters original purpose. ok, so you can see a need for a setting that implements "show NONE except the timestamp date". i.e. remove the repeater aspect of repeaters. i don't need such a feature, but it seems useful. > However `org-agenda-repeating-timestamp-show-all' seems to > do something different. yes, or at least different org 8 vs. org 9. ... it is with .+ that i am noticing the anomalies in org 9. i almost always use .+, so i am much more concerned about them in my own case, not + or ++. i was thinking of the mce i posted, but you were talking in general terms. > > AFAIU, a nil `org-agenda-repeating-timestamp-show-all' means that > nothing will appear on <2016-11-09 Wed>, but the task will be displayed > on <2016-11-15 Tue>, as if it was automatically marked as done without > my consent. Odd. so your understanding is that a repeat indicates having gone through the done state if nil? i think of it ALSO as a reminder, without cluttering up every date. > > Note that I could understand the use for that. But there is worse: > ><2016-11-09 Wed .+3d> > > In this case, I cannot possibly guess when the next repeat is going to > show, since it depends on the date at which the task is done. As it is STILL also a reminder that it needs doing at around this frequency. > a consequence, treating the above as <2016-11-09 Wed +3d> is just plain > wrong IMO. Every repeat displayed in the agenda could be inaccurate. iirc you indicated in an old email that you didn't want the variable to apply to .+ or ++ . i indicated to you that i found the usual org behavior (org 8 and previous) to be extremely useful. i believe the op, for whom you made the change, also queried whether the change should be optional. the release notes for org 9 did not indicate any change, but we are seeing changes from org 8 to org 9. so it seems possible that you made the change and that it went through to org 9 and that that is what we are witnessing. does that sound possible to you? which git delta do you think is relevant? === i don't think the only purpose of an occurrence is to indicate having gone through the done state. === i will try to explain. i also tried to explain it in the old email. i hope i don't make a mistake. i am fogged and limited in typing. i prefer the setting of showing today or on an upcoming date (org 8 nil) to the extreme settings of showing only the timestamp date or all (your nil or t). this gives me just enough information but not too much. there is valuable information in the repeater interval. it says "this is about the frequency this should be done". it doesn't have to be exact. === sometimes people forget to doneify the previous instance. sometimes they don't even DO the previous instance, but still want reminding. showing the repeater not on every date but on today or the nearest into the future says "popping up again at about the same frequency -- either you forgot to doneify or you did not do it". org 8 reminded me "you went through ANOTHER cycle without doneifying this .+!". even in the time grid if it is timed. === it's a reminder frequency that scales with the repeater interval. that's what i need. === another factor is appt, which activates when something is in today's time grid. org 9 breaks that. if i did not do a task. i don't get reminded by appt in org 9. === bubbling down in a sched nx line is not enough. that becomes decreasingly looked at. your use case is different. you probably always look at all of your sched. nx. things that bubble down in sched. nx in org 9 could mean "long repeater interval" OR "you didn't doneify it". to me those are totally unrelated things. in org 8 if they mean the latter, i know that i will be reminded in a more visible place. === i am incapable of doing many things, but i need .+ semantics. i want to be reminded, but not on every occurrence, just today or nearest into future. the "pop up again, then bubble down, then pop up again" behavior is exactly what i need. then i doneify and it does not show until .+nd. so if possible, i'd like this customizable back to org 8 behavior. it's throwing me off quite a bit and i no longer can trust the repeaters in the agenda. > >>> makes
Re: [O] renumber/resort footnotes?
Hi Sharon, Sharon Kimble writes: > How can I renumber or resort my footnotes please? =C-u C-c C-x f= (=org-footnote-action=) offers an action to sort footnotes, in the footnotes section. You can also re-number them throughout the document from here. Stig
Re: [O] current, working org-protocol bookmarklet for firefox?
On Wednesday, 16 Nov 2016 at 12:39, Marco Wahl wrote: > The short-cut key is available after turning off all the vimperator keys > (which can be triggered by the "Insert"-key with my setting.) That's > the way I use it. D'oh... yes, thanks, works like a charm. -- : Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_8.3.6-1272-gc61ee8
Re: [O] ical export issues
> I use your approach but also use MobileOrg on Android as a channel to > connect org to Google. I essentially have my org calendar entries in > two different calendars on Google as a result. MobileOrg works well and > also "assimilates" any new entries put in directly into the Google > calendar back into my org files. Thank you Eric. I'm just trying the new MobileOrg, as I prefer its syncing method, but as yet I don't think it does calendar merging. Best wishes, Stephen
Re: [O] current, working org-protocol bookmarklet for firefox?
>> Don't know about bookmarklet but have you tried the addon >> >> http://chadok.info/firefox-org-capture/ > > This works well for me except that the short-cut key is not > recognised. This is probably due to some interaction with vimperator in > Firefox. But the little gnu icon works just fine. Looks like we use a similar environment. ;) The short-cut key is available after turning off all the vimperator keys (which can be triggered by the "Insert"-key with my setting.) That's the way I use it. Ciao Marco
Re: [O] current, working org-protocol bookmarklet for firefox?
On Tuesday, 15 Nov 2016 at 22:51, Marco Wahl wrote: [...] > Don't know about bookmarklet but have you tried the addon > > http://chadok.info/firefox-org-capture/ This works well for me except that the short-cut key is not recognised. This is probably due to some interaction with vimperator in Firefox. But the little gnu icon works just fine. Thanks. -- : Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_8.3.6-1272-gc61ee8
Re: [O] ical export issues
On Monday, 14 Nov 2016 at 21:50, Stephen Eglen wrote: > Hi everyone, > > I routinely export my diary entries to an ics file on the web so that > google calendar can display them. This normally works well, although it > is well known that the google calendar can take many hours before > updating the calendar. > > Has anyone got any neater approaches for keeping their org mode calendar > items in sync with google? I use your approach but also use MobileOrg on Android as a channel to connect org to Google. I essentially have my org calendar entries in two different calendars on Google as a result. MobileOrg works well and also "assimilates" any new entries put in directly into the Google calendar back into my org files. -- : Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_8.3.6-1272-gc61ee8
[O] ical export issues
Hi everyone, I routinely export my diary entries to an ics file on the web so that google calendar can display them. This normally works well, although it is well known that the google calendar can take many hours before updating the calendar. Has anyone got any neater approaches for keeping their org mode calendar items in sync with google? I've looked at org-gcal but I think I'm missing something (https://github.com/myuhe/org-gcal.el/issues/68) and there don't seem to be any reliable command line tools for syncing an .ics file with google that work under OAuth2. p.s. a small issue, but when I passed the org-generated .ics file through a validator, http://severinghaus.org/projects/icv/ it noted that: Your calendar is using an invalid newline format. Make sure to use \r\n to end lines rather than just \n (RFC 2445 ยง4.1). This doesn't seem to prevent google parsing the file though. Stephen
Re: [O] Capture templates - using result from %^g twice?
Hm - I seem to ask strange questions here. Any ideas? Rainer Rainer M Krug writes: > Hi > I have the following capture template and would like to re-use the tag > entered by %^g . I try to use %\2 but this is not working. > > Is there a way that I can re-use the tag entered by %^g and add it as a > property? > > Thanks, > > Rainer > > , > | ("s" "Change logged in buffer - for spreadsheet changes" > | entry (file+headline (lambda() (buffer-file-name)) "CHANGES") > | "* %^{Header of CHANGES item} :%^g: > | :PROPERTIES: > | :SHEET: %\2 > | :AUTHOR: Rainer M Krug, rai...@krugs.de > | :DATE: %T > | :END: > | %?") > ` -- Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 signature.asc Description: PGP signature