[O] clock consistency check doesn't work for today item
Hello! I find that "clock consistency check" doesn't work for today item. For example, when I come into the log mode by C-c a l ,it looks like this: >XXX (someday before today) > Emacs: 12:56-16:09 Clocked: (3:13) STARTED The Org Manual > 生活: 16:34-16:49 Clocked: (0:15) 杂务 > 生活: 17:08-17:22 Clocked: (0:14) 杂务 > .. >XXX (today) > 物理: 16:46-16:56 Clocked: (0:10) 静电场 > 生活: 17:07-17:36 Clocked: (0:29) 休息 > 物理: 17:36-17:46 Clocked: (0:10) 静电场 > goal: 19:10-22:41 Clocked: (3:31) 林肯 After "v c" to check the clock consistency,,it looks like this: >XXX (someday before today) > Emacs: 12:56-16:09 Clocked: (3:13) STARTED The Org Manual >Clocking gap: 25 minutes > 生活: 16:34-16:49 Clocked: (0:15) 杂务 >Clocking gap: 19 minutes > 生活: 17:08-17:22 Clocked: (0:14) 杂务 > .. >XXX (today) > 物理: 16:46-16:56 Clocked: (0:10) 静电场 > 生活: 17:07-17:36 Clocked: (0:29) 休息 > 物理: 17:36-17:46 Clocked: (0:10) 静电场 > goal: 19:10-22:41 Clocked: (3:31) 林肯 It seems only to loose its power on today...This really confused me when I want to summarize today's work. Regards, Yuchen
Re: [O] backslashchar in texinfo
Hi Bastien, >> Could you change the line 3091 from ``@item'' to ``@item @@'' by hand? > > I think it should be @item, to mean "no special char in this table > line." Or am I missing something? Oh, I was so wrong. Please keep it as ``@item''. Thanks. >> I don't know why my patch was not generated correctly. > > The patch was okay, I didn't apply it -- but it was not attached in > a way that lets the patchwork catch it. That's Ok! I understood. Best, Takaaki -- Takaaki ISHIKAWA
Re: [O] Bug: org-time-stamp sometimes moves my cursor to another monitor ( [7.8.11]
In emacs -Q (setq mouse-autoselect-window t) M-x org-mode C-c . The cursor will move. Sometimes it will move the cursor on top of another frame, which will become active on my computer, since my window manager is also cursor-sensitive. On Sun, Jan 6, 2013 at 7:58 AM, Bastien wrote: > Hi, > > E Sabof writes: > > > The culprit has proved to be the last line of this function, which I > > commented out in my config: > > Please provide a way to reproduce the bug. > > Thanks, > > -- > Bastien >
Re: [O] org-mobile-push vs. symlinks
On Jan 4, 2013 11:34 PM, "Bastien" wrote: > > Hi James, > > James Harkins writes: > > > The outcome is the same as the first: document the issue. > > Org is yours :) I worked in software support for awhile, so... I know what it means, e.g., when some behavior is labeled a "known issue" ;-) I'm not sure of the procedure to contribute to the org manual, but I might suggest something like this, under MobileOrg section B2: ~~ This operation copies all files currently listed in org-mobile-files to the directory org-mobile-directory. By default this list contains all agenda files (as listed in org-agenda-files), but additional files can be included by customizing org-mobile-files. File names will be staged with paths relative to org-directory, so all files should be inside this directory.* ... (rest of paragraph) * It is recommended to store the source org files physically under org-directory. If this is not practical, org-directory may contain symlinks to the org files, provided that the symlink has the same name as the original file. If the original file is called "mylife.org," then the symlink should also be called mylife.org. If the names are different, pulling edited nodes from MobileOrg will fail. ~~ hjh
Re: [O] [new exporter] adhere org-export-date-timestamp-format?
Hello,
Bastien writes:
> Rasmus writes:
>
>> Would it be desirable if the new exporter took the variable
>> org-export-date-timestamp-format into consideration when formatting
>> dates?
>
> I think so. What do you think, Nicolas?
I'm not convinced by this variable. Back-ends are usually so much
different that a global variable aiming at formatting a date timestamp
in any of them doesn't sound very useful.
Though it may be the job of back-ends to provide such a variable
variable, whenever it makes sense.
Another option would be to allow to specify an arbitrary timestamp as
a second, optional, argument to {{{time(...)}}} macro. One could then
use:
#+DATE: {{{time(%Y-%m-%d,<2013-01-06 Sun>)}}}
Regards,
--
Nicolas Goaziou
Re: [O] Bug: org-time-stamp sometimes moves my cursor to another monitor ( [7.8.11]
Apparently what doesn't work is (select-frame-set-input-focus), which might have something to do with calendar appearing in a separate frame depending on the value of calendar-setup. Meaning it's probably either an emacs bug, an xmonad bug or a xinerama bug. On Sun, Jan 6, 2013 at 8:46 AM, E Sabof wrote: > In emacs -Q > (setq mouse-autoselect-window t) > M-x org-mode > C-c . > The cursor will move. > > Sometimes it will move the cursor on top of another frame, which will > become active on my computer, since my window manager is also > cursor-sensitive. > > > > On Sun, Jan 6, 2013 at 7:58 AM, Bastien wrote: > >> Hi, >> >> E Sabof writes: >> >> > The culprit has proved to be the last line of this function, which I >> > commented out in my config: >> >> Please provide a way to reproduce the bug. >> >> Thanks, >> >> -- >> Bastien >> > >
Re: [O] Ignoring empty subtrees/new exporter
Hello, Florian Beck writes: > I have a document with many sections not yet written (i.e. heading > without content) and I would like them to be ignored in the exported > file. I know, I could manually tag these headings with :noexport:, but > what about a more automated approach? > > Now, I tried this: > > > (defun ignore-empty-section (headline contents info) > (when contents > (org-e-latex-headline headline contents info))) > > > (add-to-list 'org-e-latex-translate-alist > '(headline . ignore-empty-section)) The global idea is correct, but I find that the implementation is too low level. It also taints original e-latex back-end. I suggest the following instead: #+begin_src emacs-lisp (defun ignore-empty-section (headline contents info) (when (org-string-nw-p contents) (org-export-with-backend 'e-latex headline contents info))) (org-export-define-derived-backend my-draft-latex e-latex :translate-alist ((headline . ignore-empty-section)) ;; Optionally add a sub-menu entry in the latex menu. :menu-entry (?l 99 ((?d "As a draft PDF file" my-draft-latex (defun my-draft-latex (&optional async subtreep visible-only body-only ext-plist) (interactive) (let ((outfile (org-export-output-file-name ".tex" subtreep))) (if async (org-export-async-start (lambda (f) (org-export-add-to-stack f 'e-latex)) `(expand-file-name (org-e-latex-compile (org-export-to-file 'my-draft-latex ,outfile ,subtreep ,visible-only ,body-only ',ext-plist (org-e-latex-compile (org-export-to-file 'my-draft-latex outfile subtreep visible-only body-only ext-plist) #+end_src Note that if you don't want the hassle of creating a derived back-end, you can also implement a function that will remove every section containing only sections or nothing from the buffer, and add it to `org-export-before-processing-hook' (or `org-export-before-parsing-hook'). Regards, -- Nicolas Goaziou
Re: [O] Logical not in org-entities.el
On 01/06/2013 07:14 AM, Bastien wrote: Hi Florian, Florian Beck writes: The confusion arises with org-pretty-entities because what you see is definitely not what you get. Mhh... not sure what you mean: what do you see that you don't get? With org-pretty-entities: On display, org-entities handles all entities and displays them as unicode characters, even inside math blocks. On export, org-entities only handles entities outside math. Most of the time it doesn't matter because the entity name is the same as the latex command. But in case of "$\not a$" latex export and fontification differ: the fontified buffer shows the angled dash (¬), the exported document shows a slash through the next charaxter.
[O] Using Pandoc for export to EPub and Mediawiki Re: Bug: Status of the org-mediawiki.el [7.8.11]
Hi all! Am 24.10.12 15:43, schrieb Bastien: > Hi Bernhard, > > Bernhard Gschaider writes: > >> May question: Is the support for Mediawiki-export abandoned? > > For now, yes. > > But I think it would be a nice format to export to. Just one question: does this HAVE to be implemented in org-mode/elisp itself? I just stumbled on Pandoc http://johnmacfarlane.net/pandoc/README.html which can export from several markup-languages to for instance MediaWiki (what I think is weird is that it accepts org-mode as an output, but not as an input). So one "only" has to write an org-reader and get the project to accept it and then there would be a number of output-formats (including ePub which would be VERY cool) available for "free" (some duplicate existing formats). I know that the "only" part is the hard thing. But there seems to be somebody working on this already https://github.com/jgm/pandoc/issues/476 If nobody is actively working on these export filters (Mediawiki) then maybe "outsourcing" this conversion to pandoc and "only" integrating the call into the "export menu" would be an interesting way to go Bernhard > >> If yes: I'd suggest to remove the reference to it from >> http://orgmode.org/worg/org-contrib/ > > Done, thanks! >
Re: [O] Bug: org-time-stamp sometimes moves my cursor to another monitor ( [7.8.11]
Hi, E Sabof writes: > In emacs -Q > (setq mouse-autoselect-window t) > M-x org-mode > C-c . > The cursor will move. Fixed, thanks for the detailed explanations. -- Bastien
Re: [O] Logical not in org-entities.el
Hi Florian,
Florian Beck writes:
> With org-pretty-entities:
> On display, org-entities handles all entities and displays them as unicode
> characters, even inside math blocks.
> On export, org-entities only handles entities outside math. Most of the
> time it doesn't matter because the entity name is the same as the latex
> command. But in case of "$\not a$" latex export and fontification differ:
> the fontified buffer shows the angled dash (¬), the exported document shows
> a slash through the next charaxter.
In master, I added
("neg" "\\neg{}" nil "¬" "[angled dash]" "¬" "¬")
in (defconst org-entities ...)
so that you can now use it to produce \\neg{} where relevant.
Thanks,
--
Bastien
Re: [O] [new exporter] adhere org-export-date-timestamp-format?
Hi Nicolas,
thanks for looking into this.
Nicolas Goaziou writes:
> I'm not convinced by this variable. Back-ends are usually so much
> different that a global variable aiming at formatting a date timestamp
> in any of them doesn't sound very useful.
>
> Though it may be the job of back-ends to provide such a variable
> variable, whenever it makes sense.
Yes, I think it's the job of backends.
> Another option would be to allow to specify an arbitrary timestamp as
> a second, optional, argument to {{{time(...)}}} macro. One could then
> use:
>
> #+DATE: {{{time(%Y-%m-%d,<2013-01-06 Sun>)}}}
I'm all for allowing macros in "document info" keywords
(i.e. "#+title:" "#+author:" "#+email:" "#+date) though
I'm not sure if it makes sense for other keywords than
for "#+date", and maybe allowing macro here just for
this use-case is to liberal.
Best,
--
Bastien
Re: [O] Using Pandoc for export to EPub and Mediawiki Re: Bug: Status of the org-mediawiki.el [7.8.11]
Hi Bernhard, "Bernhard F.W. Gschaider" writes: > If nobody is actively working on these export filters (Mediawiki) then > maybe "outsourcing" this conversion to pandoc and "only" integrating the > call into the "export menu" would be an interesting way to go Yes. If you can motivate someone either from this list or from Pandoc community to write an Org mode reader, that'd be nice. Even when we finally have a mediawiki exporter. Best, -- Bastien
Re: [O] org-mobile-push vs. symlinks
Hi James, James Harkins writes: > I'm not sure of the procedure to contribute to the org manual, but I > might suggest something like this, under MobileOrg section B2: I added a footnote: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=76684b5 Thanks! -- Bastien
Re: [O] clock consistency check doesn't work for today item
Hi Bastien, Bastien altern.org> wrote: >Can you send a minimal .org file that we can use to reproduce the bug? Thanks for your attention to this matter. I'm sorry I post this mail twice by mistake.here is the test org file： >* Task1 > CLOCK:[2013-01-03 周四 23:24]--[2013-01-03 周四 23:42] => 0:18 >* Task2 > CLOCK: [2013-01-06 周日 12:31]--[2013-01-06 周日 12:39] => 0:08 > CLOCK: [2013-01-06 周日 10:02]--[2013-01-06 周日 10:18] => 0:16 In fact, I find that this problem is caused by the absence of blank between "CLOCK:" and the timestamp.I forget to type it :P I don't know whether this is a bug... And thanks for telling me the basic etiquette while posting a question,here is the version info: Emacs: GNU Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-29 on MARVIN Package: Org-mode version 7.8.11 Sincerely, Yuchen
[O] emacs initialization files in org mode
Hello, After having read about the emacs-starter-kit on the list, I really like the idea of having my initialization files in org-mode. As I have many customizations already made, I don't want to dump everything to use esk. What I want is doing the same with my own keybindings and customizations. So I went and had a look at the code, and it seems it's fairly trivial to do. If I have missed something, please don't hesitate to let me know. The bare minimum one can do is: - rename the current init.el into myinit.org - add the lines "#+begin_src emacs-lisp" as the first line, and "+end_src" as the last line - adapt the init.el from emacs-starter-kit as follows #+BEGIN_SRC emacs-lisp (add-hook 'after-init-hook `(lambda () ;; remember this directory (setq emacsd-dir ,(file-name-directory (or load-file-name (buffer-file-name ;; load up the starter kit (require 'org) (org-babel-load-file (expand-file-name "myinit.org" emacsd-dir #+END_SRC Then one can start editing the myinit.org so that it is not just a big chunk of code. Alan
Re: [O] Compatibility tests
Bastien writes:
> As for XEmacs and Emacs 22, I'm fine with anything that
> helps supporting these emacsen, unless it adds too much
> extra complexity.
First three patchs apply against maint:
>From 4e2f6d7d8f870f834079ce010eb2049d61bb5576 Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Sun, 6 Jan 2013 18:28:06 +0100
Subject: [PATCH 1/3] Compatibility: Use org-no-warnings
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
* contrib/lisp/org-e-odt.el (org-e-odt-htmlfontify-string): Use
compatibility alias `org-no-warnings´.
---
contrib/lisp/org-e-odt.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/lisp/org-e-odt.el b/contrib/lisp/org-e-odt.el
index 346b029..5953cc6 100644
--- a/contrib/lisp/org-e-odt.el
+++ b/contrib/lisp/org-e-odt.el
@@ -2886,7 +2886,7 @@ (defun org-e-odt-htmlfontify-string (line)
(lambda (style text-block text-id text-begins-block-p)
(insert (format "" style
(hfy-end-span-handler (lambda nil (insert ""
-(with-no-warnings (htmlfontify-string line
+(org-no-warnings (htmlfontify-string line
(defun org-e-odt-do-format-code
(code &optional lang refs retain-labels num-start)
--
1.8.1
>From d524e7d6112cda2b53e3e0822609fa81b2dd6ee9 Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Sun, 6 Jan 2013 17:48:39 +0100
Subject: [PATCH 2/3] Compatibility: Define face alias mode-line for XEmacs
* lisp/org-faces.el: Define face alias mode-line for XEmacs (it's
called modeline there).
---
lisp/org-faces.el | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lisp/org-faces.el b/lisp/org-faces.el
index 80e8134..606db08 100644
--- a/lisp/org-faces.el
+++ b/lisp/org-faces.el
@@ -44,6 +44,9 @@ (defun org-copy-face (old-face new-face docstring &rest attributes)
(set-face-doc-string new-face docstring)
(put 'org-copy-face 'lisp-indent-function 2)
+(when (featurep 'xemacs)
+ (put 'mode-line 'face-alias 'modeline))
+
(defgroup org-faces nil
"Faces in Org-mode."
:tag "Org Faces"
--
1.8.1
>From 305f29776fba57cdd1566071e0e8a75270d095c6 Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Sun, 6 Jan 2013 18:29:05 +0100
Subject: [PATCH 3/3] Compatibility: Use
org-define-obsolete-{function,variable}-alias
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
* lisp/org-compat.el (org-define-obsolete-function-alias,
org-define-obsolete-variable-alias): Introduce new compatibility
macros to obsolete functions and variables.
* lisp/org-agenda.el, lisp/org-clock.el, lisp/org-id.el,
lisp/org-lparse.el, lisp/org-protocol.el lisp/org.el: Use
`org-define-obsolete-{function,variable}-alias´instead of
`define-obsolate{function,variable}-alias´.
---
lisp/org-agenda.el | 6 +++---
lisp/org-clock.el| 2 +-
lisp/org-compat.el | 18 ++
lisp/org-id.el | 2 +-
lisp/org-lparse.el | 4 ++--
lisp/org-protocol.el | 6 +++---
lisp/org.el | 13 -
7 files changed, 32 insertions(+), 19 deletions(-)
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index 1b2337c..b4c21fc 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -890,7 +890,7 @@ (defcustom org-agenda-menu-show-matcher t
:version "24.1"
:type 'boolean)
-(define-obsolete-variable-alias 'org-agenda-menu-two-column 'org-agenda-menu-two-columns "24.3")
+(org-define-obsolete-variable-alias 'org-agenda-menu-two-column 'org-agenda-menu-two-columns "24.3")
(defcustom org-agenda-menu-two-columns nil
"Non-nil means, use two columns to show custom commands in the dispatcher.
@@ -900,7 +900,7 @@ (defcustom org-agenda-menu-two-columns nil
:version "24.1"
:type 'boolean)
-(define-obsolete-variable-alias 'org-finalize-agenda-hook 'org-agenda-finalize-hook "24.3")
+(org-define-obsolete-variable-alias 'org-finalize-agenda-hook 'org-agenda-finalize-hook "24.3")
(defcustom org-agenda-finalize-hook nil
"Hook run just before displaying an agenda buffer.
The buffer is still writable when the hook is called.
@@ -7681,7 +7681,7 @@ (defun org-agenda-set-mode-name ()
"")))
(force-mode-line-update))
-(define-obsolete-function-alias
+(org-define-obsolete-function-alias
'org-agenda-post-command-hook 'org-agenda-update-agenda-type "24.3")
(defun org-agenda-update-agenda-type ()
diff --git a/lisp/org-clock.el b/lisp/org-clock.el
index a481ac5..e3048e5 100644
--- a/lisp/org-clock.el
+++ b/lisp/org-clock.el
@@ -204,7 +204,7 @@ (defcustom org-clock-sound nil
(const :tag "Standard beep" t)
(file :tag "Play sound file")))
-(define-obsolete-variable-alias 'org-clock-modeline-total
+(org-define-obsolete-variable-alias 'org-clock-modeline-total
'org-clock-mode-line-total "24.3")
(defcustom org-clock-mode-line-total 'auto
diff --git a/lisp/org-compat.el b/lisp/org-compat.el
index 8f21321..8150875 100644
--- a/lisp/org-compat.el
+++ b/lisp/org-compat.el
@@ -169,6 +169,24 @@ (defsubst org-decompose-region (beg en
Re: [O] backslashchar in texinfo
On Sun 06 Jan 2013, Bastien wrote:
> Hi Takaaki,
>
> Takaaki ISHIKAWA writes:
>
>> I found two build errors in the latest org manual(HEAD of git).
>>
>> 1. Using ``@backslashcar{}'' command in texinfo(L5114).
>> 2. Missing ``@''(L3091).
>
> Thanks for reporting this!
>
>> The texinfo command was introduced at the version 4.14,
>> see http://permalink.gmane.org/gmane.comp.gnu.lilypond.devel/51827.
>>
>> I think the command should not be used because many users
>> currently use the previous version 4.13.
>>
>> Any comments?
>
> I backported a diff from the Emacs trunk erroneously.
> It is fixed now.
This still appears to be broken in emacs trunk - could you please update
the org manual there to fix this too ?
Thanks,
AndyM
Re: [O] backslashchar in texinfo
Hi Andy, Andy Moreton writes: > This still appears to be broken in emacs trunk - could you please update > the org manual there to fix this too ? This has been fixed in the emacs-24 branch and will be merged into trunk soon. http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-24&id=7c68ba Best, -- Bastien
Re: [O] Babel related bug in elpa version 20121231
On Sunday, January 6, 2013, Eric Schulte wrote: > Tom Davey > writes: > > > Hi folks, > > > > This is a very interesting discussion. I too have run into this issue, > > and addressed it in a different way. > > > > My init.el contains only a defun and an add-hook. The defun is simple. > > It adds a few miscellaneous directories to load-path and then makes > > the call to Eric's starter kit via org-babel-load-file(). > > > > The trick is this: I add the defun to the hook "after-init-hook". This > > ensures that my personal initialization, including the Starter Kit > > .org files, doesn't begin to execute until all the ELPA packages are > > initialized. That way my own initialization can depend on a fully > > stabilized Emacs. > > > > (add-hook 'after-init-hook 'my-after-init-hook-functions) > > > > I found this useful because my personal initialization makes little > > tweaks to my ELPA packages. It seems to give me the control over the > > order of initialization that I need. > > > > Regards to all, > > Tom Davey > > > > -- > > Tom Davey > > t...@tomdavey.com > > New York NY USA > > > > Thanks for sharing, this does seem like the best way to ensure that all > of the packages are loaded. > > I've just updated the starter kit to both require org and to use the > `after-init-hook'. > > Hopefully this should fix as many problems as possible now, please let > me know if any issues persist. > Thanks Eric, will give it a shot.
Re: [O] Compatibility tests
Hi Achim, Achim Gratz writes: > First three patchs apply against maint: > Then merge into master and apply these two on top: Please feel free to apply those patch, thanks a lot. PS: Is there any way to convert inline patches into attached patches easily from Gnus? -- Bastien
Re: [O] clock consistency check doesn't work for today item
Hi Yuchen, yuchen writes: > In fact, I find that this problem is caused by the absence of blank between > "CLOCK:" and the timestamp.I forget to type it :P > I don't know whether this is a bug... If you clock in and ou using org-clock-in and org-clock-out (or equivalent commands from the agenda), then you should not have to worry abou whitespaces -- this must have been manually deleted/typed by error. So I'd say no, this is not a bug. Thanks! -- Bastien
Re: [O] Compatibility tests
Bastien writes: > Please feel free to apply those patch, thanks a lot. Done. > PS: Is there any way to convert inline patches into attached > patches easily from Gnus? I don't know, but they were inline by accident anyway. Sorry for that. I've almost convinced XEmacs to run the tests, but loading the elisp tests triggers an infinite recursion to max-eval-depth or a segmentation fault when I increase the depth limit too far. If I find a way to work around this… Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
[O] how to add a alias to babel mode
Hi, I want to be able to have this kind of code block (the reason is for ease of postprocessing with org-ruby with coderay_bash) #+begin_src bash #+end_src but I can't find a pointer on how to alias the "sh" babel mode to the string "bash". Can someone shows me the way ? Thanks, -- Sofer.
Re: [O] Ignoring empty subtrees/new exporter
On 01/06/2013 11:24 AM, Nicolas Goaziou wrote: The global idea is correct, but I find that the implementation is too low level. It also taints original e-latex back-end. I suggest the following instead: Thanks a lot! A derived backend seems like a good idea. Unfortunatly, the function org-export-with-backend isn't in the latest org-plus-contrib package (20121231). I'll try it then.
Re: [O] Logical not in org-entities.el
On 01/06/2013 12:39 PM, Bastien wrote:
In master, I added
("neg" "\\neg{}" nil "¬" "[angled dash]" "¬" "¬")
in (defconst org-entities ...)
so that you can now use it to produce \\neg{} where relevant.
Thanks, but: \neg has to be put in math mode.
Re: [O] Logical not in org-entities.el
Hi Florian, Florian Beck writes: > Thanks, but: \neg has to be put in math mode. Isn't it the case for other entities as well? -- Bastien
Re: [O] Compatibility tests
Achim Gratz writes: > Bastien writes: >> Please feel free to apply those patch, thanks a lot. > > Done. Thanks! >> PS: Is there any way to convert inline patches into attached >> patches easily from Gnus? > > I don't know, but they were inline by accident anyway. Sorry for that. > > I've almost convinced XEmacs to run the tests, but loading the elisp > tests triggers an infinite recursion to max-eval-depth or a segmentation > fault when I increase the depth limit too far. If I find a way to work > around this… All right, let us know. -- Bastien
Re: [O] org-mobile-push vs. symlinks
On Jan 6, 2013 9:57 PM, "Bastien" wrote:
>
> Hi James,
>
> James Harkins writes:
>
> > I'm not sure of the procedure to contribute to the org manual, but I
> > might suggest something like this, under MobileOrg section B2:
>
> I added a footnote:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=76684b5
(The thread that wouldn't die...)
I just looked at the footnote text... why did we go from "symlinks work if
the name is the same" to an unqualified "symlinks are not supported"?
It isn't always feasible, or even desirable in some cases, to keep all your
org files under org-directory. For instance, I have a separate project
folder for a series of concerts to be given in the spring. If I back up
this folder, I want the project's org file to come with it. The updated
documentation seems to suggest that I should store the org file physically
under org-directory and place a symlink under the project directory, making
backups a bit more complex ("oh my, I forgot again what is the cp or rsync
option to follow links... man page...").
I can accept the same-name requirement, but it really makes much more sense
to me to keep org files physically with their projects. So I'd kindly
request that future org-mobile changes avoid breaking the use of symlinks
in org-directory (which currently does work). Documenting that symlinks are
supported (with the one caveat about the filename) is a step in that
direction.
hjh
Re: [O] org-mobile-push vs. symlinks
James Harkins writes: > I just looked at the footnote text... why did we go from "symlinks > work if the name is the same" to an unqualified "symlinks are not > supported"? I overlooked the difference. Please provide a patch. ~$ git clone git://orgmode.org/org-mode.git ~$ emacs & C-x f org-mode/doc/org.texi ... [edit edit edit] ... C-x s C-x v = C-x s Send the file you saved and you're done! -- Bastien
Re: [O] org bingo
Hi Tony, At Thu, 20 Dec 2012 16:43:37 +1100, Tony Day wrote: > > org-random-entry: select and goto a random todo entry. Prefix allows you > to select which todo keyword. > > https://gist.github.com/4343164 love that idea! However, I accidentally tried org-random-entry after org-agenda-exit and got following: debug(error (error "Selecting deleted buffer")) org-compile-prefix-format(todo) (catch (quote exit) (org-compile-prefix-format (quote todo))... (let* ((today (org-today)) (date (calendar- org-random-entry(nil) call-interactively(org-random-entry record nil) this is because org-compile-prefix-format assumed to have org-agenda-buffer set either 'nil' or 'live buffer', but not '#'. I'm not sure it is good idea to fix the org-compile-prefix-format itself or not. so I came up with the following fix: diff --git a/dotemacs.org b/dotemacs.org index 302ac53..c4042a1 100644 --- a/dotemacs.org +++ b/dotemacs.org @@ -9,6 +9,8 @@ (kwds org-todo-keywords-for-agenda) (lucky-entry nil) (completion-ignore-case t) + (org-agenda-buffer (if (buffer-live-p org-agenda-buffer) + org-agenda-buffer)) (org-select-this-todo-keyword (if (stringp arg) arg (and arg (integerp arg) (> arg 0) What do you think? regards, -- yashi
Re: [O] org bingo
Yasushi SHOJI writes: > + (org-agenda-buffer (if (buffer-live-p org-agenda-buffer) > + org-agenda-buffer)) --^ This should be a "when" form since there's no else clause. 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] help advicing org-todo
This is great! Thanks, Luca > (setq org-clock-in-switch-to-state "STRT") > (setq org-clock-out-switch-to-state "DONE") >
