Re: [O] More flyspell-overlays removed
Hi Bjarte, Bjarte Johansen writes: > I made a patch to remove some more flyspell-overlays in #-blocks. The > reason for no : in the latex_header is that for some reason the : does > not get captured in dc1. flyspell is also removed for the full > verbatim, lstlisting and src blocks. > > I hope you guys can use the patch. I cannot apply it because it adds keywords at the wrong place. For example you cannot add "startup:" in the first (cond ((...))) because "startup:" is not a "backend specific content." And some other discrepencies. I'd welcome a patch for removing more flyspell overlays, but it has to be rewritten. I'm not using flyspell so someone else will have to do roll his sleeves. Thanks anyway for the patch! -- Bastien
Re: [O] A bit of work around org-clock-idle-time
Sorry, I forgot to reply to all when Nicolas D. answered the first email and took it off the list. Here is what you missed regarding org-clock.el: On Thu, Jul 19, 2012 at 2:33 PM, Nick Dokos wrote: > Nicolas Calderon wrote: > >> >> As for the max solution for idle time, I don't think it's a good >> solution. It solves the case where x11idle always return 0, but if >> you're active in X (x11idle always low) but not in emacs (high idle >> time), you'll end up in clock resolving mode. >> > > Fair enough, but it can still be done so as to simulate today's behavior > while avoiding the 0 case. Something like > > ((eq window-system 'x) > (let ((idle (org-x11-idle-seconds))) > (if (> idle 0) > idle > (org-emacs-idle-seconds The problem I see here is that 0 is a valid output for x11idle, so if the check is done while X11 is not idle, it will fall back to org-emacs-idle-seconds. From what I could see in the shell-command-to-string, there is no way to tell between an output from the program and the 0 the function returns if there is no output (can't find the command). That's why I added the additional check for the command existence. Optimally, that check would be done once at startup or the first time idle time is checked but I lack the elisp skills to perform such a "feat". That being said, the patch was merged in, so I don't know if it's an indication that I should not worry. Thanks, -- Nicolas Calderon On Fri, Jul 27, 2012 at 11:19 PM, Nick Dokos wrote: > Bastien wrote: > >> Nick Dokos writes: >> >> > o in org-clock.el, instead of checking whether x11idle exists or not, how >> > about something like this: >> > >> > ... >> > (eq window-system 'x) >> > (max (org-x11-idle-seconds) (org-emacs-idle-seconds)) >> > ... >> >> Yes, this is cleaner, thanks! >> > > Cleaner maybe, but it's not correct, as Nicolas C. pointed out. Nicolas > C. and I had an email exchange and I hope he will follow up with revised > patches. > > Nick
Re: [O] [ANN] Markdown export back-end in contrib
Nicolas Goaziou writes: > I modified the hash protection code a few hours ago. Could you update > org-md.el and try again? I downloaded the latest one and tried it. It did the trick, no issues. > If it still fails, could you provide an ECM? Erm, would you enlighten this old man and describe an ECM other than the thinguie used by fighter planes to avoid being shut down by enemy missiles? :) > > Done. Users can configure `org-md-headline-style' variable. Cool! -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] A bit of work around org-clock-idle-time
Nicolas Calderon writes: > Sorry, I forgot to reply to all when Nicolas D. answered the first > email and took it off the list. Here is what you missed regarding > org-clock.el: Thanks for resending. > Optimally, that check would be done once at startup or the first time > idle time is checked but I lack the elisp skills to perform such a > "feat". This is now the case. > That being said, the patch was merged in, so I don't know if it's an > indication that I should not worry. You should _always_ worry. :) -- Bastien
Re: [O] limitation: no tab in my headlines
Hi Giovanni, Inserting a tab in a heading is bizarre enough so that we can let users who dare doing it rely on ids. Thanks, -- Bastien
Re: [O] [ANN] Markdown export back-end in contrib
Luis Anaya writes: >> If it still fails, could you provide an ECM? > > Erm, would you enlighten this old man and describe an ECM other than the > thinguie used by fighter planes to avoid being shut down by enemy > missiles? :) http://orgmode.org/worg/org-faq.html#ecm --
Re: [O] [ANN] Markdown export back-end in contrib
Hello, Luis Anaya writes: > I downloaded the latest one and tried it. It did the trick, no issues. Great. > Erm, would you enlighten this old man and describe an ECM other than the > thinguie used by fighter planes to avoid being shut down by enemy > missiles? :) It's in the FAQ! http://orgmode.org/worg/org-faq.html#ecm It's used by bug reporters so maintainers are not shot by eisenbugs. Regards, -- Nicolas Goaziou
Re: [O] make install-info error messages
Achim,
this is fink's install-info, living in /sw/bin. it covers (now that i'm
looking) /usr/bin/install-info.
bash greg-minshalls-mbp: {1080} /usr/bin/install-info --version
install-info (GNU texinfo) 4.8
(it's odd, but not likely of interest, that fink claims
i texinfo 4.13-1001 GNU documentation system
that it's texinfo system is fairly recent, even if the install-info
appears quite old.)
i suspect i should take this up with the fink folks. sorry for the
nuisance.
cheers, Greg
Re: [O] local.mk and up2
Nick Dokos writes: > I said: > > , > | You can always redefine makefile variables on the command line: > | > | make SUDO= up2 > | > | will redefine SUDO to nothing for this run. > ` > > but I should also have added that you can redefine the variable in > local.mk as well for more permanence: > > SUDO = > > local.mk is included *after* default.mk, which is where the > > SUDO = sudo > > line originally defines the SUDO variable, so it overrides the > default. Thanks a lot, that worked wonderfully well. Now a single make keeps my org-mode up to date. Alan
Re: [O] org-caldav: Sync Org with external calendars through CalDAV (Owncloud, Google, ...)
Torsten Wagner writes: > Sync went ok however, I notice I have to log-out from the ownCloud > webmask... again maybe a ownCloud server setting Yes, Owncloud can be a bit finicky here. From my experience, you should not be fooled by its 4.x version number; it often behaves more like a 0.4. > The location was not synced yet. Yes, I will add that eventually. > Furthermore, I wonder how to use it finally. I can see the new entries > in the from-calendar.org file. Can I move them to appropiate places in > my working file? No. > What would happen to a sync in that case? You would get a double entry. > I guess my working scheme would be like this > > Create appointments in my org-file... > sync > on-the-go make changes or add new entries to the calendar > sync > move all from the file from-calendar.org to the right places in the > work org-file. > sync > > Is this the intended way of usage? That's what I'm aiming for. But it requires to do have a proper 2-way sync, which is not there yet. > Also, you said not to add the from-calendar.org file but why not using > the following scheme? > Read all appointments from from-calendar.org and sync them with the > calendar (they should be there already) mark all double entries in the > calendar to be still not in the original work file e.g. the title > could be [WIP] Title > That would remind people to move them out of from-calendar.org to the > right places. As soon as they removed them from from-calendar.org they > could be marked by using the title [org-file] Titel. That would help > people to tell them that they will finally find entries later in the > work file. A tag would esp. help if there will be a support for > multiple org-files to sync. > As for multiple org-files the org-agenda mechanism might be helpful. > It already enables to use several org-files to create an agenda. Maybe > syncing from there is easier?! These are good suggestions. The problem is, as already mentioned, to implement proper 2-way sync from CalDAV to Org. For this, the 'etags' from the CalDAV server have to be saved in the Org items as PROPERTIES. I guess not all people will be thrilled to have their Org items polluted by stuff like that, but it's the most straightforward and reliable way to do it. Another problem is that there's no unique mapping from iCalendar to Org items. The good news is that I've now fixed the problems with url-dav and xml.el in Emacs proper, meaning that org-caldav will work without any additional files with current Emacs from bzr (which will become 24.2). -David
Re: [O] MobileOrg and tags
Hi James, James Harkins writes: > I found a reference to a function, org-global-tags-completion-table, that > would collect all of the tags currently being used. So, as an experiment, I > made a small change to org-mobile.el [1]. And, magically, in index.org, now > I get: > > #+TAGS: Bug FarShore Hadron Hard Lament lily Lilypond. Can you try replacing the call to the function (org-global-tags-completion-table) by a call to the variable `org-tag-alist'? I'm not using org-mobile.el, so purely a shoot in the dark. But `org-tag-alist-for-agenda' doesn't seem necessary here, and using `org-global-tags-completion-table' is too time consuming. Thanks, -- Bastien
Re: [O] mobile-org, webdav, can't push (password not accepted)
James Harkins writes: > It would be worth an update to the manual to list the other sync > options. "Dropbox or WebDAV" sent me on a wild goose chase. Can you submit a patch for this? See http://orgmode.org/worg/org-contribute.html on prefered ways to create a patch. Thanks, -- Bastien
Re: [O] Bug: Include existing tags in index.org :Mobile: [7.8.11 (release_7.8.11.dirty @ /home/dlm/share/org-mode.git/lisp/)]
James Harkins writes: > 2. Every time the user tags a node with a new identifier, she has to > update org-tag-alist-for-agenda by hand. Or maybe (org-get-buffer-tags) will do the work. -- Bastien
[O] several column view dynamic block on sparse tree
Hi,
I would like to do have several dynamic blocks, that each works for a specific
tag and captures a time-summing column view on the sparse tree of the file
matching the current tag.
In other words, I would like to write something like this:
#+BEGIN: columnview :id global :width t :skip-empty-rows t :contents "%45ITEM
%10Time{:}" :match TAG1
#+END
#+BEGIN: columnview :id global :width t :skip-empty-rows t :contents "%45ITEM
%10Time{:}" :match TAG2
#+END
What is the right way to do this in org-mode?
I have been looking in the documentation and FAQ, but I did not get anywhere.
Background:
I am currently designing two university courses that cover roughly the same
topics. I would like to do the topic selection, time estimation (time needed
for a topic in class, time to solve an exercise) and scheduling (which
topic/exercise/..) to do in which class/week in one org-mode file that has as
the main tree a topic tree.
My idea was to have tags to identify topics I would do in a certain course, and
a family of tags (like courseA_a, courseA_b) to tag things I would do in a
certain lecture.
Now I could (with the above constructs) extract the topics and time-estimates
for the two different courses, and even for the single lectures of each course,
or the single weeks of assigned homeworks for the different courses.
Is this a reasonable setup?
Any comment or help is appreciated.
Riko
--
Riko Jacob
rja...@inf.ethz.ch
http://www.inf.ethz.ch/personal/rjacob/
[O] conceptual TODO help?
Hi guys, I have a few questions about todo states. I have these keywords defined: #+TODO: Do Doing DoBy DoLater | Did DidNot DidNever #+TAGS: @Beverly(y) @Bionca(a) I'd like to have a better understanding of the TODO sequence for any given task, assignment, or project. The states Do and Did are pretty obviously just TODO and DONE renamed. I can maybe add a DEADLINE:<2012-07-28 Sat> for the DoBy heading, and a SCHEDULED:<2012-07-28 Sat> for DoLater, but what can or should I do with Doing? Should I just leave it alone and look at it? I think I've seen TODO keywords defined (in the manual? list emails?) like "feedback", etc, but it seems like if I have a basic but comprehensive sequence I can put that kind of stuff in tags (Incidentally, what are the @ signs in front of tags for?). Are there any keywords I should add or remove? Should I get rid of DidNot and DidNever (implying not yet and never will)? My keywords are arbitrary and silly, but I'd like to better understand the states they label. Thanks, I hope I was clear, and sorry for the "basic question" noise.
Re: [O] Missing files in mobileorg-android when syncing using Windows and cygwin
Hi Mathias, Mathias Kegelmann writes: > Details and workaround are described on the issue page https:// > github.com/matburt/mobileorg-android/issues/246#issuecomment-7204576 > of the mobileorg-android github project. There is no mention of Emacs version on this page. Please send *all* relevant information directly on the list, that helps. For this problem, knowing Emacs version will certainly help, as `shell-quote-argument' should do the right thing on w32. -- Bastien
Re: [O] O[GSoC] Org-sync
Wes Hardaker writes: > Aurélien Aptel writes: > >> I plan on writing backends for Redmine, Bugzilla, Google Code, Google >> Task, Toodledo, Remember the milk. >> But I may not have the time to do them all. What backends would you >> like me to implement first? Something not in this list? > > I think a RtM plugin would be fantastic and a good example of > synchronizing with generic todo lists that other random people would > find interesting (not just coders). +1 Aurélien, feel free to start a RTM plugin :) -- Bastien
Re: [O] conceptual TODO help?
Aloha scrawler, scrawler writes: > Hi guys, I have a few questions about todo states. I have these > keywords defined: > > #+TODO: Do Doing DoBy DoLater | Did DidNot DidNever > #+TAGS: @Beverly(y) @Bionca(a) > > I'd like to have a better understanding of the TODO sequence for any > given task, assignment, or project. The states Do and Did are pretty > obviously just TODO and DONE renamed. I can maybe add a > DEADLINE:<2012-07-28 Sat> for the DoBy heading, and a > SCHEDULED:<2012-07-28 Sat> for DoLater, but what can or should I do > with Doing? Should I just leave it alone and look at it? I found the discussions of TODO states by John Wiegley, Charles Cave, and Bernt Hansen very helpful: http://orgmode.org/worg/org-tutorials/index.html#sec-2 I eventually set up my files along the lines laid out by Bernt, but I don't track things as exhaustively as he's able to do. hth, Tom > > I think I've seen TODO keywords defined (in the manual? list emails?) > like "feedback", etc, but it seems like if I have a basic but > comprehensive sequence I can put that kind of stuff in tags > (Incidentally, what are the @ signs in front of tags for?). > > Are there any keywords I should add or remove? Should I get rid of > DidNot and DidNever (implying not yet and never will)? My keywords are > arbitrary and silly, but I'd like to better understand the states they > label. > > Thanks, I hope I was clear, and sorry for the "basic question" noise. > > -- Thomas S. Dye http://www.tsdye.com
Re: [O] Missing files in mobileorg-android when syncing using Windows and cygwin
Hi Bastien, thanks for pointing out that the version is missing. I am running: ELISP> (emacs-version) "GNU Emacs 23.2.1 (i386-mingw-nt6.1.7601)\n of 2010-05-08 on G41R2F1" The issue with shell-quote is as follows: ELISP> (shell-quote-argument "c:/org/test") "c\\:/org/test" The problem is the backslash before the colon as quoting colons doesn't seem to be legal in Cygwin. - Mathias On 28 July 2012 20:06, Bastien wrote: > Hi Mathias, > > Mathias Kegelmann writes: > > > Details and workaround are described on the issue page https:// > > github.com/matburt/mobileorg-android/issues/246#issuecomment-7204576 > > of the mobileorg-android github project. > > There is no mention of Emacs version on this page. > > Please send *all* relevant information directly on the list, > that helps. > > For this problem, knowing Emacs version will certainly help, > as `shell-quote-argument' should do the right thing on w32. > > -- > Bastien >
Re: [O] Installation via el-get: info not added correctly
On Fri, Jul 27, 2012 at 2:03 AM, Achim Gratz wrote: > Markus Baden writes: > > I just installed org-mode via the recipe provided with the current > > development version of el-get [1]. Org-Mode is installed correctly > > into emacs.d/el-get/org-mode and the docs can be found in the doc > > subfolder. The recipe [2] adds the doc to the info via the :info "doc" > > property. However, when going to the info browser with C-h i the > > org-mode docs cannot be found. In the doc subfolder there is a file > > called "org" (no filename extension), which looks like the info file. > > After doing a "cp org org.info" the org-mode info shows up in the info > > browser. > > El-get for whatever reason seems to think that all info files have a > ".info" suffix, but they appear to never check if that assumption is > true. I don't understand how they set up the info tree further on from > looking at the sources. File a bug report for el-get I'd say. > Looking at this a bit this morning, I'm not sure that it is el-get (at least alone) that is insisting on the .info suffix. The portion of elisp in el-get that adds the .info suffix: #+begin_src emacs-lisp (if (string= (substring infofile -5) ".info") infofile (concat infofile ".info")) #+end_src (Side note, I did try a work around, https://github.com/SkydiveMike/el-get/commit/88920c84bbe4d814bae1e79cdda163315d8d8d24that doesn't work). Is only called if the ~dir~' file does not exist (and other conditions) and as part of creating a command string for ~/usr/bin/install-info~. Since an non-built (no execution of ~make~) Org mode Git clone has a ~dir~ file, this code is never called. I also don't believe that ~cp org org.info~ in ~$HOME/.emacs.d/el-get/org-mode/~ fixes things (I currently can't get the correct info to display using that).
Re: [O] More flyspell-overlays removed
On 28 Jul, 2012, at 11:27 , Bastien wrote: > I cannot apply it because it adds keywords at the wrong place. > For example you cannot add "startup:" in the first (cond ((...))) > because "startup:" is not a "backend specific content." And some > other discrepencies. OK, I understand. I should have spent some more time trying to understand the code. > I'd welcome a patch for removing more flyspell overlays, but it > has to be rewritten. I'm not using flyspell so someone else will > have to do roll his sleeves. I'd be willing to put in the effort to make a proper patch, but I need some help to understand what is going on in this function. It is not obvious to me. The places flyspell-overlays needs to be removed are in the startup, options, latex_header. Some of structures that might be used in latex like lstlisting and verbatim where the text also should not have flyspell-overlays. There are also some other places like label, caption and attr.
