[O] Bug: Patch for org-docview: make normal links from docview: links on export from org to html [7.9.3d (release_7.9.3d-1-g115bd7 @ /home/vdyadov/Work/Tools/emacs/share/emacs/24.2/lisp/org/)]
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. Pathch for org-docview.el is attached. Emacs : GNU Emacs 24.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.18.9) of 2012-12-25 on canopus-pc.elvees.com Package: Org-mode version 7.9.3d (release_7.9.3d-1-g115bd7 @ /home/vdyadov/Work/Tools/emacs/share/emacs/24.2/lisp/org/) diff -Naur a/org-docview.el b/org-docview.el --- a/org-docview.el2013-01-17 11:45:13.389208433 +0400 +++ b/org-docview.el2013-01-17 11:47:43.881896241 +0400 @@ -51,9 +51,20 @@ (autoload 'doc-view-goto-page "doc-view") -(org-add-link-type "docview" 'org-docview-open) +(org-add-link-type "docview" 'org-docview-open 'org-docview-link-export) (add-hook 'org-store-link-functions 'org-docview-store-link) +(defun org-docview-link-export (link description format) + "Export a docview link from Org files." + (let* ((path (when (string-match "\\(.+\\)::.+" link) + (match-string 1 link))) + (desc (or description link))) +(cond + ((eq format 'html) + (format "%s" + path desc)) + (t path + (defun org-docview-open (link) (when (string-match "\\(.*\\)::\\([0-9]+\\)$" link) (let* ((path (match-string 1 link)) Diff finished. Thu Jan 17 11:49:46 2013
[O] org-indent-mode sans-serif font support
org-indent-mode doesn't work well except on monospaced font. Is there a way around this? I want to use Arial font. (sans-serif font) But with org-indent-mode, the body and entry indents are misaligned, This is very apparent at higher indent levels.
Re: [O] commenting out a SCHEDULED line does not remove todo from agenda.
On 17.1.2013, at 06:02, Nick Dokos wrote: > Nick Dokos wrote: > >> Rainer Stengele wrote: >> >>> Hi! >>> >>> Imagine you have a todo like this: >>> >>> * TODO a task >>> SCHEDULED: <2013-01-16 Mi +2m> >>> >>> Now suppose you want to put that todo on hold. In order to no more see >>> the scheduled date in the agenda I comment out the "SCHEDULED" line. >>> I do not want to delete it because I maybe need it later again: >>> >>> >>> * TODO a task >>> # SCHEDULED: <2013-01-16 Mi +2m> >>> >>> The todo still appears in the agenda. >>> Is this not counterintuitive? >>> >> >> Try putting the # in column 1 (untested). >> > > I've now tested it and it is as I thought: the comment character has to > be in column 1. The reason is org-agenda-skip: > > , > | (defun org-agenda-skip () > | "Throw to `:skip' in places that should be skipped. > | Also moves point to the end of the skipped region, so that search can > | continue from there." > | (let ((p (point-at-bol)) to) > | (when (org-in-src-block-p t) (throw :skip t)) > | (and org-agenda-skip-archived-trees (not org-agenda-archives-mode) > | (get-text-property p :org-archived) > | (org-end-of-subtree t) > | (throw :skip t)) > | (and org-agenda-skip-comment-trees > | (get-text-property p :org-comment) > | (org-end-of-subtree t) > | (throw :skip t)) > | (if (equal (char-after p) ?#) (throw :skip t)) > | (when (setq to (or (org-agenda-skip-eval > org-agenda-skip-function-global) > |(org-agenda-skip-eval org-agenda-skip-function))) > | (goto-char to) > | (throw :skip t > ` > > It sets p to the point at the beginning of the line and then > checks if the character after it is '#'. Only then does it skip > the entry. And this is done for speed. Maybe Moore's law has progressed enough to relax this assumption? - Carsten > > Nick > > > >
Re: [O] org-caldav: New version with proper two-way sync
Eric S Fraga writes: Sure but the problem does not appear to be what I had originally thought. It turns out that all of my entries with non-ASCII characters happened to be SEXP based entries, of this form: #+begin_src org * Test entries %%(diary-anniversary 1971 03 13) Somebody's birthday (%d años) #+end_src Ummm, something has screwed up my email... I was playing with =use-hard-newlines= for email. Sorry about this. The example should have been (fingers crossed hoping this comes through fine this time): #+begin_src org * Test entries %%(diary-anniversary 1971 03 13) Somebody's birthday (%d años) #+end_src Hope it comes through correctly this time... -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3d-826-gbe0d87
Re: [O] org-mode failing on org-mobile-push with error
hi Jeff, I have the same behaviour. did you find any solution. br robin
[O] About `open formula'
In (info "(org) Editing and debugging formulas"): ` (`org-table-fedit-lisp-indent')' Pretty-print or indent Lisp formula at point. When in a line containing a Lisp formula, format the formula according to Emacs Lisp rules. Another collapses the formula back again. In the open formula, re-indents just like in Emacs Lisp mode. What does the `open formula' mean? I've searched the Org manual/FAQ and web, and I only found this: http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.html But it seems that the `open formula' doesn't mean this. -- Best regards, Xue Fuqiao. http://www.emacswiki.org/emacs/XueFuqiao
Re: [O] commenting out a SCHEDULED line does not remove todo from agenda.
Nick Dokos wrote: > Rainer Stengele wrote: > > > Hi! > > > > Imagine you have a todo like this: > > > > * TODO a task > > SCHEDULED: <2013-01-16 Mi +2m> > > > > Now suppose you want to put that todo on hold. In order to no more see > > the scheduled date in the agenda I comment out the "SCHEDULED" line. > > I do not want to delete it because I maybe need it later again: > > > > > > * TODO a task > > # SCHEDULED: <2013-01-16 Mi +2m> > > > > The todo still appears in the agenda. > > Is this not counterintuitive? > > > > Try putting the # in column 1 (untested). > I've now tested it and it is as I thought: the comment character has to be in column 1. The reason is org-agenda-skip: , | (defun org-agenda-skip () | "Throw to `:skip' in places that should be skipped. | Also moves point to the end of the skipped region, so that search can | continue from there." | (let ((p (point-at-bol)) to) | (when (org-in-src-block-p t) (throw :skip t)) | (and org-agenda-skip-archived-trees (not org-agenda-archives-mode) |(get-text-property p :org-archived) |(org-end-of-subtree t) |(throw :skip t)) | (and org-agenda-skip-comment-trees |(get-text-property p :org-comment) |(org-end-of-subtree t) |(throw :skip t)) | (if (equal (char-after p) ?#) (throw :skip t)) | (when (setq to (or (org-agenda-skip-eval org-agenda-skip-function-global) | (org-agenda-skip-eval org-agenda-skip-function))) | (goto-char to) | (throw :skip t ` It sets p to the point at the beginning of the line and then checks if the character after it is '#'. Only then does it skip the entry. Nick
Re: [O] org-caldav: New version with proper two-way sync
David Engster writes: Eric S. Fraga writes: I've tracked down the root of the various problems I have encountered with the synchronisation. It all comes down to character sets. I have some entries that have UTF-8 characters that are not present in ASCII, specifically accented characters and similar (latin1, basically, but not exclusively). Any such entries cause the synchronisation to fail. Could you post an example entry where this happens? Sure but the problem does not appear to be what I had originally thought. It turns out that all of my entries with non-ASCII characters happened to be SEXP based entries, of this form: #+begin_src org * Test entries %%(diary-anniversary 1971 03 13) Somebody's birthday (%d años) #+end_src (see the N TILDE character in the spanish word for years) The problem, however, seems related to the use SEXP entries and not the character set. Having said this, my org diary file has had the encoding changed out from under me so that all my UTF-8 characters have been mangled. I've not quite figured out how this happened or when it happened between yesterday and today. I cannot reproduce the problem at the moment. This may be coincidental and have nothing to do with org-caldav. However, it may be something to do with using org-caldav in emacs -batch mode and whether files get loaded in the same way. Still playing with this. Resuming a failed synchronisation seems to forget to try to bring in the external calendar entries into org? That happens last, so I wouldn't know why this would be skipped on resume. It's kinda hard to debug, though. Okay. The fact that descriptions are not synchronised for changed entries is something I understand but probably need to think about some more (in terms of default behaviour). Is there a practical limitation on the size of the description entry that could be synchronised? The default is 100 but would there be any harm in having this 1, 2 or even 3 orders of magnitude larger? Or even unlimited? Just wondering. I was wondering about that, too, but couldn't find any definite statements on the maximum length of the DESCRIPTION field. I only skimmed RFC 2445, though. Even if there is such a definite limit, I wouldn't count on servers to correctly implement that. I guess you just have to try what works. Thanks. I'll stick to the default behaviour you have chosen; it's good enough for most of my use cases and seems safest. Anyway, with respect to my problems, would you please have a look to see if you are assuming ASCII or similar and whether there is anything you can do about this? I (and many others, I assume) really do need to be able to work in UTF-8 at the very least. I will look into that. I'm pretty sure this is fixable. As mentioned above, I am now not sure if there are problems with ASCII vs non-ASCII encodings. I will keep playing. Thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3d-826-gbe0d87
[O] How to use org-capture with "dynamic ID" targets?
I'm trying to set-up some org-capture templates using the ID target
type. However, I need the ID to be determined either as the return value of
a function or as the value of a variable.
When I use a template such as
--8<---cut here---start->8---
("f" "The template description" table-line
(id "someIDstring")
"this is the template content"
:table-line-pos "II-1"
:immediate-finish t)
--8<---cut here---end--->8---
everything works as expected and a table in the headline with ID
"someIDstring" is used. However, if I try
--8<---cut here---start->8---
("f" "The template description" table-line
(id some_variable)
"this is the template content"
:table-line-pos "II-1"
:immediate-finish t)
--8<---cut here---end--->8---
or
--8<---cut here---start->8---
("f" "The template description" table-line
(id (some_function))
"this is the template content"
:table-line-pos "II-1"
:immediate-finish t)
--8<---cut here---end--->8---
then it does not work even if some_variable or (some_function) provides the
correct ID value. It seems that
(id something)
will always interpret "something" as a string (no matter if I put it inside
quotes or not).
Is it possible to achieve what I want with the current org-capture
implementation? If not, consider this as a feature request.
The reason behind this is that each month I want a different target table
for this capture template and I already implemented a function that returns
the correct ID. If I can somehow make the ID target type use the return
value of this function then this capture template will use the correct
table each month. If not, I would be forced to manually change the capture
template in the beginning of each month (something I will definitely
forget).
--
Darlan
Re: [O] =C-c '= isn't working to visit setupfile; bug?
On Wed, Jan 16, 2013 at 12:31 PM, Nicolas Goaziou wrote: > Hello, > > John Hendy writes: > >> I can no longer =C-c '= to visit the file listed in #+setupfile: > > It should be fixed now. Thank you for the report. > Confirmed fixed! Thanks so much, John > > Regards, > > -- > Nicolas Goaziou
Re: [O] org-caldav: New version with proper two-way sync
Vincent Beffara writes: > Works great for me, thanks! One thing that changed (but it was kind of > a glitch anyway, even if a nice one to have): events with several > timestamps now appear only once rather than one per timestamp. Not > sure if this is due to org-caldav or to recent evolutions in the > org->ics export. Anyway, not a big deal. That's a consequence of org-caldav now doing proper syncing. Every Org entry is linked through the UID to exactly one event in the calendar. If I would allow an entry to produce several events in the calendar, we would get duplicate UIDs there, which is not allowed. One could code around that (in fact, the iCalendar export already does that by putting stuff like 'DL' or 'TS' in front of the UIDs), but it would make syncing from the Calendar to Org much more difficult. > One thing hinted at in the docs, but I couldn't figure out how to do > it: how do you use an authinfo file? Mine seems to be ignored totally > ... The example given in the Readme machine www.google.com:443 port https login username password secret should work. If it doesn't, set `auth-source-debug' to 't' and look into the Messages buffer. Maybe it doesn't work properly on older Emacs versions; a lot has changed in auth-source recently. -David
Re: [O] org-caldav: New version with proper two-way sync
Eric S. Fraga writes: > I've tracked down the root of the various problems I have encountered > with the synchronisation. It all comes down to character sets. I > have some entries that have UTF-8 characters that are not present in > ASCII, specifically accented characters and similar (latin1, > basically, but not exclusively). Any such entries cause the > synchronisation to fail. Could you post an example entry where this happens? > Resuming a failed synchronisation seems to forget to try to bring in > the external calendar entries into org? That happens last, so I wouldn't know why this would be skipped on resume. It's kinda hard to debug, though. > The fact that descriptions are not synchronised for changed entries is > something I understand but probably need to think about some more (in > terms of default behaviour). Is there a practical limitation on the > size of the description entry that could be synchronised? The default > is 100 but would there be any harm in having this 1, 2 or even 3 > orders of magnitude larger? Or even unlimited? Just wondering. I was wondering about that, too, but couldn't find any definite statements on the maximum length of the DESCRIPTION field. I only skimmed RFC 2445, though. Even if there is such a definite limit, I wouldn't count on servers to correctly implement that. I guess you just have to try what works. > Anyway, with respect to my problems, would you please have a look to > see if you are assuming ASCII or similar and whether there is anything > you can do about this? I (and many others, I assume) really do need > to be able to work in UTF-8 at the very least. I will look into that. I'm pretty sure this is fixable. -David
Re: [O] org-caldav: New version with proper two-way sync
Detlef Steuer writes: > So it seems all events get deleted immediately after loading them up. > Indeed my calendars show up empty again in owncloud :-) > > Any hints? Could you post the contents of the *org-caldav-debug* buffer when this happens? -David
Re: [O] latex-export of first-column-starting emphasis broken
Marijn wrote:
> While visiting a file with just these two lines:
>
> * S
> /s ()/
>
> export to latex: C-c C-e p.
>
> Resulting tex file fails to compile due to the presence of:
>
> \emph{s ()\}
>
> instead of
>
> \emph{s ()}
>
> If you add a space to the beginning of the second line, then it works
> as expected. I am using this work-around for now. I'm using emacs-24.2
>
Works correctly for me with either the old or the new exporter:
Org-mode version 7.9.3d (release_7.9.3d-826-gbe0d87.dirty)
Nick
[O] latex-export of first-column-starting emphasis broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While visiting a file with just these two lines:
* S
/s ()/
export to latex: C-c C-e p.
Resulting tex file fails to compile due to the presence of:
\emph{s ()\}
instead of
\emph{s ()}
If you add a space to the beginning of the second line, then it works
as expected. I am using this work-around for now. I'm using emacs-24.2
Marijn
PS Please CC me in responses, as I'm not subsscribed.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlD2zTsACgkQp/VmCx0OL2yGBQCfWJ1XxQOzZvLRNkepyC8GbI2G
SOAAoKKgVv2fgouo/7ZjChSPztiIkHaC
=i1dg
-END PGP SIGNATURE-
Re: [O] latex-export of first-column-starting emphasis broken
Aloha Marijn,
Marijn writes:
> While visiting a file with just these two lines:
>
> * S
> /s ()/
>
> export to latex: C-c C-e p.
>
> Resulting tex file fails to compile due to the presence of:
>
> \emph{s ()\}
>
> instead of
>
> \emph{s ()}
>
> If you add a space to the beginning of the second line, then it works
> as expected. I am using this work-around for now. I'm using emacs-24.2
>
> Marijn
>
> PS Please CC me in responses, as I'm not subsscribed.
I'm not able to reproduce the problem with Org-mode version 7.9.3b
(release_7.9.3b-811-g0c9579 @ /Users/dk/.emacs.d/src/org-mode/lisp/). I
don't think I have anything in my setup that accounts for the different
result.
Here is the exported file:
% Created 2013-01-16 Wed 09:22
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\providecommand{\alert}[1]{\textbf{#1}}
\title{marijn}
\author{Thomas Dye}
\date{\today}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs Org-mode version 7.9.3b}}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\section{S}
\label{sec-1}
\emph{s ()}
\end{document}
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
[O] bug#10125: RFE: require and load-path-shadowing
On 1/16/13 3:06 AM, Andreas Schwab wrote: Kevin Rodgers writes: (defun run-emacs (command) "Run the Emacs COMMAND in the background via `shell-command'." (interactive (let ((program (expand-file-name invocation-name invocation-directory))) (list (read-string "Emacs command: " (cons (concat program (if (cdr command-line-args) (mapconcat 'identity (cdr command-line-args) You need to use shell-quote-argument to properly shell-quote each argument. Thanks, Andreas! -- Kevin Rodgers Denver, Colorado, USA
[O] Exporting headlines as blog-posts for Jekyll
Hi, I'm trying to organize my "lab" notebook with org-mode. Its working great for personal use, but since my research is collaborative I need to be able to share my progress with others. I want to be able to take a project file that has headlines in the form: > * <2013-01-14 Mon> Dated Entry 1 :export: and export their contents as html to: /path/to/jekyll/site/_posts/2013-01-14-Dated-Entry-1.html Then Jekyll will handle the rest for parsing and building up the final product. My inspiration is coming from: http://orgmode.org/worg/org-tutorials/org-jekyll.html#sec-11 I've tried this code on my file and for some reason the timestamp always comes out as nil, but when I manually run the code, the timestamp is properly formatted. My specific implementation is here: https://gist.github.com/4547520 I've checked all the usual places before posting, and I can't seem to figure out what's going wrong, any insights would be most appreciated. Cheers, Dave
Re: [O] Bug (?) in new exporter (export subtree)
Hello, Rick Frankel writes: > In the new exporter, when the option to export only the subtree is > specified, the first heading in the subtree is used as the title of > the document. This seems wrong, as it becomes the title, the first > element in the table of contents and the first (not necessarily > the top level) section in the document. It doesn't, AFAIU. Could you explain how you do export (in particular, where is the point when you call the export subtree process) and what do you expect on a simple example ? For me: #+begin_src org #+TITLE: title #+OPTIONS: toc:t * Level 1 Body 1 X ** Level 2 Body 2 *** Level 3 Body 3 #+end_src with point at X will have "Level 1" as its title, but "Level 1" will appear neither in the table of contents nor as the first section of the produced document. Regards, -- Nicolas Goaziou
Re: [O] =C-c '= isn't working to visit setupfile; bug?
Hello, John Hendy writes: > I can no longer =C-c '= to visit the file listed in #+setupfile: It should be fixed now. Thank you for the report. Regards, -- Nicolas Goaziou
Re: [O] Error building org-e-publish
Hello, Achim Gratz writes: > Michael Gauland writes: >> Thanks, Nick. If I change 'ignore to ignore (without the tick), it builds >> for me >> on both systems. > > It may build, but it is completely wrong. The error is triggered during > expanding the macro and it seems that the special reader form #' does in > fact expect a lambda list in Emacs 23 (as indicated by the error > message) while it also recognizes a function symbol in Emacs 24. Using > a normal quote should be possible here, but I'll leave it to Nicolas to > commit any changes. I have applied the change. Thank you. Regards, -- Nicolas Goaziou
[O] bug#10125: RFE: require and load-path-shadowing
On 1/15/13 12:34 PM, Achim Gratz wrote: Achim Gratz writes: + (concat invocation-directory invocation-name) Better make that + (expand-file-name invocation-name invocation-directory) FWIW here's what I use: (defun run-emacs (command) "Run the Emacs COMMAND in the background via `shell-command'." (interactive (let ((program (expand-file-name invocation-name invocation-directory))) (list (read-string "Emacs command: " (cons (concat program (if (cdr command-line-args) (mapconcat 'identity (cdr command-line-args) " ") " -Q") " &") (1+ (length program))) (shell-command command)) -- Kevin Rodgers Denver, Colorado, USA
Re: [O] commenting out a SCHEDULED line does not remove todo from agenda.
Rainer Stengele wrote: > Hi! > > Imagine you have a todo like this: > > * TODO a task > SCHEDULED: <2013-01-16 Mi +2m> > > Now suppose you want to put that todo on hold. In order to no more see > the scheduled date in the agenda I comment out the "SCHEDULED" line. > I do not want to delete it because I maybe need it later again: > > > * TODO a task > # SCHEDULED: <2013-01-16 Mi +2m> > > The todo still appears in the agenda. > Is this not counterintuitive? > Try putting the # in column 1 (untested). Nick
Re: [O] commenting out a SCHEDULED line does not remove todo from agenda.
Rainer Stengele writes: > Am 16.01.2013 17:49, schrieb Markus Heller: >> Rainer Stengele writes: >> >>> Hi! >>> >>> Imagine you have a todo like this: >>> >>> * TODO a task >>> SCHEDULED: <2013-01-16 Mi +2m> >>> >>> Now suppose you want to put that todo on hold. In order to no more see >>> the scheduled date in the agenda I comment out the "SCHEDULED" line. >>> I do not want to delete it because I maybe need it later again: >>> >>> >>> * TODO a task >>> # SCHEDULED: <2013-01-16 Mi +2m> >>> >>> The todo still appears in the agenda. >>> Is this not counterintuitive? >> >> No, not IMHO. You commented out the date on which you were scheduled to >> start working on the task, but the task remains TODO. >> >> What about changing the TODO state from TODO to WAITING? >> >> Markus >> >> >> > Markus, > > I create the agenda for today. > Why do I see the todo although it is no more scheduled for today? Ah, now I get it. But this works for me, i.e. if I comment the SCHEDULED property out, the task doesn't show up in the agenda. M-x org-version: Org-mode version 7.9.2 (7.9.2-84-g89b8a8-elpa @ c:/Users/mheller/AppData/Roaming/.emacs.d/elpa/org-20121126/) M-x emacs-version: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) of 2012-06-10 on MARVIN Markus
[O] bug#10125: RFE: require and load-path-shadowing
Kevin Rodgers writes: > (defun run-emacs (command) > "Run the Emacs COMMAND in the background via `shell-command'." > (interactive >(let ((program (expand-file-name invocation-name invocation-directory))) > (list (read-string "Emacs command: " > (cons (concat program > (if (cdr command-line-args) > (mapconcat 'identity >(cdr command-line-args) You need to use shell-quote-argument to properly shell-quote each argument. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Re: [O] Opening (for the first time) a 10-line Org doc takes 4 seconds
Bernt Hansen writes:
> For the record here is the output on my Emacs:
>
> GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.1) of 2013-01-08
> on murphy, modified by Debian
>
> Current git head: release_7.9.3d-826-gbe0d87d
I can't check Emacs 23.2 right now, but Emacs 23.4 comes with Org
version 6.33x installed. Just looking at what loaddefs.el has defined
as autoloads from org.el:
;;;### (autoloads (org-customize org-reload org-require-autoloaded-modules
;; org-submit-bug-report org-cycle-agenda-files org-iswitchb
;; org-map-entries org-open-link-from-string org-open-at-point-global
;; org-insert-link-global org-store-link org-run-like-in-org-mode
;; turn-on-orgstruct++ turn-on-orgstruct orgstruct-mode org-global-cycle
;; org-mode) "org" "org/org.el" (20712 11830))
;;; Generated autoloads from org/org.el
Now compare that with the same section generated for a recent Git version:
;;;### (autoloads (org-customize org-reload org-submit-bug-report
;; org-cycle-agenda-files org-switchb org-open-link-from-string
;; org-open-at-point-global org-insert-link-global org-store-link
;; org-run-like-in-org-mode turn-on-orgstruct++ turn-on-orgstruct
;; orgstruct-mode org-global-cycle org-cycle org-mode
org-clock-persistence-insinuate
;; turn-on-orgtbl org-version org-babel-do-load-languages) "org"
;; "org.el" (20726 54443))
;;; Generated autoloads from org.el
So yes, "org-mode" is autoloaded, but some other stuff that should be
isn't. Things get more interesting with the autoloads that are defined
in the earlier version, but not anymore in the newer. In the case of
org-iswitchb the autoload still works since it is defaliased to
org-switchb in the same file. If it were removed, you'd get an error
when trying to use it, the same if it was moved to another file (since
the autoload definition says to look in "org" it will not look in
"org-whatever-i-have-been-moved-to". Also if the file in question has
been renamed ("org-exp-blocks" exists in 6.33x, but not in a current
version), then those autoloads will also not work.
Having Emacs pull in the current autoload definitions will ensure that
all current autoloads are pointing to the correct file, so if you are
using only those everything is fine. It still leaves some definitions
for functions that may not exist anymore, but you would not be able to
use them anyway, so while not squeaky-clean, it will work in practise.
There is one problem that all this still doesn't solve: if a previously
autoloaded function has no current autoload definition and the file it
used to reside in has been renamed, then Emacs will happily descend into
the load-path to load the function along with that old file. This is
why Emacs itself should provide a way to de-activate a built-in package
when a newer version has been installed so that these stale autoload
definitions aren't present after initialization (it is probably possible
to traverse load-history to remove superseded autoload definitions, but
there is no ready-made function to do this AFAIK).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] commenting out a SCHEDULED line does not remove todo from agenda.
Am 16.01.2013 17:49, schrieb Markus Heller: > Rainer Stengele writes: > >> Hi! >> >> Imagine you have a todo like this: >> >> * TODO a task >> SCHEDULED: <2013-01-16 Mi +2m> >> >> Now suppose you want to put that todo on hold. In order to no more see >> the scheduled date in the agenda I comment out the "SCHEDULED" line. >> I do not want to delete it because I maybe need it later again: >> >> >> * TODO a task >> # SCHEDULED: <2013-01-16 Mi +2m> >> >> The todo still appears in the agenda. >> Is this not counterintuitive? > > No, not IMHO. You commented out the date on which you were scheduled to > start working on the task, but the task remains TODO. > > What about changing the TODO state from TODO to WAITING? > > Markus > > > Markus, I create the agenda for today. Why do I see the todo although it is no more scheduled for today? Rainer
Re: [O] commenting out a SCHEDULED line does not remove todo from agenda.
Rainer Stengele writes: > Hi! > > Imagine you have a todo like this: > > * TODO a task > SCHEDULED: <2013-01-16 Mi +2m> > > Now suppose you want to put that todo on hold. In order to no more see > the scheduled date in the agenda I comment out the "SCHEDULED" line. > I do not want to delete it because I maybe need it later again: > > > * TODO a task > # SCHEDULED: <2013-01-16 Mi +2m> > > The todo still appears in the agenda. > Is this not counterintuitive? No, not IMHO. You commented out the date on which you were scheduled to start working on the task, but the task remains TODO. What about changing the TODO state from TODO to WAITING? Markus
[O] About range references in the spreadsheet
In (info "(org) References"), there is an example explaining the range references: @-1$-2..@-1 3 numbers from the column to the left, 2 up to current row What does `2 up to current row' mean? I don't understand. IIRC `@' represents row, it should be `1 up to current row'. -- Best regards.
[O] commenting out a SCHEDULED line does not remove todo from agenda.
Hi! Imagine you have a todo like this: * TODO a task SCHEDULED: <2013-01-16 Mi +2m> Now suppose you want to put that todo on hold. In order to no more see the scheduled date in the agenda I comment out the "SCHEDULED" line. I do not want to delete it because I maybe need it later again: * TODO a task # SCHEDULED: <2013-01-16 Mi +2m> The todo still appears in the agenda. Is this not counterintuitive? Rainer
Re: [O] org-caldav: New version with proper two-way sync
Thank you a lot!
I ran into the issue that repeated syncs have putting and deleting
wrong (it seems).
I use a script in crontab to sync different calendars:
-
#!/bin/bash
### Es werden die Inhalte der Org-Mode Dateien in verschiedene Calender
### in der owncloud exportiert.
for calendar in Ferien Geburtstage Todo WAB; do \
emacs --batch \
--load ${HOME}/Working-Copies/Scripts/Org-Multicalendar/${calendar}.el ;
\
done
##
-
${calendar}.el looking like
-
(add-to-list 'load-path "/home/steuer/GIT/org-mode/lisp/")
(require 'org)
(setq org-icalendar-include-todo t)
(setq org-icalendar-use-deadline '(todo-due))
(setq org-icalendar-use-scheduled '(event-if-not-todo))
(require 'url)
(require 'auth-source)
(setq auth-sources '((:source "~/.netrc" :host t :protocol t)))
(setq auth-source-debug t)
(add-to-list 'load-path "/home/steuer/GIT/org-caldav/")
(setq org-caldav-url
"http://steuer-geilke.de/owncloud/remote.php/caldav/calendars/detlef";)
(setq org-caldav-calendar-id "ferien")
(setq org-caldav-files '("/home/steuer/.pim/ferien.org") )
(setq org-caldav-inbox "/home/steuer/.pim/caldav-inbox.org")
(require 'org-caldav)
(org-caldav-sync)
-
That worked for me, but now, after a first successful sync I get:
(2. and subsequent syncs!)
-
steuer@vknecht-intel:~> /home/steuer/bin/orgdavexport.sh
Contacting host: ##
Reading [application/xml; charset=utf-8]... 306 bytes of 291 bytes (105%)
auth-source-user-or-password: get login for ##:80 (http)
auth-source-user-or-password: found (login)=(#) for ##:80 (http)
auth-source-user-or-password: get password for #:80 (http)
auth-source-user-or-password: found (password)=SECRET for #:80 (http)
Reading [application/xml; charset=utf-8]... 1k of 1k (101%)
OVERVIEW
OVERVIEW
Saving file /tmp/orgics11019cvx...
Wrote /tmp/orgics11019cvx
Saving file /tmp/orgics11019O5A...
Wrote /tmp/orgics11019O5A
Saving file /tmp/org-caldav-11019TUn...
Wrote /tmp/org-caldav-11019TUn
Reading [application/xml; charset=utf-8]... 1k of 1k (101%)
Reading [application/xml; charset=utf-8]... 1k of 1k (101%)
Putting event 1 of 5
Putting event 2 of 5
Putting event 3 of 5
Putting event 4 of 5
Putting event 5 of 5
Deleting event 1 from 5
Deleting event 2 from 5
Deleting event 3 from 5
Deleting event 4 from 5
Deleting event 5 from 5
Wrote /home/steuer/.emacs.d/org-caldav-fb95cae.el
Symbol's function definition is void: pop-to-buffer-same-window
###
So it seems all events get deleted immediately after loading them up.
Indeed my calendars show up empty again in owncloud :-)
Any hints?
org from today, emacs 23.2, org-caldav from yesterday
Deltlef
On Mon, 14 Jan 2013 22:53:53 +0100
David Engster wrote:
> I just pushed a pretty big update to org-caldav. Get it at
>
> https://github.com/dengste/org-caldav
>
> The short story: org-caldav now does proper two-way syncing. It's pretty
> much a rewrite, actually. If you're already using org-caldav, you will
> have to start from scratch after updating.
>
> Please read the README before using this version. Most notably,
> org-caldav will set org-icalendar-store-UID when doing the iCalendar
> export, so every entry with an activate timestamp will get an ID
> property like this:
>
> :PROPERTIES:
> :ID: 6cdf8805-8d1a-46ac-94fc-d225cac5f098
> :END:
>
> If you don't want this, do not use this package.
>
> Please report bugs here or in the github tracker. And please have
> backups.
>
> -David
>
>
Re: [O] Logging of work no longer working with emcas24
Achim, On Tue, Jan 15, 2013 at 8:10 PM, Achim Gratz wrote: > alias mygtd 'emacs /home/dietmarw/ORGA/GTD/org/mygtd.org' of course ... some things just are too simple to see it. Thanks for this! /Dietmar/
