[O] Bug: org-paste-subtree may delete headline at point [9.1.14 (release_9.1.14-961-g5abfde)]

2018-10-04 Thread Dale Sedivec
Hi, I think I may have found a bug in org-paste-subtree in master branch
where it will delete the content of the headline at point before yanking.
Steps to reproduce:

1. Start a fresh Emacs along the lines of:

mkdir /tmp/fake-home
cd /tmp/fake-home
git clone https://code.orgmode.org/bzg/org-mode.git
(cd org-mode && make autoloads)
HOME=/tmp/fake-home emacs -L /tmp/fake-home/org-mode/lisp

2. Create a new org file with the following contents:

* One
* Two
* Three

3. Move point to the "Two" headline, use C-c C-x C-w to kill it

4. Move point to *the end* of the "One" headline (first line)

5. Try to yank the "Two" headline: C-c C-x C-y (org-paste-special ->
org-paste-subtree)

Expected results (using ~~ as delimiters here):

~~
* One
* Two
* Three
~~

Observed results:

~~

* Two
* Three
~~

Note that all content on the "* One" line where we invoked
org-paste-subtree has been deleted.

I suspect the problem may be in org-paste-subtree.  Here's an excerpt that
calculates the value for force-level:

~~
  (force-level
   (cond
(level (prefix-numeric-value level))
;; When point is right after the stars in an otherwise
;; empty headline, use stars as the forced level.
((and (looking-at-p "[ \t]*$")
  (string-match-p "^\\*+ *"
  (buffer-substring (line-beginning-position)
(point
 (org-outline-level))
((looking-at-p org-outline-regexp-bol) (org-outline-level
~~

The comment says it's trying to identify an "empty headline", but the
combination of the two regexes there seems to simply confirm that point is
at EOL, ignoring white space, and that we're on a headline.  They seem to
do nothing to ensure that there is no content between the headline bullets
and EOL, so force-level becomes non-nil, which causes org-paste-subtree to
delete the contents of the line at point.

Assuming the comment's intent is correct, perhaps the
looking-at-p/string-match-p pair should just be replaced with something
like this?

(string-match-p "^\\*+\\s-*$" (buffer-substring (line-beginning-position)
(point)))

Version info:

Emacs  : GNU Emacs 26.1.50 (build 2, x86_64-apple-darwin17.7.0, NS
appkit-1561.60 Version 10.13.6 (Build 17G65))
 of 2018-08-31
Package: Org mode version 9.1.14 (release_9.1.14-961-g5abfde @
/tmp/orgbug/org-mode/lisp/)

Regards,
Dale


[O] org-save-outline-visibility no longer saves drawer visibility

2018-02-02 Thread Dale Sedivec
Hi!  I think maybe there's a bug in org-save-outline-visibility, or else I
misunderstand what that macro is supposed to do.  Test case:

1. Start Emacs 26.0.91 with -Q and load org-mode from master
(release_9.1.6-419-g4b2006).

2. Make an org-mode buffer with contents:

~~
* Foo
  :PROPERTIES:
  :bar:  baz
  :END:
~~

3. Fold the PROPERTIES drawer by moving to the line with :PROPERTIES: and
hitting TAB.

4. M-: (org-save-outline-visibility t (org-show-all)) RET

Expected result: PROPERTIES drawer is still folded

Observed result: PROPERTIES drawer is no longer folded, its contents have
become visible

Should org-save-outline-visibility save the visibility of drawers along
with other visibility?

I am wondering if this is perhaps a consequence of 4403d4685e19, "Give
drawers their own invisibility spec", where the 'org-hide-drawer
invisibility spec was introduced?  As a consequence,
org-outline-overlay-data (called by org-save-outline-visibility) no longer
saves the invisible overlays for drawers, since those overlays' 'invisible
property is no longer 'outline, but instead 'org-hide-drawer.

Thanks,
Dale


[O] Bug: Blank line when logging state changes [9.0.9 (9.0.9-692-gfbf31d.dirty-elpaplus @ /tmp/emacs/.emacs.d/elpa/org-plus-contrib-20170801/)]

2017-08-01 Thread Dale Sedivec
Hi!

I think a recent change to org-split-string in master may have made logging
of state changes a little uglier, adding "\\" and an empty line with
trailing whitespace.  Steps to reproduce:

1. Start fresh Emacs with no local configuration (e.g. mkdir /tmp/emacs &&
HOME=/tmp/emacs emacs)

2. Install org-plus-contrib package dated 20170731

3. Create an org file with the following two lines:

~~
#+TODO: TODO(!) DONE(!)
* Test
~~

4. Move point to the beginning of the "* Test" headline and call org-todo
with C-c C-t to change it to a TODO item

Expected result:

~~
* TODO Test
  - State "TODO"   from  [2017-08-01 Tue 11:18]
~~

Actual result:

~~
* TODO Test
  - State "TODO"   from  [2017-08-01 Tue 11:18] \\

~~

Note the " \\" and blank line with trailing whitespace in the actual result.

I strongly suspect this is a result of a change in behavior of
org-split-string in f776e65373.  Before that commit, calling

(org-split-string "" "\n")

as org-store-log-note is doing returned nil.  After f776e65373 it returns
'("").

IMHO the new behavior of org-split-string actually seems correct to me
(splitting a string should arguably never result in nil), so I've fixed
this by patching org-store-log-note as demonstrated in the attached patch.

Regards,
Dale
--- org.el.orig 2017-08-01 10:58:56.0 -0500
+++ org.el  2017-08-01 11:26:12.0 -0500
@@ -13640,7 +13640,9 @@
   (setq txt (replace-match "" t t txt)))
 (when (string-match "\\s-+\\'" txt)
   (setq txt (replace-match "" t t txt)))
-(setq lines (org-split-string txt "\n"))
+(setq lines (if (zerop (length txt))
+   nil
+ (org-split-string txt "\n")))
 (when (org-string-nw-p note)
   (setq note
(org-replace-escapes


Re: [O] Bug: clocktable interprets tstart/tend incorrectly, maybe? [9.0.9 (9.0.9-636-gd39ccc-elpaplus @ /tmp/emacs/.emacs.d/elpa/org-plus-contrib-20170709/)]

2017-07-15 Thread Dale Sedivec
On Mon, Jul 10, 2017 at 3:59 AM, Nicolas Goaziou <m...@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Dale Sedivec <d...@codefu.org> writes:
>
[...]

> > I notice that as of 112c5ba479d, org-clocktable-steps parses :tstart and
> > :tend with the ZONE argument to org-parse-time-string as T.  I think this
> > is causing org-parse-time-string to parse these user-entered dates as UTC
> > rather than the user's local time as I would have expected.  Changing
> > org-clocktable-steps from doing (org-parse-time-string ts nil t)
> > to (org-parse-time-string ts nil nil), and then the same for te as well,
> > seems to fix this problem.
>
> Fixed. Thank you for the report and the analysis.
>

Thank you as always Nicolas!  You fixed the time zone for :tstart in
60eda8e4ec4.  However, I think the parsing of :tend (locally bound as te)
eight lines below that needs the same fix.  Diff attached this time, just
to demonstrate what I'm talking about.  (Sorry I don't send more patches,
but I have not updated my copyright assignment to reflect my new employer.)

Steps to reproduce:

* Start Emacs 25.1 in an empty $HOME with TZ=America/Chicago

* Install org-mode HEAD

* Insert the following into an org-mode buffer and update the dblock:

~~
* Test
  :LOGBOOK:
  CLOCK: [2017-07-15 Sat 00:01]--[2017-07-15 Sat 01:01] =>  1:00
  :END:
#+BEGIN: clocktable :maxlevel 2 :scope subtree :tstart "<2017-07-09 Sun>"
:tend "<2017-07-16 Sun>" :step day
#+END:
~~

Expected result: The last step in the clock table for 2017-07-15 shows 1
hour

Actual result: The last step in the clock table for 2017-07-15 shows 0 hours

Thanks again,
Dale
diff --git a/lisp/org-clock.el b/lisp/org-clock.el
index 8e04aec2dd..4164c92aba 100644
--- a/lisp/org-clock.el
+++ b/lisp/org-clock.el
@@ -2710,8 +2710,7 @@ LEVEL is an integer.  Indent by two spaces per level 
above 1."
   (pcase-let ((`(,month ,day ,year) (calendar-gregorian-from-absolute te)))
(setq te (float-time (encode-time 0 0 0 day month year)
  (te
-  (setq te (float-time
-   (apply #'encode-time (org-parse-time-string te nil t))
+  (setq te (float-time (apply #'encode-time (org-parse-time-string te))
 (setq tsb
  (if (eq step0 'week)
  (- ts (* 86400 (- (nth 6 (decode-time (seconds-to-time ts))) ws)))


[O] Bug: clocktable interprets tstart/tend incorrectly, maybe? [9.0.9 (9.0.9-636-gd39ccc-elpaplus @ /tmp/emacs/.emacs.d/elpa/org-plus-contrib-20170709/)]

2017-07-09 Thread Dale Sedivec
-delete-maybe)
 org-ascii-format-drawer-function '(closure (t) (_name contents _width)
   contents)
 org-odt-format-inlinetask-function
'org-odt-format-inlinetask-default-function
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
 org-cycle-show-empty-lines
 org-optimize-window-after-visibility-change)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-odt-format-drawer-function '(closure
 (hfy-user-sheet-assoc hfy-html-quote-regex
  hfy-html-quote-map hfy-face-to-css
  hfy-begin-span-handler hfy-end-span-handler
  archive-zip-extract
  nxml-auto-insert-xml-declaration-flag t)
 (_name contents) contents)
 org-html-format-headline-function
'org-html-format-headline-default-function
 org-link-parameters '(("rmail" :follow org-rmail-open :store
org-rmail-store-link)
  ("mhe" :follow org-mhe-open :store org-mhe-store-link)
  ("irc" :follow org-irc-visit :store org-irc-store-link)
  ("info" :follow org-info-open :export org-info-export
:store org-info-store-link)
  ("gnus" :follow org-gnus-open :store
org-gnus-store-link)
  ("docview" :follow org-docview-open :export
org-docview-export :store org-docview-store-link)
  ("bbdb" :follow org-bbdb-open :export org-bbdb-export
:complete org-bbdb-complete-link :store
org-bbdb-store-link)
  ("w3m" :store org-w3m-store-link)
  ("bibtex" :follow org-bibtex-open :store
org-bibtex-store-link)
  ("id" :follow org-id-open) ("file+sys") ("file+emacs")
  ("doi" :follow org--open-doi-link)
  ("elisp" :follow org--open-elisp-link)
  ("file" :complete org-file-complete-link)
  ("ftp" :follow
(lambda (path) (browse-url (concat "ftp:" path
  ("help" :follow org--open-help-link)
  ("http" :follow
(lambda (path) (browse-url (concat "http:" path
  ("https" :follow
(lambda (path) (browse-url (concat "https:" path
  ("mailto" :follow
(lambda (path) (browse-url (concat "mailto:; path
  ("news" :follow
(lambda (path) (browse-url (concat "news:; path
  ("shell" :follow org--open-shell-link))
 org-html-format-inlinetask-function
'org-html-format-inlinetask-default-function
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 )

Regards,
Dale


Re: [O] Is doc/org-version.tex generation broken?

2017-06-30 Thread Dale
On Fri, Jun 30, 2017 at 12:29 PM, Kyle Meyer <k...@kyleam.com> wrote:

> Kyle Meyer <k...@kyleam.com> writes:
>
[...]

> Can you verify that the below change works on your system?
>
> Thanks.
>
> -- >8 --
> Subject: [PATCH] doc/Makefile: Use printf to generate org-version.tex
>
> * doc/Makefile (org-version.tex): Use printf instead of echo to
> increase portability.
>
[...]

Confirmed, I can now "make card" successfully.  Thanks!

Dale


[O] Is doc/org-version.tex generation broken?

2017-06-30 Thread Dale
Hi!

a8d007db15 starts generating doc/org-version.{tex,inc}, but on my OS X
system this ends up creating broken files with (I believe) vertical tab
characters in them.  On HEAD this morning:

$ make card
[...]
PDFLATEX=pdftex texi2pdf --batch --clean --expand orgcard.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded
format=pdftex)
 restricted \write18 enabled.
entering extended mode

(../../.././orgcard.tex
(/Users/dale/repositories/org-mode/doc/org-version.tex
/Users/dale/repositories/org-mode/doc/org-version.tex:3: Missing control
sequen
ce inserted.

\inaccessible



l.3 \def
 ersionyear{2017}
[...]
/opt/local/bin/texi2dvi: pdftex exited with bad status, quitting.
make[1]: *** [orgcard.pdf] Error 1
make: *** [card] Error 2

$ cat doc/org-version.tex
% automatically generated, do not edit
\def\orgversionnumber{9.0.9}
\def
ersionyear{2017}
\def\year{2017}

I have no idea how that \v is getting turned into a vertical tab.  Is make
processing these?

$ gmake --version
GNU Make 4.2.1
Built for x86_64-apple-darwin15.6.0
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ cat /tmp/test-makefile
single:
echo "single: 123\v456"

double:
echo "double: 123\\v456"

quad:
echo "quad: 123v456"
$ gmake -f /tmp/test-makefile single double quad
echo "single: 123\v456"
single: 123
   456
echo "double: 123\\v456"
double: 123
   456
echo "quad: 123v456"
quad: 123\v456

Is this something screwed up in my environment or are others seeing this as
well?

Thanks,
Dale


[O] org-todo-keyword-faces in agenda

2017-04-12 Thread Dale
Greetings!  I've got a file-local org-todo-keyword-faces set in an
org-mode file.  When I use agenda on this org file, my keyword faces
from the org-mode buffer don't carry over to the agenda buffer.  I
assume this is because the local org-todo-keyword-faces value is not
set in the agenda buffer.

If my assumption is correct, does anyone have an idea of how I could
accomplish getting my file-local org-todo-keyword-faces value into
agenda buffers?

I don't want to set org-todo-keyword-faces globally since the values
there only apply to a single org-mode file.

For a test case, drop these four lines in an org-mode file:

* TODO Test
# Local Variables:
# org-todo-keyword-faces: (("TODO" . "blue"))
# End:

Load up that file, accept the "unsafe" local value, then M-x
org-agenda RET < t (all to-dos only from the current org-mode buffer).
The TODO in the agenda buffer is the default red, rather than the blue
I set in the org file.

I've thought of two *possibilities* that I haven't really explored yet:

1. Agenda could copy the keyword from the contributing org-mode buffer
with its face text property intact (but I can imagine that this would
interfere with other features, such as existing customizations in
org-agenda)

2. Some hook function that figures out which org-mode buffer(s)
contributed to an agenda view and copies/merges org-todo-keyword-faces
values into the agenda buffer

Thanks!
Dale



[O] Bug: Agenda clockcheck: org-duration-to-minutes: Wrong type argument: stringp [9.0.5 (release_9.0.5-318-gb1353c @ /tmp/emacs/org-mode/lisp\ /)]

2017-02-22 Thread Dale
Hi!  I think org-mode from master currently has a bug in agenda's
clockcheck mode.  Steps to reproduce:

1. Start emacs -Q and load org-mode master (b1353cb6f83)

2. Open a empty org-mode buffer, e.g.: C-x C-f test.org RET

3. M-x org-agenda RET

4. Hit "a" for "Agenda for current day or week"

5. Hit "v" then "c" to switch to clockcheck view

Expected results: clockcheck view is engaged (albeit empty given the
empty org-mode file)

Observed results: I receive the following error:

org-duration-to-minutes: Wrong type argument: stringp, 0

Due to this error, clockcheck mode does not seem to activate.

Emacs  : GNU Emacs 25.1.1 (x86_64-apple-darwin15.6.0)
 of 2017-01-30
Package: Org mode version 9.0.5 (release_9.0.5-318-gb1353c @
/tmp/emacs/org-mode/lisp/)

Other information:

I suspect this is happening as of the recent switch to using the
org-duration library (7e8cf5f4c20), which replaced some/all uses of
org-hh:mm-string-to-minutes with org-duration-to-minutes.
org-hh:mm-string-to-minutes accepted an integer as its argument
(despite its name):

(cond
 ((integerp s) s)
 ...

In contrast, org-duration-to-minutes only expects a string as its
argument.  The "Wrong type argument" seems to be coming from its first
string-match-p call.

org-agenda-show-clocking-issues will potentially call
org-duration-to-minutes with the integer 0 as its argument:

(mintime (org-duration-to-minutes
  (or (plist-get pl :min-duration) 0)))

The default value for org-agenda-clock-consistency-checks also
specifies :min-duration 0; that is, an integer rather than a string.

I cannot say whether org-duration-string should accept a number, as
org-hh:mm-string-to-minutes did, or instead whether org-agenda.el
should be changed to always pass it a string.

Kind regards,
Dale



[O] Bug: Properties don't work in clocktable [9.0.5 (release_9.0.5-305-g21797c @ /Users/dale/.emacs.d/el-get/org-mode/lisp/)]

2017-02-18 Thread Dale
For me, clocktable's :properties option is including columns for the
properties, but is never including the actual values for those properties.
This *may* be a bug, specifically in org-clock.el line 2590:

(pcase-dolist (`(,level ,headline ,ts ,time . ,props) entries)
  ...)

I believe the ". ,props" should be just ",props", since I think the list
of properties here is its own list, and not the cdr of entries:

(pcase-dolist (`(,level ,headline ,ts ,time ,props) entries)
  ...)

To reproduce this problem using org-mode HEAD, evaluate the following:

(switch-to-buffer (generate-new-buffer "*org mode test*"))
(org-mode)
(insert "* Time
:PROPERTIES:
:FOO:  bar
:END:
:LOGBOOK:
CLOCK: [2017-02-18 Sat 10:50]--[2017-02-18 Sat 10:51] =>  0:01
:END:

#+BEGIN: clocktable :compact t :properties (\"FOO\") :maxlevel 2
:scope subtree
#+END:
")
(goto-char (point-max))
(forward-line -1)
(org-dblock-update)

Expected result which includes the property value:

#+BEGIN: clocktable :compact t :properties ("FOO") :maxlevel 2 :scope subtree
#+CAPTION: Clock summary at [2017-02-18 Sat 10:59]
| FOO | Headline | Time|
|-+--+-|
| | *Total time* | *0.02h* |
|-+--+-|
| bar | Time | 0.02h   |
#+END:

Observed result from HEAD, note no property value:

#+BEGIN: clocktable :compact t :properties ("FOO") :maxlevel 2 :scope subtree
#+CAPTION: Clock summary at [2017-02-18 Sat 10:54]
| FOO | Headline | Time|
|-+--+-|
| | *Total time* | *0.02h* |
|-+--+-|
| | Time | 0.02h   |
#+END:

Emacs  : GNU Emacs 25.2.1 (x86_64-apple-darwin15.6.0, Carbon Version
157 AppKit 1404.47)
 of 2017-02-07
Package: Org mode version 9.0.5 (release_9.0.5-305-g21797c @
/Users/dale/.emacs.d/el-get/org-mode/lisp/)

I'll take every opportunity I can to thank all the people who work to
make org-mode so indispensable!  Thank you!

Dale



[O] Bug: clocktable doesn't preserve formulas with :scope file-with-archives

2016-10-21 Thread Dale
Hi!  I've found that the "#+TBLFM:" in a clocktable can get changed or
deleted when used together with ":scope file-with-archives".  Here's a
minimal org file to reproduce with:

--8<--
* Test
:LOGBOOK:
CLOCK: [2016-10-20 Thu 17:42]--[2016-10-20 Thu 18:03] =>  0:21
:END:

#+BEGIN: clocktable :scope file-with-archives
#+TBLFM: $3=string("foo")
#+END:
--8<--

Steps to reproduce:

1. emacs -Q, load above file with org-mode from Git

2. Update clocktable dblock (move to "#+BEGIN" and C-c C-c)

Expected result: a third column is added with value "foo" in every
row; #+TBLFM line is preserved

Observed result: table has two columns, the second of which contains
"foo" in every row; #+TBLFM line changes from $3=string("foo") to
$2=string("foo")

If you keep updating the block, the formula's "$2" then becomes "$1".
Do it one more time and the "#+TBLFM:" is preserved but now the
formula is gone entirely.

Emacs  : GNU Emacs 25.1.1 (x86_64-apple-darwin15.6.0)
 of 2016-09-23
Package: Org-mode version 8.2.10 (release_8.2.10 @ /opt/local/share/emacs/25.1/\
lisp/org/)

I have also reproduced this with org-mode from Git as of an hour or so ago.

My hunch is that the problem is in org-clocktable-write-default.  It
writes the table (the dblock's contents have already been deleted),
restores any #+TBLFM: line that used to be there pre-update, and then,
if you're using :scope file-with-archives, it deletes the file column,
which is the first column.  The order here is the problem:
org-table-delete-column updates the formula in #+TBLFM, decrementing
the column reference to account for the deleted column.

If this sounds right then I'd suggest that the solution may be as
simple as just updating org-clocktable-write-default to insert table
formulas *after* deleting the file column, along with some

I'm attaching a patch but I'm not sure whether you'll be able to use
it because my FSF assignment hasn't been updated for my new employer.
Even if you can't use it, hopefully my description above is still
useful.

Thanks!

Dale


clocktable-formulas.patch
Description: Binary data


[O] Bug: Column mode display broken after adding PROPERTIES drawer [8.3.1 (release_8.3.1-176-g45abec @ /tmp/minimal-org/org-mode/lisp/)]

2015-08-25 Thread Dale
I believe I have found a bug with column mode in org-mode from Git
(45abec0): if editing a column's value adds a PROPERTIES drawer then
the column mode display becomes corrupted.

Steps to reproduce:

1. Create an org-mode buffer with the following contents:

--8--
#+COLUMNS: %62ITEM(Task) %8Effort(Estimate){:}
* Parent
** Test 1
** Test 2
--8--

2. Move cursor to Parent headline

3. Enter column mode with C-c C-x C-c

4. Move cursor into Estimate column of Test 1 task

5. Press e to edit the column's value and enter any value (e.g. 0:00)

Expected visible buffer contents:

--8--
Task   | Estimate |
#+COLUMNS: %10ITEM(Task) %8Effort(Estimate){:}
* Parent   | 0:00 |
** Test 1  | 0:00 |...
** Test 2  |  |
--8--

What I observed instead of that, the Test 2 heading being moved onto
the same line as Test 1:

--8--
Task   | Estimate |
#+COLUMNS: %10ITEM(Task) %8Effort(Estimate){:}
* Parent   | 0:00 |
** Test 1  | 0:00 |...** Test 2  |  |
--8--

Note that the Test 2 headline has been moved to the end of the Test
1 headline.  Pressing down arrow from Test 1's Estimate column moves
to Test 2's Estimate column just as it appears, way off to the right
of the Test 1 heading rather than below it.

Tested with Emacs 24.5.1 built from MacPorts on OS X 10.9 with emacs
-nw -Q -L org-mode/lisp.





Emacs  : GNU Emacs 24.5.1 (x86_64-apple-darwin13.4.0, NS
apple-appkit-1265.21)
 of 2015-08-25 on dale
Package: Org-mode version 8.3.1 (release_8.3.1-176-g45abec @
/tmp/minimal-org/org-mode/lisp/)

current state:
==
(setq
 org-tab-first-hook '(org-hide-block-toggle-maybe
org-babel-hide-result-toggle-maybe org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-confirm-shell-link-function 'yes-or-no-p
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '((lambda nil (org-add-hook (quote change-major-mode-hook)
(quote org-show-block-all) (quote append) (quote local)))
(lambda nil (org-add-hook (quote change-major-mode-hook) (quote
org-babel-show-result-all) (quote append) (quote local)))
org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-show-empty-lines
 org-optimize-window-after-visibility-change)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 )


Re: [O] Using org-goto loses org-todo-keyword-faces settings

2013-09-02 Thread Dale
How surprising!  I just confirmed this again by installing Emacs 24.3
release from MacPorts, running emacs -Q in a terminal Emacs, loading
org-mode from Git, and opening the below org file, making sure to
accept the unsafe file local setting of org-todo-keyword-faces.  I
was able to reproduce it: WAITING was orange before org-goto, default
red after org-goto.

Now I wonder what's different about my setup!

Oh well, thanks anyway for looking at this.  For the time being I've
just added after advice to org-goto to run (font-lock-fontify-buffer),
which restores my colors when I exit org-goto.

Regards,
Dale


On Mon, Sep 2, 2013 at 12:42 AM, Carsten Dominik
carsten.domi...@gmail.com wrote:
 Hi Dale,

 thank you for the report and detailed example.  I have followed your recipe 
 and cannot reproduce the issue.

 Regards

 - Carsten

 On 21.8.2013, at 02:25, Dale d...@codefu.org wrote:

 Hi,

   My thanks to everyone who works on org-mode.  It is a truly 
 indispensable tool.

   I'm not sure if I have a bug or a feature request: I have custom faces 
 set up for my todo keywords (see my file local variable for 
 org-todo-keyword-faces at the bottom of this report).   When I use org-goto 
 (C-c C-j) and then exit goto mode, my custom colors for todo keywords are 
 reset to the defaults.

   Explicitly:

 1. Create and save an org file with the following contents:

 --8--Cut here--8--
 * WAITING test1

 #+TODO: NEW(n) PENDING(p!) WAITING(w!) HOLD(h!) | DONE(d!) CANCELLED(c!)

 # Local Variables:
 # org-todo-keyword-faces: ((WAITING . dark orange)
 #  (HOLD . dark orange))
 # End:
 --8--Cut here--8--

 2. Revert the buffer to pick up the in-buffer configuration including file 
 local variables.

 3. C-c C-j followed by C-g to exit goto mode.

 What I expected: WAITING would still be dark orange when I exit goto mode.

 What I observed: WAITING reverts to the default red color when I exit goto 
 mode.

 (WAITING is also red while I'm in org-goto mode, which is less of a problem 
 for me.  I'd be happy enough if the color was just restored when I'm done 
 with org-goto.)

   I would, of course, be grateful if my org-todo-keyword-faces would 
 still be respected after using goto mode.

   I am using Emacs 24.3.1, apparently, the unofficial Emacs Mac Port 
 (ftp://ftp.math.s.chiba-u.ac.jp/emacs/).  I just confirmed this behavior 
 using org-mode's master branch from git://orgmode.org/org-mode.git as of a 
 few minutes ago.  The output from org-submit-bug-report is below.

 Thanks for everything,
 Dale


 Emacs  : GNU Emacs 24.3.1 (x86_64-apple-darwin12.4.0, Carbon Version 1.6.0 
 AppKit 1187.39)
 of 2013-06-26
 Package: Org-mode version 8.0.7 (release_8.0.7-383-g927f1b @ 
 /Users/dale/.emacs.d/packages/org-mode/)

 current state:
 ==
 (setq
 org-hide-leading-stars t
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-default-hook
  org-babel-speed-command-hook)
 org-reverse-note-order t
 org-time-clocksum-format %d:%02d
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-agenda-todo-ignore-deadlines 'far
 org-src-window-setup 'other-window
 org-confirm-shell-link-function 'yes-or-no-p
 org-agenda-todo-ignore-scheduled 1
 org-default-notes-file ~/todo.org
 org-startup-indented t
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
 org-src-mode-configure-edit-buffer)
 org-tags-column -76
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-agenda-dim-blocked-tasks nil
 org-mode-hook '(#[nil \300\301\302\303\304$\207
   [org-add-hook change-major-mode-hook org-show-block-all
append local]
   5]
 #[nil \300\301\302\303\304$\207
   [org-add-hook change-major-mode-hook
org-babel-show-result-all append local]
   5]
 org-babel-result-hide-spec org-babel-hide-all-hashes
 my:org-mode-hook)
 org-outline-path-complete-in-steps nil
 org-agenda-todo-list-sublevels nil
 org-replace-disputed-keys t
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
  org-babel-execute-safely-maybe)
 org-refile-use-outline-path t
 org-enforce-todo-dependencies t
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-hide-inline-tasks org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-after-refile-insert-hook '(my:org-maybe-note-refile)
 org-metareturn-hook '(my:org-meta-return-hook)
 org

[O] Using org-goto loses org-todo-keyword-faces settings

2013-08-21 Thread Dale
Hi,

My thanks to everyone who works on org-mode.  It is a truly 
indispensable tool.

I'm not sure if I have a bug or a feature request: I have custom faces 
set up for my todo keywords (see my file local variable for 
org-todo-keyword-faces at the bottom of this report).   When I use org-goto 
(C-c C-j) and then exit goto mode, my custom colors for todo keywords are reset 
to the defaults.

Explicitly:

1. Create and save an org file with the following contents:

--8--Cut here--8--
* WAITING test1

#+TODO: NEW(n) PENDING(p!) WAITING(w!) HOLD(h!) | DONE(d!) CANCELLED(c!)

# Local Variables:
# org-todo-keyword-faces: ((WAITING . dark orange)
#  (HOLD . dark orange))
# End:
--8--Cut here--8--

2. Revert the buffer to pick up the in-buffer configuration including file 
local variables.

3. C-c C-j followed by C-g to exit goto mode.

What I expected: WAITING would still be dark orange when I exit goto mode.

What I observed: WAITING reverts to the default red color when I exit goto mode.

(WAITING is also red while I'm in org-goto mode, which is less of a problem for 
me.  I'd be happy enough if the color was just restored when I'm done with 
org-goto.)

I would, of course, be grateful if my org-todo-keyword-faces would 
still be respected after using goto mode.

I am using Emacs 24.3.1, apparently, the unofficial Emacs Mac Port 
(ftp://ftp.math.s.chiba-u.ac.jp/emacs/).  I just confirmed this behavior using 
org-mode's master branch from git://orgmode.org/org-mode.git as of a few 
minutes ago.  The output from org-submit-bug-report is below.

Thanks for everything,
Dale


Emacs  : GNU Emacs 24.3.1 (x86_64-apple-darwin12.4.0, Carbon Version 1.6.0 
AppKit 1187.39)
 of 2013-06-26
Package: Org-mode version 8.0.7 (release_8.0.7-383-g927f1b @ 
/Users/dale/.emacs.d/packages/org-mode/)

current state:
==
(setq
 org-hide-leading-stars t
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-default-hook
  org-babel-speed-command-hook)
 org-reverse-note-order t
 org-time-clocksum-format %d:%02d
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-agenda-todo-ignore-deadlines 'far
 org-src-window-setup 'other-window
 org-confirm-shell-link-function 'yes-or-no-p
 org-agenda-todo-ignore-scheduled 1
 org-default-notes-file ~/todo.org
 org-startup-indented t
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
 org-src-mode-configure-edit-buffer)
 org-tags-column -76
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-agenda-dim-blocked-tasks nil
 org-mode-hook '(#[nil \300\301\302\303\304$\207
   [org-add-hook change-major-mode-hook org-show-block-all
append local]
   5]
 #[nil \300\301\302\303\304$\207
   [org-add-hook change-major-mode-hook
org-babel-show-result-all append local]
   5]
 org-babel-result-hide-spec org-babel-hide-all-hashes
 my:org-mode-hook)
 org-outline-path-complete-in-steps nil
 org-agenda-todo-list-sublevels nil
 org-replace-disputed-keys t
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
  org-babel-execute-safely-maybe)
 org-refile-use-outline-path t
 org-enforce-todo-dependencies t
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-hide-inline-tasks org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-after-refile-insert-hook '(my:org-maybe-note-refile)
 org-metareturn-hook '(my:org-meta-return-hook)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-default-priority 68
 org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
 org-completion-use-ido t
 org-src-preserve-indentation t
 org-clock-in-hook '(my:org-clock-in-set-pending-hook)
 org-agenda-files '(~/todo.org)
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 )

In-buffer configuration:

#+TODO: NEW(n) PENDING(p!) WAITING(w!) HOLD(h!) | DONE(d!) CANCELLED(c!)

# Local Variables:
# org-todo-keyword-faces: ((WAITING . dark orange)
#  (HOLD . dark orange))
# End:



[O] problem with figure captions / labels in LaTeX export

2013-03-20 Thread Dale Barr
Hi all,

First I would just like to thank all the people responsible for org-mode.
 It is an amazing product that has become an indispensable part of my
workflow!

I encountered a problem with LaTeX export that seems to affect org-versions
7.9.3f and 7.9.4.
Specifically, exporting figure captions and labels using #+CAPTION and
#+LABEL no longer seems to work.

### start of code snippet

#+TITLE: My Important Paper

#+AUTHOR:Dr. Nyan

#+DATE:  \today

#+LATEX_CLASS: article
#+LATEX_CLASS_OPTIONS: []

* Section 1

See Figure\nbsp{}\ref{fig:myfig} below

#+CAPTION: This is a figure
#+LABEL: fig:myfig
file:myfig.pdf

### end of code snippet

When I look in the LaTeX output after exporting, I see:

See Figure~{}\ref{fig:myfig} below

\includegraphics[width=.9\linewidth]{myfig.pdf}

There is no figure caption and the label fig:myfig is unresolved.

Thanks for looking into this!

-Dale Barr


Re: [Orgmode] Re: Custom docbook stylesheets.

2010-05-13 Thread Dale P. Smith
Carsten Dominik carsten.domi...@gmail.com writes:

 Somehow I do net seem to have a patch relating to this thread.  Can  
 you please send it again?  Baoqiu, you agree that this should be  
 applied?


Here is is.

diff --git a/lisp/org-docbook.el b/lisp/org-docbook.el
index 8a89675..37851da 100644
--- a/lisp/org-docbook.el
+++ b/lisp/org-docbook.el
@@ -77,6 +77,7 @@
 (require 'org)
 (require 'org-exp)
 (require 'org-html)
+(require 'format-spec)
 
 ;;; Variables:
 
@@ -330,10 +331,10 @@ in a window.  A non-interactive call will only return the buffer.
   Export as DocBook XML file, and generate PDF file.
   (interactive P)
   (if (or (not org-export-docbook-xslt-proc-command)
-	  (not (string-match %s.+%s org-export-docbook-xslt-proc-command)))
+	  (not (string-match %[io].+%[io] org-export-docbook-xslt-proc-command)))
   (error XSLT processor command is not set correctly))
   (if (or (not org-export-docbook-xsl-fo-proc-command)
-	  (not (string-match %s.+%s org-export-docbook-xsl-fo-proc-command)))
+	  (not (string-match %[io].+%[io] org-export-docbook-xsl-fo-proc-command)))
   (error XSL-FO processor command is not set correctly))
   (message Exporting to PDF...)
   (let* ((wconfig (current-window-configuration))
@@ -345,10 +346,10 @@ in a window.  A non-interactive call will only return the buffer.
 	 (pdffile (concat base .pdf)))
 (and (file-exists-p pdffile) (delete-file pdffile))
 (message Processing DocBook XML file...)
-(shell-command (format org-export-docbook-xslt-proc-command
-			   fofile (shell-quote-argument filename)))
-(shell-command (format org-export-docbook-xsl-fo-proc-command
-			   fofile pdffile))
+(shell-command (format-spec org-export-docbook-xslt-proc-command
+(format-spec-make ?o fofile ?i (shell-quote-argument filename
+(shell-command (format-spec org-export-docbook-xsl-fo-proc-command
+(format-spec-make ?i fofile ?o pdffile)))
 (message Processing DocBook file...done)
 (if (not (file-exists-p pdffile))
 	(error PDF file was not produced)

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: Custom docbook stylesheets.

2010-05-13 Thread Dale P. Smith
Carsten Dominik carsten.domi...@gmail.com writes:

 do I still need to do something with #+XSLT?  If yes, could you please
 spell it out for me?

Ok!

So now the command to process docbook to whatever is more flexible.
Previously, the the order of input file and output file were fixed,
and the stylesheet was hard-coded into the command.

The goal of this is to allow for the name of a stylesheet file to be
directly in the org file itself, using #+XSLT (or soemthing else?).  I
can see how individual documents could require differnt stylesheets.

So either the command to process can be in the org file, or the
default command can be modified to use a stylesheet variable, and that
variable can be in the org file.

-Dale


-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: Custom docbook stylesheets.

2010-05-13 Thread Dale P. Smith
Baoqiu Cui cbao...@yahoo.com writes:

 Before I change the document for variable
 `org-export-docbook-xslt-proc-command', let's finalize the design of
 this first. :-)

 Currently `org-export-docbook-xslt-proc-command' contains two
 format-like specs: %i (for the input DocBook XML file) and %o (for
 the output FO file).  Values of these two specs will be generated based
 on the Org file name to be exported.

 We should add a 3rd spec, %s, to this variable for the XSLT stylesheet
 that users would like to use for exporting the Org file.  As Dale
 pointed earlier, users would like to use different stylesheets for
 different Org files.  By default, the value of the stylesheet is set
 based on a new customizable variable called
 `org-export-docbook-xslt-stylesheet'.  However users can use #+XSLT in
 each individual Org file to override it.

 Are you OK with this?

I am.  It's pretty much exactly what I was thinking.

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: Custom docbook stylesheets.

2010-05-03 Thread Dale P. Smith
Baoqiu Cui cbao...@yahoo.com writes:

 Hi Dale,

 Dale Smith dsm...@vtiinstruments.com writes:

 Dale Smith dsm...@vtiinstruments.com writes:

 The current org-export-docbook-xslt-proc-command is a format string,
 with a fixed order of arguments (the fo filename and then the input
 docbook filname).  Thats probably good enough for most (all?) xslt
 processors, but things may be more limited when it comes to also
 specifying the stylesheet.  Do we need to have some kind of special
 markers in the format string for where the different options go?
 Something like $i $o and $s (for in, out, and stysheet)?

 I thought about doing something similar to make the commands easier to
 set, but stopped pursuing that after seeing the format string style
 worked fine.  I am not sure if any other Emacs modes/packages have done
 something like this, i.e. using (semi)named arguments.

 Well, it took me a while, but it found it.  It's the format-spec
 function. (Actually, http://edward.oconnor.cx/2009/06/format-spec
 clued me in.)

 I'll have a go at it today and see if I can send in a patch.

 Ok.  This works for me.  Docs are not updated.  That would push me
 over the 10 line limit. ;^)

 Thanks for working on this patch, which looks very good to me!  Yes, I
 think format-spec is the right way to go, and it does make the command
 format more flexible.

This didn't seem to make it into org-mode.  Any chance it could be
added?

Thanks,
  -Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: [BUG] revering agenda files

2010-04-12 Thread Dale P. Smith
Łukasz Stelmach lukasz.stelm...@iem.pw.edu.pl writes:

 Richard Riley rileyrg...@gmail.com writes:

 Łukasz Stelmach lukasz.stelm...@iem.pw.edu.pl writes:
 I'm not quite sure it is bug indeed but org-mode stops working as usual
 when you change the agenda files behind the scenes. I sometimes do it
 because I use org-mode on several machines and I keep my files
 synchronised with git. Since git-vc.el doesn't provide interface for
 git's push pull commands I have to invoke them from outside of Emacs.

 Use magit perhaps? or egg.

 I'll give them a try. Thanks.

Magit is awesome.  I'd choose git for just so I can use magit.

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: OrgmodeOrgmodePOLL: Change of keys to move agenda through time

2009-08-25 Thread Dale Smith
Wes Hardaker wjhns...@hardakers.net writes:

 On Tue, 25 Aug 2009 08:30:51 -0700, Wes Hardaker 
 wjhns...@hardakers.net said:

 On Tue, 25 Aug 2009 11:12:16 +0200, Carsten Dominik 
 carsten.domi...@gmail.com said:
 CD 1. Make the cursor keys LEFT and RIGHT do normal cursor motion again

 WH +1.  I find these two keys have confused me more than any others 

 Thinking about it further, I realized a good part of the confusion
 results from the up/down keys actually doing in-buffer movement and
 left/right doing date movement.  I don't think that's natural for
 people.  They expect the arrows, be it up/down/left/right, to act in a
 similar fashion to each other.

Yes, I think your are right.

I also used to experience this problem a while ago.  And then I picked
up some code in this list that highlight the current agenda line:

(add-hook 'org-agenda-mode-hook '(lambda () (hl-line-mode 1)))

(I think that's the code anyway.)  And now I *never* go off in the
weeds with my Right  Left keys.

For me, I think I use the cursor to help my eyes focus on something.
Usually in the agenda the cursor is off to one side. I want to move it
to the column I'm actuallly looking at, so I lean on it for about
the right key-repeat time to get it there.  That would throw the
agenda several months in the future.

But that all stopped once I started using that hightlight code above.

My $.02

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: Custom docbook stylesheets.

2009-06-22 Thread Dale Smith
Baoqiu Cui cbao...@yahoo.com writes:

 The current org-export-docbook-xslt-proc-command is a format string,
 with a fixed order of arguments (the fo filename and then the input
 docbook filname).  Thats probably good enough for most (all?) xslt
 processors, but things may be more limited when it comes to also
 specifying the stylesheet.  Do we need to have some kind of special
 markers in the format string for where the different options go?
 Something like $i $o and $s (for in, out, and stysheet)?

 I thought about doing something similar to make the commands easier to
 set, but stopped pursuing that after seeing the format string style
 worked fine.  I am not sure if any other Emacs modes/packages have done
 something like this, i.e. using (semi)named arguments.

Well, it took me a while, but it found it.  It's the format-spec
function. (Actually, http://edward.oconnor.cx/2009/06/format-spec
clued me in.)

I'll have a go at it today and see if I can send in a patch.

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: Custom docbook stylesheets.

2009-06-22 Thread Dale Smith
Dale Smith dsm...@vtiinstruments.com writes:

 The current org-export-docbook-xslt-proc-command is a format string,
 with a fixed order of arguments (the fo filename and then the input
 docbook filname).  Thats probably good enough for most (all?) xslt
 processors, but things may be more limited when it comes to also
 specifying the stylesheet.  Do we need to have some kind of special
 markers in the format string for where the different options go?
 Something like $i $o and $s (for in, out, and stysheet)?

 I thought about doing something similar to make the commands easier to
 set, but stopped pursuing that after seeing the format string style
 worked fine.  I am not sure if any other Emacs modes/packages have done
 something like this, i.e. using (semi)named arguments.

 Well, it took me a while, but it found it.  It's the format-spec
 function. (Actually, http://edward.oconnor.cx/2009/06/format-spec
 clued me in.)

 I'll have a go at it today and see if I can send in a patch.

Ok.  This works for me.  Docs are not updated.  That would push me
over the 10 line limit. ;^)

Now we can easily add other options, like %s for stylesheets or
whatever.  Maybe something like %p to set parameters. (As in the
--stringparam option to xsltproc).

What would be cool is a way to allow the user to *add* custom spec
chars to the default set. (hint hint)

-Dale

diff --git a/lisp/org-docbook.el b/lisp/org-docbook.el
index 8a89675..37851da 100644
--- a/lisp/org-docbook.el
+++ b/lisp/org-docbook.el
@@ -77,6 +77,7 @@
 (require 'org)
 (require 'org-exp)
 (require 'org-html)
+(require 'format-spec)
 
 ;;; Variables:
 
@@ -330,10 +331,10 @@ in a window.  A non-interactive call will only return the buffer.
   Export as DocBook XML file, and generate PDF file.
   (interactive P)
   (if (or (not org-export-docbook-xslt-proc-command)
-	  (not (string-match %s.+%s org-export-docbook-xslt-proc-command)))
+	  (not (string-match %[io].+%[io] org-export-docbook-xslt-proc-command)))
   (error XSLT processor command is not set correctly))
   (if (or (not org-export-docbook-xsl-fo-proc-command)
-	  (not (string-match %s.+%s org-export-docbook-xsl-fo-proc-command)))
+	  (not (string-match %[io].+%[io] org-export-docbook-xsl-fo-proc-command)))
   (error XSL-FO processor command is not set correctly))
   (message Exporting to PDF...)
   (let* ((wconfig (current-window-configuration))
@@ -345,10 +346,10 @@ in a window.  A non-interactive call will only return the buffer.
 	 (pdffile (concat base .pdf)))
 (and (file-exists-p pdffile) (delete-file pdffile))
 (message Processing DocBook XML file...)
-(shell-command (format org-export-docbook-xslt-proc-command
-			   fofile (shell-quote-argument filename)))
-(shell-command (format org-export-docbook-xsl-fo-proc-command
-			   fofile pdffile))
+(shell-command (format-spec org-export-docbook-xslt-proc-command
+(format-spec-make ?o fofile ?i (shell-quote-argument filename
+(shell-command (format-spec org-export-docbook-xsl-fo-proc-command
+(format-spec-make ?i fofile ?o pdffile)))
 (message Processing DocBook file...done)
 (if (not (file-exists-p pdffile))
 	(error PDF file was not produced)


-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: Custom docbook stylesheets.

2009-05-28 Thread Dale Smith
Carsten Dominik carsten.domi...@gmail.com writes:

  Thanks for the suggestion, Carsten!  It's a little hard for me to  
 decide
 which way is better to specify the stylesheet: #+XSLT or Local
 Variables:.  Maybe #+XSLT is better?  I don't see many local
 variables being used in Org mode...  Please advise.

 This is only a mater of convenience.  The #+ syntax is easier to
 set up and refresh, so I prefer it for stuff that is frequently changed.
 But you can also use file variables of course

#+ I think would be better.  Does it make sense to do something
 extensible, like the #+ macros?  Then Carsten won't need to be adding
 new #+ words all the time. ;^)

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Custom docbook stylesheets.

2009-05-26 Thread Dale Smith
Greetings List,

I was suprised an pleased to discover that the docbook exporter has
the ability to apply the stylesheets to transform to fo and to also
process that to pdf.  Somehing I'd like to see is a document specific
way to specify the stylesheet.  I tried setting
org-export-docbook-xslt-proc-command in a Local Variables: section,
but it seems the variable is being used from a different buffer.

So, what do you think about some kind of document property to
overrride a global setting?

The current org-export-docbook-xslt-proc-command is a format string,
with a fixed order of arguments (the fo filename and then the input
docbook filname).  Thats probably good enough for most (all?) xslt
processors, but things may be more limited when it comes to also
specifying the stylesheet.  Do we need to have some kind of special
markers in the format string for where the different options go?
Something like $i $o and $s (for in, out, and stysheet)?

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: {{{macro}}} expansion not working properly for docbook export

2009-05-20 Thread Dale Smith
Baoqiu Cui cbao...@yahoo.com writes:

 Thanks for reporting this bug.  For some reason I missed the coverage of
 macro support in DocBook exporter, and the bug was caused by an
 optimization that I thought I did in the code...  Variable
 org-export-opt-plist should have been set but it was not in DocBook
 exporter.

 Attached please find the patch for the fix.  Please let me know if it
 works.

Works great!

This bug may be related to another I noticed.  I don't yet have a clear
picture yet of what is (not) going on.  Basically, the time reported
by modification time was just plain wrong.  By over a day.  And I
*know* I just saved the file.

I'm guessing now that the property was cached.  If so, that property
should *not* be. It really needs to be fresh every time an export is
done.

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Re: {{{macro}}} expansion not working properly for docbook export

2009-05-20 Thread Dale Smith
Baoqiu Cui cbao...@yahoo.com writes:

 This bug may be related to another I noticed.  I don't yet have a clear
 picture yet of what is (not) going on.  Basically, the time reported
 by modification time was just plain wrong.  By over a day.  And I
 *know* I just saved the file.

 I'm guessing now that the property was cached.  If so, that property
 should *not* be. It really needs to be fresh every time an export is
 done.

 I am not able to reproduce this problem.  I tried adding the following
 line in an Org file

{{{modification-time(%Y-%m-%d %H:%M:%S)}}}

 and then tried to save the file multiple times with minor changes, and
 was able to consistently get the correct time in the exported DocBook
 file.

Indeed is *is* now working correctly.  So I guessing that the time was
frozen at the point I did an html export.  Now that the docbook
exporter is generating the properties, the time is being updated.
Yay!

Thanks again,
  -Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] {{{macro}}} expansion not working properly for docbook export

2009-05-19 Thread Dale Smith
{{{maxro}}} expansion does not happen for docbook export until an html
export is done.  After that, macros seems to be expanded properly for
docbook export.

Thanks!
  -Dale
-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Commas in {{date(FORMAT)}}}

2009-05-18 Thread Dale Smith
Carsten Dominik carsten.domi...@gmail.com writes:

 On May 14, 2009, at 11:03 PM, Dale Smith wrote:

   I'm confused about the value of FORMAT in {{{date(FORMAT)}}}.

   I wanted to use %B %e, %Y, but I have two problems.  With the
   quotes, I get an eval: End of file during parsing message.  Without
   the quotes, processing stops at the comma, expanding to May 14
   instead of May 14, 2009.

   Thanks,
 -Dale

 Wow, I knew this report was coming, but I had not at all
 expected it so fast.

heh.

 , is the (undocumented) argument separator for Org macros.
 Actually, I am changing it now to ;, so that your example
 should now directly work.  To include a semicolon in the date
 format, use \;.

Thanks.
  -Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Commas in {{date(FORMAT)}}}

2009-05-15 Thread Dale Smith
Dale Smith dsm...@vtiinstruments.com writes:

 I'm confused about the value of FORMAT in {{{date(FORMAT)}}}.

 I wanted to use %B %e, %Y, but I have two problems.  With the
 quotes, I get an eval: End of file during parsing message.  Without
 the quotes, processing stops at the comma, expanding to May 14
 instead of May 14, 2009.

(Apologies about answering my own mails and all that.)

Using \x2c instead of , seems to work nicely.

So {{{date(%B %e\x2c %Y)}}} gives me what I was looking for.

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Commas in {{date(FORMAT)}}}

2009-05-14 Thread Dale Smith
I'm confused about the value of FORMAT in {{{date(FORMAT)}}}.

I wanted to use %B %e, %Y, but I have two problems.  With the
quotes, I get an eval: End of file during parsing message.  Without
the quotes, processing stops at the comma, expanding to May 14
instead of May 14, 2009.

Thanks,
  -Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] ditaa and dot blocks with docbook export

2009-05-09 Thread Dale Smith
So I was looking at http://doc.norang.ca/org-mode.html and saw the
integration with ditaa, and wondered how hard that would be to get
workign with the docbook exporter.  Oh! There is a dot block in there
too! Cool.  Hmm.  Lets try adding docbookp.

Boy was *that* easy!  Works great.  Thanks Baoqiu Cui.

-Dale

 From 0c534df7af71e0a742a7123a14e0293da9f0e4c6 Mon Sep 17 00:00:00 2001
From: Dale Smith da...@flexo.cle.vtiinstruments.lcl
Date: Fri, 8 May 2009 10:54:49 -0400
Subject: [PATCH] Add support for docbook export for dot and ditaa blocks.

---
 contrib/lisp/org-exp-blocks.el |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/contrib/lisp/org-exp-blocks.el b/contrib/lisp/org-exp-blocks.el
index 5803458..bbecd18 100644
--- a/contrib/lisp/org-exp-blocks.el
+++ b/contrib/lisp/org-exp-blocks.el
@@ -187,7 +187,7 @@ passed to the ditaa utility as command line arguments.
 			(org-split-string body \n)
 			\n)))
 (cond 
- ((or htmlp latexp)
+ ((or htmlp latexp docbookp)
   (with-temp-file data-file (insert body))
   (message (concat java -jar  org-ditaa-jar-path   args   data-file   out-file))
   (shell-command (concat java -jar  org-ditaa-jar-path   args   data-file   out-file))
@@ -222,7 +222,7 @@ digraph data_relationships {
 	(args (if (cdr headers) (mapconcat 'identity (cdr headers)  )))
 	(data-file (make-temp-file org-ditaa)))
 (cond 
- ((or htmlp latexp)
+ ((or htmlp latexp docbookp)
   (with-temp-file data-file (insert body))
   (message (concat dot  data-file   args  -o  out-file))
   (shell-command (concat dot  data-file   args  -o  out-file))
-- 
1.6.0.3



-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: DocBook exporter code (version 1.0)

2009-03-13 Thread Dale Smith
Carsten Dominik domi...@science.uva.nl writes:

 On Mar 13, 2009, at 3:05 AM, Baoqiu Cui wrote:

 Baoqiu Cui cbao...@yahoo.com writes:

 Dale Smith da...@vxitech.com writes:

 Somthing that muse has that I'd really like to see in org is some
 way to insert raw docbook into the exported output.

 Any ideas or suggestions?  Something I've missed?

Heh.  Figured I'd miss it.

 Oh, I just noticed that #+BEGIN_LaTeX ... #+END_LaTeX already exists.
 Then maybe it is OK to add #+BEGIN_DOCBOOK ... #+END_DOCBOOK.

 This is already in org-exp.el and should work:

 #+DOCBOOK: dockbookcode

 and

 #+BEGIN_DOCBOOK
 docbookcode
 docbookcode
 docbookcode
 #+END_DOCBOOK

 Also I have just pushed changes to org-mtags.el (contributed package).
 If you load it, muse-like tags will be understood by Org as well,
 and you can write:

 literal style=docbook dockbookcode /literal

Both look good.

Thanks,
  -Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: DocBook exporter code (version 1.0)

2009-03-12 Thread Dale Smith
Baoqiu Cui cbao...@yahoo.com writes:

 I just posted the code for DocBook exporter to Google Code.

I've been enjoying this docbook exporter for sveral days now. Thanks
Baoqiu!

Somthing that muse has that I'd really like to see in org is some way
to insert raw docbook into the exported output.  The LaTeX exporter
already has a feature like this.  Muse-mode uses the literal tag.

In the past, I've used this for inserting a programming instruction
that cauaes a page-break.  I'm sure there could be many many uses.

Any ideas or suggestions?  Something I've missed?

Thanks!
  -Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: DocBook exporter for Org-mode

2009-03-05 Thread Dale Smith
Sebastian Rose sebastian_r...@gmx.de writes:

 Gour g...@mail.inet.hr writes:
 Otoh, number of tags in DocBook is overwhelming and, imgo, way too
 distracting for most documentation tasks, at least, for *my* use-cases.


 It is, and that's exactly why the DocBook export is such a great thing. 

 You could say a similar thing about (valid) XHTML, LaTeX, reST -
 whatever markup you're not familiar with.

 With the DocBook exporter, learning DocBook is reduced to pressing `C-c
 C-e' and choose the right option ;-)

And that's one of the reasons I would like a docbook exporter.

I see myself with two usage patterns.  One is where I keep the file in
org (or muse) format, and export to docbook and eventually pdf for
external consumption.  The other is where I use org (or muse) to
start the docbook file, and then continue to edit the docbook.  This
is because docbook is so much richer than any wiki format, and I want
to take advantage of what's there.

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: DocBook exporter for Org-mode

2009-03-03 Thread Dale Smith
Baoqiu Cui cbao...@yahoo.com writes:

 The only thing that is missing (at least to me) in current Org-mode is
 the exporter for DocBook format.

There is quite a bit of similarity between org and muse formats.  I've
found that I can edit .muse files in org-mode and stiil publish to
docbook.


 During the last week (mainly during the last weekend), I wrote some code
 to export Org files to DocBook V5.0 format, and everything looks very
 promising (I have to admit that a lot of work still needs to be done to
 make the code complete and stable) .

Looks pretty good to me.  I'm ready to ty it out!

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: DocBook exporter for Org-mode

2009-03-03 Thread Dale Smith
Sebastian Rose sebastian_r...@gmx.de writes:

 The LaTeX and XHTML export (which, by the
 way, could be transformed just as good as docbook) work and are widely
 used.

I'm not sure sure.  I think docbook is much more content oriented than
LaTeX and xhtml, which seem to be more presentation oriented.  To
me anyway.

-Dale

-- 
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

The information in this e-mail and any attachments is intended solely
for use by the recipient(s) to whom this e-mail is addressed and may
contain confidential and/or privileged information which is exempt
from disclosure.  If you are not an intended recipient, or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that you have received this e-mail
and any attachments in error and that dissemination, distribution,
review or copying of this e-mail and its attachments is strictly
prohibited.  If you have received this e-mail in error, please notify
the sender immediately and delete all electronic and paper copies of
this e-mail as well as any attachments.
Thank you.

http://www.vtiinstruments.com/images/vtiemaillogo.gif


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: C-a and C-e in org-mode

2009-02-03 Thread Dale Smith
Ken Harris kengru...@gmail.com writes:

 On my keyboard layout, I can hit all of C-u, C-a, C-e, C-p,
 C-k, and C-y with my left hand, so I can a whole lot of simple
 navigation editing without putting down the mouse (or mousing back
 over to my emacs window).

Wow.  Big hands!

-Dlae
-- 
Dale P. Smith
da...@vxitech.com
216-447-4059 x2018
216-447-8951 FAX



___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] icalendar importing

2009-01-30 Thread Dale Smith
Howdy list,

My company recently moved to an exchange server (ugh!) and so now i've
been getting icalendar meeting requests.  I have
icalendar-import-buffer in my gnus-article-prepare-hook, and that
works well enough to add things to my diary.  Diary entries show up im
my appointemts, so that's good, but I'd like to add them to an org
file instead.  Is there anything similar to icalendar-import-buffer
but creates a task in org format insteat of diary format?

Thanks!
  -Dale
-- 
Dale P. Smith
da...@vxitech.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

This email is covered by the Electronic Communications Privacy Act, 18
U.S.C. 2510-2521.

This information is confidential and is intended only for the use of
the individual or entity named above. If the reader of this message is
not the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this communication is
strictly prohibited.

If you have received this communication in error, please notify the
sender by reply transmission and delete the message without copying or
disclosing it.

Thank you.



___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: icalendar importing

2009-01-30 Thread Dale Smith
David Thole dth...@gmail.com writes:

 I'd be interested in finding this out as well.  Could you provide details
 Dale on how you got it to import correctly into Diary even?  There's a
 huge disconnect right now for me between my calendar and what I do my GTD
 stuff in.

Sure.  I have

  (add-hook 'gnus-article-prepare-hook 'icalendar-import-buffer)

in my ~/.emacs file.  Read the comments at the top of icalendar.el .

You might need something like

  (autoload 'icalendar-import-buffer icalendar
Import iCalendar data from current buffer t)

too.

HTH,
  -Dale



-- 
Dale P. Smith
da...@vxitech.com
216-447-4059 x2018
216-447-8951 FAX

(Company mandated disclaimer follows...)

This email is covered by the Electronic Communications Privacy Act, 18
U.S.C. 2510-2521.

This information is confidential and is intended only for the use of
the individual or entity named above. If the reader of this message is
not the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this communication is
strictly prohibited.

If you have received this communication in error, please notify the
sender by reply transmission and delete the message without copying or
disclosing it.

Thank you.


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: Feature request: Highlight the agenda line with the cursor on it

2008-08-13 Thread Dale Smith
Rob Weir [EMAIL PROTECTED] writes:

 On 13 Aug 2008, Robert Miesen wrote:
 I've noticed that as I go through tasks listed in my agenda, it's
 very easy to select and operate on the wrong task because it's too
 easy to loose track of what task I am operating on. If the entire task
 line entry were highlighted, it would be much easier to determine
 which task was being operated on.

 Not built-in, but:

 ,
 | (add-hook 'org-agenda-mode-hook '(lambda () (hl-line-mode 1)))
 `

 works quite well.

Yes!  I've been needing this and didn't even know it!

When in an aganda buffer, the cursor is usually way over on the left
side.  To help me focus my eyes on the task/tags/etc, I (without
thinking) lean on my right key to move the cursor over.  What this
actually does is move forward by about 10 weeks or so. :(

-Dale

-- 
Dale P. Smith
[EMAIL PROTECTED]
216-447-4059
216-447-8951 FAX

(Company mandated disclaimer follows...)

This email is covered by the Electronic Communications Privacy Act, 18
U.S.C. 2510-2521.

This information is confidential and is intended only for the use of
the individual or entity named above. If the reader of this message is
not the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this communication is
strictly prohibited.

If you have received this communication in error, please notify the
sender by reply transmission and delete the message without copying or
disclosing it.

Thank you.


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: Linux Journal

2007-11-08 Thread Dale Smith
Bastien [EMAIL PROTECTED] writes:

 Dale Smith [EMAIL PROTECTED] writes:

 I just noticed there is an article on org-mode in the December Linux
 Journal by Abhijeet Chavan.

 Great.  Any chance that people in this list could read it *somewhere*,
 even if not Linux Journal subscribers?

I'm not sure.  There is this link, but you need to be a registered
print or digital subscriber: http://www.linuxjournal.com/article/9116

-Dale

-- 
Dale P. Smith
[EMAIL PROTECTED]
216-447-4059
216-447-8951 FAX

(Company mandated disclaimer follows...)

This email is covered by the Electronic Communications Privacy Act, 18
U.S.C. 2510-2521.

This information is confidential and is intended only for the use of
the individual or entity named above. If the reader of this message is
not the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this communication is
strictly prohibited.

If you have received this communication in error, please notify the
sender by reply transmission and delete the message without copying or
disclosing it.

Thank you.


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Linux Journal

2007-11-07 Thread Dale Smith
I didn't see this here yet.  Sorry if I'm being redundant. (again?)

I just noticed there is an article on org-mode in the December Linux
Journal by Abhijeet Chavan.

Yaayy.  Nice job, Abhijeet.

-Dale

-- 
Dale P. Smith
[EMAIL PROTECTED]
216-447-4059
216-447-8951 FAX



___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: Org-mode version 5.01

2007-07-03 Thread Dale Smith
Carsten Dominik [EMAIL PROTECTED] writes:

 I am releasing Org-mode 5.01.  It is available at my website

 http://www.astro.uva.nl/~dominik/Tools/org

 and also through Emacs CVS.

 I am pretty excited about this release, a new major version.

Wow!  What a lot of new functionality.  I can hardly wait to start
making good use of all this.

Thanks (again!) for the very fine work you do on org-mode, it has
brought some sanity to my (and many others) life.

-Dale

-- 
Dale P. Smith
[EMAIL PROTECTED]
216-447-4059
216-447-8951 FAX


___
Emacs-orgmode mailing list
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: Customizable link types

2006-09-25 Thread Dale Smith
Carsten Dominik [EMAIL PROTECTED] writes:

 I am not using planner.el, so I can only guess how this feature is
 supposed to work.  Would you care to expand?

Sure.  I'm acually abusing interwiki links.  In my planner files, I
can quicky use Bugzilla::1234 as a link to bug number 1234.  Planner
sees that as an interwiki link (the ::) .  Pressing return over the
link while in planner or following the link in the published html
actually goes to http://10.1.2.9/bugzilla/show_bug.cgi?id=1234

I *could* use something like
[[http://10.1.2.9/bugzilla/show_bug.cgi?id=1234][Bug# 1234]], but
that's a lot to type in.  Hmm.  It wouldn't be too hard to whip up
some elist that generates a link like that.

What I'm really asking is a way to extend the current list of link
types (gnus:, file:, vm:, etc.) with some user-defined types.


 On Sep 22, 2006, at 23:57, Dale Smith wrote:

 I've been trying out org-mode instead of planner-el for a few weeks
 now.  I like it.  However, there are a few things I miss.  One is
 how easy it was to ad my own hyperlink types.  This was all I
 needed to add Bugzilla::number links:

 (setq muse-wiki-interwiki-alist
   '((Bugzilla . http://10.1.2.9/bugzilla/show_bug.cgi?id=;)))

-Dale

-- 
Dale P. Smith
[EMAIL PROTECTED]
216-447-4059
216-447-8951 FAX



___
Emacs-orgmode mailing list
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode