[Orgmode] Problem exporting table with images
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
#+TITLE: Export of images in table to pdf
#+AUTHOR:Rainer M. Krug
#+DATE: 2011-02-08 Tue
Hi
I have problems exporting this table with graphs to pdf:
1) when exporting, the links are retained, and okular tells me
"malformed url"
2) I would like to have the graphs inserted instead of the links ---
according to the manual, this should be done automatically, but it does
not work.
Is there something I am missing here?
Cheers,
Rainer
* Generating the graphs
#+begin_src R :results output org :exports both
cat("|---|---|---|\n")
for (x in 1:3) {
for (y in 1:3) {
pdf(paste("img", x, y, "pdf", sep="."))
plot(runif(100))
dev.off()
}
cat("|", paste(" [[file:img.1", x, "pdf", sep="."), "]] |",
paste(" [[./img.2", x, "pdf", sep="."), "]] |", paste("[[./img.3", x,
"pdf", sep="."), "]] |\n")
}
cat("|---|---|---|\n")
#+end_src
#+results:
#+BEGIN_ORG
|---++|
| [[file:img.1.1.pdf ]] | [[./img.2.1.pdf ]] | [[./img.3.1.pdf ]] |
| [[file:img.1.2.pdf ]] | [[./img.2.2.pdf ]] | [[./img.3.2.pdf ]] |
| [[file:img.1.3.pdf ]] | [[./img.2.3.pdf ]] | [[./img.3.3.pdf ]] |
|---++|
#+END_ORG
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa
Tel:+33 - (0)9 53 10 27 44
Cell: +27 - (0)8 39 47 90 42
Fax (SA): +27 - (0)8 65 16 27 82
Fax (D) : +49 - (0)3 21 21 25 22 44
Fax (FR): +33 - (0)9 58 10 27 44
email: rai...@krugs.de
Skype: RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1RJtAACgkQoYgNqgF2egrBaACfQiORHUc3itvK3rXv9Z2JtFlm
F2cAnigBCCqt2XoUpGe0iGkyF1VRIwYj
=YifL
-END PGP SIGNATURE-
___
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
[Orgmode] allout-mode + Babel
Discovered allout-mode today. It permits outline navigation in code buffers. I am surprised to see that some of the stuff within org-mode itself is inspired by the allout library. If Babel could tangle so that the output file is allout navigable that would be interesting. This has never before surfaced in the mailing list. So here I go ... http://www.emacswiki.org/emacs/AllOut Jambunathan K. ___ 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
[Orgmode] Re: [ANN] Changes to lists
Nicolas, Nicolas Goaziou gmail.com> writes: > > 2. Lists in inline tasks are not exported properly (item 2a in the > > example below). > > This should be fixed now. Thanks. This does not work for me. Lists in inline tasks are still exported as follows: * item 1 * item 2 What do I miss? Regards, Karl ___ 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
[Orgmode] Problems with source code listings in PDF
I'm working on creating a PDF eBook with Org-Mode, and I'm running into some difficulty getting them to come out looking decent. I've followed the directions I found in the list archives for outputting colorized source code listings. I set org-export-latex-listings to t, and customized org-export-latex-packages-alist according to the directions in the org-export-latex-listings docs. I'm seeing a few problems with the output: 1. There is no color; only bolded keywords. 2. Listings are formatted in a not-very-well-rendered font with serifs that just doesn't look good at all. 3. In begin_example sections, spaces are replaced with odd little curved underscores. I've attached some examples to show what I mean. I'm running Org-Mode 7.4 on Ubuntu 10.10 with Emacs 23.1.50.1. Has anyone had any luck formatting source code and example listings in PDF output? What I'd really like to get is output identical to the listings exported to HTML. Thanks! -- Avdi Grimm <><>___ 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] Problems with source code listings in PDF
Avdi Grimm writes:
> I'm working on creating a PDF eBook with Org-Mode, and I'm running
> into some difficulty getting them to come out looking decent.
>
> I've followed the directions I found in the list archives for
> outputting colorized source code listings. I set
> org-export-latex-listings to t, and customized
> org-export-latex-packages-alist according to the directions in the
> org-export-latex-listings docs.
>
> I'm seeing a few problems with the output:
> 1. There is no color; only bolded keywords.
I must admit that colour has never been something I've considered...
it is, however, an option for the listings package.
> 2. Listings are formatted in a not-very-well-rendered font with serifs
> that just doesn't look good at all.
I've had no problems with typeface etc for listings in the past.
> 3. In begin_example sections, spaces are replaced with odd little
> curved underscores.
The use of curved underscores for spaces is deliberate and whether this
is done will depend on your source language. You can customise this in
any case (see below).
In summary, you may need to add a line customising the listings
package. Check out the user manual at
: ftp://ftp.tex.ac.uk/tex-archive/macros/latex/contrib/listings/listings.pdf
and then have something like this in your org file near the top:
#+latex_header: \lstset{showspaces=false, ...}
(replacing ... with the other options you may wish).
HTH.
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.4 (release_7.4.319.g88b7.dirty)
___
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
[Orgmode] Multiple var definitions in :PROPERTIES: block?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi assuming the following: * Test case with two var definitions in :PROPERTIES: drawer: :PROPERTIES: :tangle: var.sh :var: FIRST="test13" :var: SECOND="test14" :END: #+begin_src sh echo $FIRST echo $SECOND #+end_src #+results: : test13 Only the first one is defined and exported into the code. How can I define the second one, so that it is also exported in the code and in the tangled as well as executed code? Thanks, Rainer - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Natural Sciences Building Office Suite 2039 Stellenbosch University Main Campus, Merriman Avenue Stellenbosch South Africa Tel:+33 - (0)9 53 10 27 44 Cell: +27 - (0)8 39 47 90 42 Fax (SA): +27 - (0)8 65 16 27 82 Fax (D) : +49 - (0)3 21 21 25 22 44 Fax (FR): +33 - (0)9 58 10 27 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1RX6EACgkQoYgNqgF2egoi9gCgh2Z0qBw8Z8sglJTMiVMMx7B5 QkoAmgIbc5y1d3K/xoae1Iaj/NEC31DB =kcL3 -END PGP SIGNATURE- ___ 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] Problems with source code listings in PDF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/08/2011 03:59 PM, Avdi Grimm wrote:
> I'm working on creating a PDF eBook with Org-Mode, and I'm running
> into some difficulty getting them to come out looking decent.
>
> I've followed the directions I found in the list archives for
> outputting colorized source code listings. I set
> org-export-latex-listings to t, and customized
> org-export-latex-packages-alist according to the directions in the
> org-export-latex-listings docs.
>
> I'm seeing a few problems with the output:
>
> 1. There is no color; only bolded keywords.
add these definitions to the headers of the org file - they should
provide colour and a list of other things you can customize - these are
not from me, I think they are from this list or from worg.
Cheers,
Rainer
#+LATEX_HEADER: \definecolor{light-gray}{gray}{0.9}
#+LATEX_HEADER: \lstset{%
#+LATEX_HEADER: basicstyle=\ttfamily\tiny, % the font that is
used for the code
#+LATEX_HEADER: tabsize=4, % sets default
tabsize to 4 spaces
#+LATEX_HEADER: numbers=left,% where to put the
line numbers
#+LATEX_HEADER: numberstyle=\tiny, % line number font size
#+LATEX_HEADER: stepnumber=0,% step between two
line numbers
#+LATEX_HEADER: breaklines=true, %!! don't break
long lines of code
#+LATEX_HEADER: showtabs=false, % show tabs within
strings adding particular underscores
#+LATEX_HEADER: showspaces=false,% show spaces
adding particular underscores
#+LATEX_HEADER: showstringspaces=false, % underline spaces
within strings
#+LATEX_HEADER: keywordstyle=\color{blue},
#+LATEX_HEADER: identifierstyle=\color{black},
#+LATEX_HEADER: stringstyle=\color{green},
#+LATEX_HEADER: commentstyle=\color{red},
#+LATEX_HEADER: backgroundcolor=\color{light-gray}, % sets the
background color
#+LATEX_HEADER: columns=fullflexible,
#+LATEX_HEADER: basewidth={0.5em,0.4em},
#+LATEX_HEADER: captionpos=b,% sets the caption
position to `bottom'
#+LATEX_HEADER: extendedchars=false %!?? workaround for
when the listed file is in UTF-8
#+LATEX_HEADER: }
> 2. Listings are formatted in a not-very-well-rendered font with serifs
> that just doesn't look good at all.
> 3. In begin_example sections, spaces are replaced with odd little
> curved underscores.
>
> I've attached some examples to show what I mean.
>
> I'm running Org-Mode 7.4 on Ubuntu 10.10 with Emacs 23.1.50.1.
>
> Has anyone had any luck formatting source code and example listings in
> PDF output? What I'd really like to get is output identical to the
> listings exported to HTML.
>
> Thanks!
>
> --
> Avdi Grimm
>
>
>
> ___
> 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
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa
Tel:+33 - (0)9 53 10 27 44
Cell: +27 - (0)8 39 47 90 42
Fax (SA): +27 - (0)8 65 16 27 82
Fax (D) : +49 - (0)3 21 21 25 22 44
Fax (FR): +33 - (0)9 58 10 27 44
email: rai...@krugs.de
Skype: RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1RYE4ACgkQoYgNqgF2egqzHQCfVFZ9nQP5l1cEsCaFpzRyR2vv
o9MAnArHaXN8pPEDoZE4ATdt/6OgN2Wq
=xwFH
-END PGP SIGNATURE-
___
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] Call org-map-entries just on children?
Hi Richard, Richard Lawrence writes: > I want to call org-map-entries in a way that calls a function at each > *child* of the current tree, but not at the current tree itself. That > is, for some function f, if my Org file looks like this: > > * Paper 1 > ** Student 1 > ** Student 2 > ... > > I want to call f at "Student 1", "Student 2", etc. but not at "Paper 1". > But if point is positioned at "Paper 1", then > > (org-map-entries 'f nil 'tree) > > first calls f at the "Paper 1" entry, not the "Student 1" entry. How > can I apply f just to the *children* of "Paper 1"? You can simply add (setq org-map-continue-from (outline-next-heading)) at the very beginning of your `f' function. HTH, -- Bastien ___ 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] IMPORTANT: let's make the biggest gift of FLOSS history!
Jeff Horn writes: > Great! Looks like I was the first. Consider yourself flattr'd. I do, thanks a lot! -- Bastien ___ 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
[Orgmode] Re: org-mhe-store-link alters window layout
Looks good to me, thank you for bringing this up. Carsten, could you please check the patch in? Thanks again Thomas Stephen Eglen writes: > If I run M-x org-store-link when my current emacs frame is just showing > one MH-E window (and nothing else in the frame), e.g. the "show-+inbox" > buffer, then the link to that email is created okay, but the window > frames are altered so that the +inbox summary window is also shown. > In general, the previous window contents are forgotten. I suggest > adding a 'save-window-excursion' into org-mhe-store-link so that the > window arrangement is preserved on exit from the function. > > Patch below is long just because of the extra indentation. > > Stephen > > diff --git a/lisp/org-mhe.el b/lisp/org-mhe.el > index c384062..c9b0481 100644 > --- a/lisp/org-mhe.el > +++ b/lisp/org-mhe.el > @@ -83,27 +83,28 @@ supported by MH-E." >"Store a link to an MH-E folder or message." >(when (or (equal major-mode 'mh-folder-mode) > (equal major-mode 'mh-show-mode)) > -(let* ((from (org-mhe-get-header "From:")) > -(to (org-mhe-get-header "To:")) > -(message-id (org-mhe-get-header "Message-Id:")) > -(subject (org-mhe-get-header "Subject:")) > -(date (org-mhe-get-header "Date:")) > -(date-ts (and date (format-time-string > -(org-time-stamp-format t) (date-to-time date > -(date-ts-ia (and date (format-time-string > - (org-time-stamp-format t t) > - (date-to-time date > -link desc) > - (org-store-link-props :type "mh" :from from :to to > - :subject subject :message-id message-id) > - (when date > - (org-add-link-props :date date :date-timestamp date-ts > - :date-timestamp-inactive date-ts-ia)) > - (setq desc (org-email-link-description)) > - (setq link (org-make-link "mhe:" (org-mhe-get-message-real-folder) "#" > - (org-remove-angle-brackets message-id))) > - (org-add-link-props :link link :description desc) > - link))) > +(save-window-excursion > + (let* ((from (org-mhe-get-header "From:")) > + (to (org-mhe-get-header "To:")) > + (message-id (org-mhe-get-header "Message-Id:")) > + (subject (org-mhe-get-header "Subject:")) > + (date (org-mhe-get-header "Date:")) > + (date-ts (and date (format-time-string > + (org-time-stamp-format t) (date-to-time > date > + (date-ts-ia (and date (format-time-string > + (org-time-stamp-format t t) > + (date-to-time date > + link desc) > + (org-store-link-props :type "mh" :from from :to to > + :subject subject :message-id message-id) > + (when date > + (org-add-link-props :date date :date-timestamp date-ts > + :date-timestamp-inactive date-ts-ia)) > + (setq desc (org-email-link-description)) > + (setq link (org-make-link "mhe:" (org-mhe-get-message-real-folder) "#" > + (org-remove-angle-brackets message-id))) > + (org-add-link-props :link link :description desc) > + link > > (defun org-mhe-open (path) >"Follow an MH-E message link specified by PATH." > > > > ___ > 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 ___ 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] Problems with source code listings in PDF
On Feb 8, 2011, at 4:59 AM, Avdi Grimm wrote: I'm working on creating a PDF eBook with Org-Mode, and I'm running into some difficulty getting them to come out looking decent. I've followed the directions I found in the list archives for outputting colorized source code listings. I set org-export-latex-listings to t, and customized org-export-latex-packages-alist according to the directions in the org-export-latex-listings docs. I'm seeing a few problems with the output: 1. There is no color; only bolded keywords 2. Listings are formatted in a not-very-well-rendered font with serifs that just doesn't look good at all. Instructions for setting up different fonts can be found here: http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-14 Note that some of the fonts clash with the amssymb LaTeX package, which Org-mode loads by default. You'll want to choose a font that doesn't clash, or configure Org-mode so the amssymb package isn't loaded. All the best, Tom 3. In begin_example sections, spaces are replaced with odd little curved underscores. I've attached some examples to show what I mean. I'm running Org-Mode 7.4 on Ubuntu 10.10 with Emacs 23.1.50.1. Has anyone had any luck formatting source code and example listings in PDF output? What I'd really like to get is output identical to the listings exported to HTML. Thanks! -- Avdi Grimm < example .png>___ 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 ___ 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
[Accepted] [Orgmode] org-mhe-store-link alters window layout
Patch 584 (http://patchwork.newartisans.com/patch/584/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C1337.1297074568%40maps%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [Orgmode] org-mhe-store-link alters window layout > Date: Mon, 07 Feb 2011 15:29:28 - > From: Stephen Eglen > X-Patchwork-Id: 584 > Message-Id: <1337.1297074568@maps> > To: emacs-orgmode@gnu.org > Cc: thomas.baum...@ch.tum.de, Stephen Eglen > > If I run M-x org-store-link when my current emacs frame is just showing > one MH-E window (and nothing else in the frame), e.g. the "show-+inbox" > buffer, then the link to that email is created okay, but the window > frames are altered so that the +inbox summary window is also shown. > In general, the previous window contents are forgotten. I suggest > adding a 'save-window-excursion' into org-mhe-store-link so that the > window arrangement is preserved on exit from the function. > > Patch below is long just because of the extra indentation. > > Stephen > > > diff --git a/lisp/org-mhe.el b/lisp/org-mhe.el > index c384062..c9b0481 100644 > --- a/lisp/org-mhe.el > +++ b/lisp/org-mhe.el > @@ -83,27 +83,28 @@ supported by MH-E." >"Store a link to an MH-E folder or message." >(when (or (equal major-mode 'mh-folder-mode) > (equal major-mode 'mh-show-mode)) > -(let* ((from (org-mhe-get-header "From:")) > -(to (org-mhe-get-header "To:")) > -(message-id (org-mhe-get-header "Message-Id:")) > -(subject (org-mhe-get-header "Subject:")) > -(date (org-mhe-get-header "Date:")) > -(date-ts (and date (format-time-string > -(org-time-stamp-format t) (date-to-time date > -(date-ts-ia (and date (format-time-string > - (org-time-stamp-format t t) > - (date-to-time date > -link desc) > - (org-store-link-props :type "mh" :from from :to to > - :subject subject :message-id message-id) > - (when date > - (org-add-link-props :date date :date-timestamp date-ts > - :date-timestamp-inactive date-ts-ia)) > - (setq desc (org-email-link-description)) > - (setq link (org-make-link "mhe:" (org-mhe-get-message-real-folder) "#" > - (org-remove-angle-brackets message-id))) > - (org-add-link-props :link link :description desc) > - link))) > +(save-window-excursion > + (let* ((from (org-mhe-get-header "From:")) > + (to (org-mhe-get-header "To:")) > + (message-id (org-mhe-get-header "Message-Id:")) > + (subject (org-mhe-get-header "Subject:")) > + (date (org-mhe-get-header "Date:")) > + (date-ts (and date (format-time-string > + (org-time-stamp-format t) (date-to-time > date > + (date-ts-ia (and date (format-time-string > + (org-time-stamp-format t t) > + (date-to-time date > + link desc) > + (org-store-link-props :type "mh" :from from :to to > + :subject subject :message-id message-id) > + (when date > + (org-add-link-props :date date :date-timestamp date-ts > + :date-timestamp-inactive date-ts-ia)) > + (setq desc (org-email-link-description)) > + (setq link (org-make-link "mhe:" (org-mhe-get-message-real-folder) "#" > + (org-remove-angle-brackets message-id))) > + (org-add-link-props :link link :description desc) > + link > > (defun org-mhe-open (path) >"Follow an MH-E message link specified by PATH." > ___ 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: org-mhe-store-link alters window layout
Thomas Baumann writes: > Looks good to me, thank you for bringing this up. > > Carsten, could you please check the patch in? I applied this patch, thanks for double-checking it! -- Bastien ___ 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
[Accepted] [Orgmode] org-crypt: cache encrypted text
Patch 586 (http://patchwork.newartisans.com/patch/586/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C1297102717-5071-1-git-send-email-julien%40danjou.info%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [Orgmode] org-crypt: cache encrypted text > Date: Mon, 07 Feb 2011 23:18:37 - > From: Julien Danjou > X-Patchwork-Id: 586 > Message-Id: <1297102717-5071-1-git-send-email-jul...@danjou.info> > To: emacs-orgmode@gnu.org > Cc: Julien Danjou > > * lisp/org-crypt.el (org-encrypt-string): New function. > (org-encrypt-entry): Use org-encrypt-string to encrypt, so we use cached > crypted values. > (org-decrypt-entry): Store crypted text in decrypted text. > > Signed-off-by: Julien Danjou > > --- > lisp/org-crypt.el | 26 -- > 1 files changed, 20 insertions(+), 6 deletions(-) > > diff --git a/lisp/org-crypt.el b/lisp/org-crypt.el > index 7c28d70..291c540 100644 > --- a/lisp/org-crypt.el > +++ b/lisp/org-crypt.el > @@ -103,6 +103,15 @@ This setting can also be overridden in the CRYPTKEY > property." > (and (boundp 'epa-file-encrypt-to) epa-file-encrypt-to) > (message "No crypt key set, using symmetric encryption." > > +(defun org-encrypt-string (str crypt-key) > + "Return STR encrypted with CRYPT-KEY." > + ;; Text and key have to be identical, otherwise we re-crypt. > + (if (and (string= crypt-key (get-text-property 0 'org-crypt-key str)) > +(string= (sha1 str) (get-text-property 0 'org-crypt-checksum str))) > + (get-text-property 0 'org-crypt-text str) > +(let ((epg-context (epg-make-context nil t t))) > + (epg-encrypt-string epg-context str (epg-list-keys epg-context > crypt-key) > + > (defun org-encrypt-entry () >"Encrypt the content of the current headline." >(interactive) > @@ -122,10 +131,7 @@ This setting can also be overridden in the CRYPTKEY > property." >(org-back-over-empty-lines) >(setq end (point) > encrypted-text > -(epg-encrypt-string > - epg-context > - (buffer-substring-no-properties beg end) > - (epg-list-keys epg-context crypt-key))) > + (org-encrypt-string (buffer-substring beg end) crypt-key)) >(delete-region beg end) >(insert encrypted-text) >(when folded > @@ -152,16 +158,24 @@ This setting can also be overridden in the CRYPTKEY > property." > (forward-line) > (point))) >(epg-context (epg-make-context nil t t)) > + (encrypted-text (buffer-substring-no-properties (point) end)) >(decrypted-text > (decode-coding-string > (epg-decrypt-string > epg-context > - (buffer-substring-no-properties (point) end)) > + encrypted-text) > 'utf-8))) > ;; Delete region starting just before point, because the > ;; outline property starts at the \n of the heading. > (delete-region (1- (point)) end) > - (insert "\n" decrypted-text) > + ;; Store a checksum of the decrypted and the encrypted > + ;; text value. This allow to reuse the same encrypted text > + ;; if the text does not change, and therefore avoid a > + ;; re-encryption process. > + (insert "\n" (propertize decrypted-text > + 'org-crypt-checksum (sha1 decrypted-text) > + 'org-crypt-key (org-crypt-key-for-heading) > + 'org-crypt-text encrypted-text)) > (when heading-was-invisible-p > (goto-char heading-point) > (org-flag-subtree t)) > ___ 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
[Accepted] [Orgmode] org-bbdb: allow anniversaries with unknown years
Patch 585 (http://patchwork.newartisans.com/patch/585/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C1297078995-9030-1-git-send-email-cwg%40falma.de%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [Orgmode] org-bbdb: allow anniversaries with unknown years
> Date: Mon, 07 Feb 2011 16:43:15 -
> From: Christoph Groth
> X-Patchwork-Id: 585
> Message-Id: <1297078995-9030-1-git-send-email-...@falma.de>
> To: emacs-orgmode@gnu.org
> Cc: Christoph Groth
>
> Anniversaries in BBDB can be now also specified in the format MM-DD
> next to -MM-DD.
>
> ---
> doc/org.texi | 11 ++-
> lisp/org-bbdb.el | 27 ++-
> 2 files changed, 24 insertions(+), 14 deletions(-)
>
> diff --git a/doc/org.texi b/doc/org.texi
> index b406d29..bfcef06 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -7098,14 +7098,15 @@ following to one your your agenda files:
>
> You can then go ahead and define anniversaries for a BBDB record. Basically,
> you need to press @kbd{C-o anniversary @key{RET}} with the cursor in a BBDB
> -record and then add the date in the format @code{-MM-DD}, followed by a
> -space and the class of the anniversary (@samp{birthday} or @samp{wedding}, or
> -a format string). If you omit the class, it will default to @samp{birthday}.
> -Here are a few examples, the header for the file @file{org-bbdb.el} contains
> -more detailed information.
> +record and then add the date in the format @code{-MM-DD} or @code{MM-DD},
> +followed by a space and the class of the anniversary (@samp{birthday} or
> +@samp{wedding}, or a format string). If you omit the class, it will default
> to
> +@samp{birthday}. Here are a few examples, the header for the file
> +@file{org-bbdb.el} contains more detailed information.
>
> @example
> 1973-06-22
> +06-22
> 1955-08-02 wedding
> 2008-04-14 %s released version 6.01 of org-mode, %d years ago
> @end example
> diff --git a/lisp/org-bbdb.el b/lisp/org-bbdb.el
> index 4155f58..c04b7ff 100644
> --- a/lisp/org-bbdb.el
> +++ b/lisp/org-bbdb.el
> @@ -136,12 +136,12 @@
>'(("birthday" lambda
> (name years suffix)
> (concat "Birthday: [[bbdb:" name "][" name " ("
> - (number-to-string years)
> + (format "%s" years); handles numbers as well as strings
>suffix ")]]"))
> ("wedding" lambda
> (name years suffix)
> (concat "[[bbdb:" name "][" name "'s "
> - (number-to-string years)
> + (format "%s" years)
>suffix " wedding anniversary]]")))
>"How different types of anniversaries should be formatted.
> An alist of elements (STRING . FORMAT) where STRING is the name of an
> @@ -239,11 +239,16 @@ italicized, in all other cases it is left unchanged."
>
> (defun org-bbdb-anniv-extract-date (time-str)
>"Convert -MM-DD to (month date year).
> -Argument TIME-STR is the value retrieved from BBDB."
> - (multiple-value-bind (y m d) (values-list (bbdb-split time-str "-"))
> -(list (string-to-number m)
> - (string-to-number d)
> - (string-to-number y
> +Argument TIME-STR is the value retrieved from BBDB. If - is omitted
> +it will be considered unknown."
> + (multiple-value-bind (a b c) (values-list (bbdb-split time-str "-"))
> +(if (eq c nil)
> +(list (string-to-number a)
> + (string-to-number b)
> + nil)
> + (list (string-to-number b)
> +(string-to-number c)
> +(string-to-number a)
>
> (defun org-bbdb-anniv-split (str)
>"Split multiple entries in the BBDB anniversary field.
> @@ -326,8 +331,12 @@ This is used by Org to re-create the anniversary hash
> table."
>class org-bbdb-anniversary-format-alist t))
> class)) ; (as format string)
> (name (nth 1 rec))
> - (years (- y (car rec)))
> - (suffix (diary-ordinal-suffix years))
> + (years (if (eq (car rec) nil)
> +"unknown"
> + (- y (car rec
> + (suffix (if (eq (car rec) nil)
> + ""
> + (diary-ordinal-suffix years)))
> (tmp (cond
> ((functionp form)
> (funcall form name years suffix))
>
___
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] [PATCH] org-bbdb: allow anniversaries with unknown years
Christoph Groth writes: > Anniversaries in BBDB can be now also specified in the format MM-DD > next to -MM-DD. I've now applied this patch, thanks for it! -- Bastien ___ 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] Store link in message mode
Hi Ulf, Ulf Stegemann writes: > If you think --despite of those issues-- it's worth adding the creation > of gnus links while in message mode I could provide a patch. FWIW, I think it would be useful. > I'd probably add the functionality to `org-gnus-store-link' but I'm > not an org code expert and a different location may be more > appropriate. What do you think? Such a change belongs to `org-gnus-store-link' -- I'd be glad to apply a patch to this effect. Thanks! -- Bastien ___ 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
[Orgmode] Re: [PATCH] org-bbdb: allow anniversaries with unknown years
Christoph Groth writes:
> Anniversaries in BBDB can be now also specified in the format MM-DD
> next to -MM-DD.
> ---
> doc/org.texi | 11 ++-
> lisp/org-bbdb.el | 27 ++-
> 2 files changed, 24 insertions(+), 14 deletions(-)
>
> diff --git a/doc/org.texi b/doc/org.texi
> index b406d29..bfcef06 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -7098,14 +7098,15 @@ following to one your your agenda files:
>
> You can then go ahead and define anniversaries for a BBDB record. Basically,
> you need to press @kbd{C-o anniversary @key{RET}} with the cursor in a BBDB
> -record and then add the date in the format @code{-MM-DD}, followed by a
> -space and the class of the anniversary (@samp{birthday} or @samp{wedding}, or
> -a format string). If you omit the class, it will default to @samp{birthday}.
> -Here are a few examples, the header for the file @file{org-bbdb.el} contains
> -more detailed information.
> +record and then add the date in the format @code{-MM-DD} or @code{MM-DD},
> +followed by a space and the class of the anniversary (@samp{birthday} or
> +@samp{wedding}, or a format string). If you omit the class, it will default
> to
> +@samp{birthday}. Here are a few examples, the header for the file
> +@file{org-bbdb.el} contains more detailed information.
>
> @example
> 1973-06-22
> +06-22
> 1955-08-02 wedding
> 2008-04-14 %s released version 6.01 of org-mode, %d years ago
> @end example
> diff --git a/lisp/org-bbdb.el b/lisp/org-bbdb.el
> index 4155f58..c04b7ff 100644
> --- a/lisp/org-bbdb.el
> +++ b/lisp/org-bbdb.el
> @@ -136,12 +136,12 @@
>'(("birthday" lambda
> (name years suffix)
> (concat "Birthday: [[bbdb:" name "][" name " ("
> - (number-to-string years)
> + (format "%s" years); handles numbers as well as strings
>suffix ")]]"))
> ("wedding" lambda
> (name years suffix)
> (concat "[[bbdb:" name "][" name "'s "
> - (number-to-string years)
> + (format "%s" years)
>suffix " wedding anniversary]]")))
>"How different types of anniversaries should be formatted.
> An alist of elements (STRING . FORMAT) where STRING is the name of an
> @@ -239,11 +239,16 @@ italicized, in all other cases it is left unchanged."
>
> (defun org-bbdb-anniv-extract-date (time-str)
>"Convert -MM-DD to (month date year).
> -Argument TIME-STR is the value retrieved from BBDB."
> - (multiple-value-bind (y m d) (values-list (bbdb-split time-str "-"))
> -(list (string-to-number m)
> - (string-to-number d)
> - (string-to-number y
> +Argument TIME-STR is the value retrieved from BBDB. If - is omitted
> +it will be considered unknown."
> + (multiple-value-bind (a b c) (values-list (bbdb-split time-str "-"))
> +(if (eq c nil)
> +(list (string-to-number a)
> + (string-to-number b)
> + nil)
> + (list (string-to-number b)
> +(string-to-number c)
> +(string-to-number a)
>
> (defun org-bbdb-anniv-split (str)
>"Split multiple entries in the BBDB anniversary field.
> @@ -326,8 +331,12 @@ This is used by Org to re-create the anniversary hash
> table."
>class org-bbdb-anniversary-format-alist t))
> class)) ; (as format string)
> (name (nth 1 rec))
> - (years (- y (car rec)))
> - (suffix (diary-ordinal-suffix years))
> + (years (if (eq (car rec) nil)
> +"unknown"
> + (- y (car rec
> + (suffix (if (eq (car rec) nil)
> + ""
> + (diary-ordinal-suffix years)))
> (tmp (cond
> ((functionp form)
> (funcall form name years suffix))
Thanks for adding this feature.
Carsten, could you please check this in?
The ChangeLog should mention that any customized
"org-bbdb-anniversary-format-alist" has to be updated, otherwise there
will be an "Bad sexp at line 637 in /home/tb/org/diary.org:
(org-bbdb-anniversaries)" error with the new format.
Thomas
___
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
[Orgmode] Using latexmk for LaTeX compilation
I want to use latexmk as the LaTeX exporting engine, I following this link's (http://orgmode.org/worg/org-faq.html#using-xelatex-for-pdf-export) instruction, but it didn't work. Note, that exporting the .org to .tex file and then manually running latexmk -pdf works flawlessly. I'm very new to emacs and I can't find what is wrong here. I also posted a question here http://tex.stackexchange.com/questions/10562/emacs-org-mode-and-latexmk. You can find some more details there. Thanks a lot! Dror ___ 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
[Orgmode] Export error. Have a look at my backtrace?
Hey orgsters, Export started behaving weirdly for me earlier this week. When I export to HTML or ASCII to a temporary buffer, I get the attached backtrace. This occurs in emacs 24 (Aquamacs) with org-mode 7.4. The error does not occur if I export to file. Also, exporting to a temporary buffer works as expected in emacs 23.2 with org-mode 7.4 in terminal emacs. Error occurs with every file I have tried in the past few days. Can anyone else reproduce? I'll come up with a minimal working example if needed. Thanks for any pointers. Jeff -- Jeffrey Horn http://www.failuretorefrain.com/jeff/ html-subtree-export-backtrace Description: Binary data ___ 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
[Orgmode] Re: Using latexmk for LaTeX compilation
Dror Atariah wrote: > I want to use latexmk as the LaTeX exporting engine, I following this > link's > (http://orgmode.org/worg/org-faq.html#using-xelatex-for-pdf-export) > instruction, but it didn't work. > Note, that exporting the .org to .tex file and then manually running > latexmk -pdf works flawlessly. This setting works for me to produce pdfs via latexmk. (setq org-latex-to-pdf-process (list "latexmk -f -pdf %f")) Lawrence -- Lawrence Mitchell ___ 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
[Orgmode] [Accepted] [Orgmode,1/2] org-publish
Patch 429 (http://patchwork.newartisans.com/patch/429/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C87mxop7qp3.fsf%40univ-nantes.fr%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [Orgmode,1/2] org-publish
> Date: Wed, 01 Dec 2010 15:06:16 -
> From: Manuel Giraud
> X-Patchwork-Id: 429
> Message-Id: <87mxop7qp3@univ-nantes.fr>
> To: emacs-orgmode
>
> Hi,
>
> This first patch adds sort options to the sitemap. In addition to
> alphabetical order, one can choose chronological or anti-chronological
> ordering of sitemap entries. To retrieve file date, it tries to parse
> the "#+date" keyword and if not present defaults to file modification
> time.
>
>
> diff --git a/doc/org.texi b/doc/org.texi
> index 4e8eb63..c283503 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -10859,9 +10859,13 @@ of links to all files in the project.
> (default) or @code{last} to display folders first or last,
> respectively. Any other value will mix files and folders.
>
> -@item @code{:sitemap-alphabetically}
> -@tab The site map is normally sorted alphabetically. Set this explicitly to
> -@code{nil} to turn off sorting.
> +@item @code{:sitemap-sort-files}
> +@tab How the files are sorted in the site map. Set this
> +@code{alphabetically} (default), @code{chronologically} or
> +@code{anti-chronologically}. @code{chronologically} sorts the files with
> +older date first while @code{anti-chronologically} sorts the files with newer
> +date first. @code{alphabetically} sorts the files alphabetically. The date of
> +a file is retrieved with @code{org-publish-find-date}.
>
> @item @code{:sitemap-ignore-case}
> @tab Should sorting be case-sensitive? Default @code{nil}.
> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
> index c66cd29..edc0b5c 100644
> --- a/lisp/org-publish.el
> +++ b/lisp/org-publish.el
> @@ -186,8 +186,9 @@ sitemap of files or summary page for a given project.
> Set this to `first' (default) or `last' to
> display folders first or last, respectively.
> Any other value will mix files and folders.
> - :sitemap-alphabetically The site map is normally sorted alphabetically.
> - Set this explicitly to nil to turn off sorting.
> + :sitemap-sort-files The site map is normally sorted alphabetically.
> + You can change this behaviour setting this to
> + `chronologically', `anti-chronologically' or nil.
>:sitemap-ignore-case Should sorting be case-sensitive? Default nil.
>
> The following properties control the creation of a concept index.
> @@ -233,13 +234,18 @@ Any changes made by this hook will be saved."
>:group 'org-publish
>:type 'hook)
>
> -(defcustom org-publish-sitemap-sort-alphabetically t
> - "Should sitemaps be sorted alphabetically by default?
> +(defcustom org-publish-sitemap-sort-files 'alphabetically
> + "How sitemaps files should be sorted by default?
> +Possible values are `alphabetically', `chronologically',
> `anti-chronologically' and nil.
> +If `alphabetically', files will be sorted alphabetically.
> +If `chronologically', files will be sorted with older modification time
> first.
> +If `anti-chronologically', files will be sorted with newer modification time
> first.
> +nil won't sort files.
>
> You can overwrite this default per project in your
> -`org-publish-project-alist', using `:sitemap-alphabetically'."
> +`org-publish-project-alist', using `:sitemap-sort-files'."
>:group 'org-publish
> - :type 'boolean)
> + :type 'symbol)
>
> (defcustom org-publish-sitemap-sort-folders 'first
>"A symbol, denoting if folders are sorted first in sitemaps.
> @@ -360,30 +366,37 @@ This splices all the components into the list."
> (nreverse (org-publish-delete-dups (delq nil rtn)
>
>
> -(defvar sitemap-alphabetically)
> +(defvar sitemap-sort-files)
> (defvar sitemap-sort-folders)
> (defvar sitemap-ignore-case)
> (defvar sitemap-requested)
> (defun org-publish-compare-directory-files (a b)
> - "Predicate for `sort', that sorts folders-first/last and alphabetically."
> + "Predicate for `sort', that sorts folders and files for sitemap."
>(let ((retval t))
> -(when (or sitemap-alphabetically sitemap-sort-folders)
> - ;; First we sort alphabetically:
> - (when sitemap-alphabetically
> -(let* ((adir (file-directory-p a))
> - (aorg (and (string-match "\\.org$" a) (not adir)))
> - (bdir (file-directory-p b))
> - (borg (and (string-match "\\.org$" b) (not bdir)))
> - (A (if aorg
> - (concat (file-name-directory a)
> - (org-publish-find-title a)) a))
> -
[Orgmode] Re: Export error. Have a look at my backtrace?
Jeff Horn wrote: > Hey orgsters, > Export started behaving weirdly for me earlier this week. When I > export to HTML or ASCII to a temporary buffer, I get the attached > backtrace. This occurs in emacs 24 (Aquamacs) with org-mode 7.4. The > error does not occur if I export to file. > Also, exporting to a temporary buffer works as expected in emacs 23.2 > with org-mode 7.4 in terminal emacs. > Error occurs with every file I have tried in the past few days. Can > anyone else reproduce? I'll come up with a minimal working example if > needed. This is an Aquamacs specific issue, I believe. What happens is that Emacs tries to guess the major mode of the temporary buffer. Aquamacs has the following entry in either magic-mode-alist, or magic-fallback-mode-alist. (objc-mode-buffer-check . objc-mode) So it calls the objc-mode-buffer-check function, and puts the buffer in objc-mode if the former returns non-nil. Here's the definition of said function: (defun objc-mode-buffer-check () (if (string-match "\\.m$" buffer-file-name) (save-restriction (narrow-to-region (point-min) (min (point-max) (+ (point-min) magic-mode-regexp-match-limit))) (looking-at "\\(.\\|\n\\)*#\\(include\\|define\\|import\\)" The culprit is the first line, this function should first check that buffer-file-name is a string before trying to match against it. So you should probably shout at the Aquamacs developers :P. Lawrence -- Lawrence Mitchell ___ 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] [Patch 1/2] org-publish
Hi Manuel, Manuel Giraud writes: > This first patch adds sort options to the sitemap. In addition to > alphabetical order, one can choose chronological or anti-chronological > ordering of sitemap entries. To retrieve file date, it tries to parse > the "#+date" keyword and if not present defaults to file modification > time. I've now applied this patch -- thanks for this contribution. -- Bastien ___ 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
[Accepted] [Orgmode] Re: [Accepted] Re: Bug: Jumping to a date in the agenda changes view back to 'day' [7.4 (release_7.4.80.g0e5e5)]
Patch 587 (http://patchwork.newartisans.com/patch/587/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C87sjvzaezr.fsf%40keller.adm.naquadah.org%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [Orgmode] Re: [Accepted] Re: Bug: Jumping to a date in the agenda > changes view back to 'day' [7.4 (release_7.4.80.g0e5e5)] > Date: Mon, 07 Feb 2011 16:39:17 - > From: Julien Danjou > X-Patchwork-Id: 587 > Message-Id: <87sjvzaezr@keller.adm.naquadah.org> > To: Matt Lundin > Cc: Bastien Guerry , emacs-orgmode@gnu.org > > On Sat, Feb 05 2011, Matt Lundin wrote: > > > This results in only a day view because org-agenda-current-span is still > > 'day. > > Here's a proposal fix. > > I could have setq org-agenda-current-span to nil as a work around, but > it seems more logical to just kill all the local variables. That is, a > custom agenda view would not keep any of the local variable of the > previous agenda, which seems logical to me. > > > >From b48fc7c395dffea60df20c23b26e362ac0354b01 Mon Sep 17 00:00:00 2001 > From: Julien Danjou > Date: Mon, 7 Feb 2011 12:36:42 +0100 > Subject: [PATCH] org-agenda: kill local variables in agenda view > > * org-agenda.el (org-agenda): Kill all local variables. This > assures we are not keeping buffer variable from an old agenda view > when switching to a new custom agenda. > > Signed-off-by: Julien Danjou > --- > lisp/org-agenda.el |2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el > index d146f83..9a3d953 100644 > --- a/lisp/org-agenda.el > +++ b/lisp/org-agenda.el > @@ -2161,6 +2161,8 @@ Pressing `<' twice means to restrict to the current > subtree or region >(put 'org-agenda-redo-command 'org-lprops nil) >;; Remember where this call originated >(setq org-agenda-last-dispatch-buffer (current-buffer)) > + ;; Remove all local variables > + (kill-all-local-variables) >(unless keys > (setq ans (org-agenda-get-restriction-and-command prefix-descriptions) > keys (car ans) > -- > 1.7.2.3 > > ___ 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] [Patch 2/2] org-publish
Hi Manuel, Manuel Giraud writes: > This second patch (that should be applied after the first one) adds a > formating option to sitemap entries. One can now use a formated string > to generate a sitemap entry. This formated string currently understands > title (%T), author (%A) and date (%D). I tested this patch and it produce weird results. (setq org-publish-sitemap-file-entry-format "%T") Outputs ill-formed links instead of the title. I'd welcome a reworked version of this idea! Best, -- Bastien ___ 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] export weekly completed/late items
This is a great idea, and one I would use myself. I don't think you could configure the agenda to build something like that though, I'd say we'd need to come up with some custom elisp code or a script that parses the org archive file and does the dirty job. Marcelo. On Mon, Feb 7, 2011 at 2:04 PM, Kyle Farrell wrote: > I'm trying to create a weekly report of items completed or > outstanding. I'd like to bucket these by status. I've got my entries > with a DEADLINE calendar date set. > > For example given the org input: > > * TODO Fix bug for software project X > DEADLINE: <2011-02-07 Mon> > * DONE Update documentation for feature Y > DEADLINE: <2011-02-09 Wed> > * DONE Scope out new version of Z > DEADLINE: <2011-02-09 Wed> > * TODO Code new version of Z > DEADLINE: <2011-02-17 Thu> > > I'd like to bucketize these based on the current date TODO status. If > the date is 2/11/2011, based on the deadline and the status I'd like > to see: > > Missed: > 2011-02-07: Fix bug for software project X > > Completed: > 2011-02-09: Update documentation for feature Y > 2011-02-09: Scope out new version of Z > > Coming up: > 2011-02-17: Code new version of Z > > > Am I best using an agenda view to create this? Or would this be in a > custom exporter? > > thanks! > -Kyle > > ___ > 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 > ___ 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] crypt entries and journal
On Mon, Feb 07 2011, Richard Riley wrote: > I would like them to. Best way? Decrypt them on file loading. (defun jd:org-decrypt-entires-silently () (let ((m (buffer-modified-p))) (org-decrypt-entries) (unless m (set-buffer-modified-p nil (add-hook 'org-mode-hook 'jd:org-decrypt-entires-silently) I think that's something that could be added to org-crypt. I'll make a patch later. -- Julien Danjou ❱ http://julien.danjou.info pgpDKaMvDcFRM.pgp Description: PGP signature ___ 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] Call org-map-entries just on children?
Hi Bastien, >> How can I apply f just to the *children* of "Paper 1"? > > You can simply add > > (setq org-map-continue-from (outline-next-heading)) > > at the very beginning of your `f' function. Ah, very good. Thanks so much! Best, Richard ___ 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
[Orgmode] [PATCH] Solved the problem of org-capture apparently not working
Hi,
Resending the patch, since it seems like patchwork hasn't grabbed it.
--
Puneeth
-- Forwarded message --
From: Puneeth Chaganti
Date: Sat, Feb 5, 2011 at 12:18 PM
Subject: Re: [Orgmode] [PATCH] Solved the problem of org-capture
apparently not working
To: Charles Cave
Cc: emacs-orgmode@gnu.org
Hi,
On Sat, Feb 5, 2011 at 9:57 AM, Puneeth Chaganti wrote:
> Hi,
>
> On Sat, Feb 5, 2011 at 6:02 AM, Charles Cave wrote:
> [..]
>> My suggestion to eliminate the problem is to modify the org-capture algorithm
>> so years have to match beginning of line + one asterisk + one space + the
>> year
>>
>> Similarly, months could match beginning of line + two asterisks + one space +
>> the year + hyphen + month number + space + Monthname. But the chance of
>> this
>> format heading appearing outside a date-tree would be very low.
>
> org-datetree currently checks if a buffer has an entry with a DATE_TREE
> property (any value), and if it finds one, the date tree will become a
> subtree under that entry.
>
> This change would break that feature.
Attached is a patch that fixes this, by using the
org-datetree-base-level variable. More details in the commit message.
@Bastien,
I didn't get the time to configure and use git-send-email. I am
sending a patch obtained using git-format-patch. So, you will have to
use git-am to apply this. (of course, if this seems good enough :))
-- Puneeth
--
Puneeth
From ab7961c3cea92271d803fdb3df89663e9c9a88ab Mon Sep 17 00:00:00 2001
From: Puneeth Chaganti
Date: Sat, 5 Feb 2011 12:08:10 +0530
Subject: [PATCH] Fix regex for finding datetree year subtree
* org-datetree.el (org-datetree-find-year-create): Use
`org-datetree-base-level' in the regex to find year subtree.
On Sat, Feb 5, 2011 at 9:57 AM, Puneeth Chaganti wrote:
>
>> On Sat, Feb 5, 2011 at 6:02 AM, Charles Cave wrote:
>> In early January I posted what I thought was a bug report with org-capture.
>>
>> I found that capturing to a date-tree didn't always work and in one file the
>> capture was written to the wrong place.
>>
>> Well, the problem was with the data! One of my headings began with 2011.
>>
>> The tree looked something like this (edited)
>>
>> * 2010
>> ** 2010-12 December
>> *** 2010-12-05 Sunday
>> A heading
>> 2011 Actions <-- this caused the problem
>> Another heading
>> ...
>> *** 2010-12-06 Monday
>> ...
>> ...
>>
>>
> In 2011 when I captured into this file's date-tree,
> org-capture found the headline 2011 Actions which matched the algorithm
> and the captured item appeared at the end of the headings at that level.
>
>> My suggestion to eliminate the problem is to modify the org-capture algorithm
>> so years have to match beginning of line + one asterisk + one space + the
>> year
>>
>> Similarly, months could match beginning of line + two asterisks + one space +
>> the year + hyphen + month number + space + Monthname.But the chance of
>> this
>> format heading appearing outside a date-tree would be very low.
>
> org-datetree currently checks if a buffer has an entry with a DATE_TREE
> property (any value), and if it finds one, the date tree will become a
> subtree under that entry.
>
> This change would break that feature.
Using the value of `org-datetree-base-level' in the regex instead of
checking for at least one star, or hard coding the number of stars (as
suggested by Charles Cave).
Also, only the regex for finding the year subtree needs to be changed,
since it is assumed that all the children of this subtree are
"generated" and there are no bad headings, like in Charles' example.
---
lisp/org-datetree.el |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/lisp/org-datetree.el b/lisp/org-datetree.el
index 8014f8f..5c48f86 100644
--- a/lisp/org-datetree.el
+++ b/lisp/org-datetree.el
@@ -64,7 +64,8 @@ tree can be found."
(goto-char (prog1 (point) (widen))
(defun org-datetree-find-year-create (year)
- (let ((re "^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t\n]")
+ (let* ((n org-datetree-base-level)
+ (re (format "^\\*\\{%s\\}[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t\n]" n))
match)
(goto-char (point-min))
(while (and (setq match (re-search-forward re nil t))
--
1.7.3.5
___
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
[Orgmode] Re: Fontification of blocks
Sébastien Vauban writes: > Hi Dan, > > Dan Davison wrote: >> Sébastien Vauban >> >> writes: >>> Dan Davison wrote: Just quickly, one thing I noticed is that the begin/end lines were visible even inside folded trees. I.e., in a folded org file, containing many src blocks, I could see the coloured backgrounds "poking out" of the folded sections, extending to the right of the screen. Do you see that? >>> >>> Yes, but that's already the current situation today, *when using faces with >>> background*. My (future) patch does not change that, and I'm not sure >>> whether it should or not. In a way, I find this better: it makes it very >>> clear there is a code block folded at that point in the document. Yes, I >>> definitively prefer it that way -- if you don't mind. >> >> Hi Seb, hmm, maybe we're talking about different things. > > I think so as well. I was thinking you were talking about the delimiter line > (begin_src and end_src) going up to the right end of the screen if the fully > expanded view. > > Your picture shows it when folded. > >> I would say this is a bug. > > Indeed, that's definitely a bug. > >> A key part of Org's visual model is that folding hides content. Imo. I'm not >> saying I know how to fix it, but that's a separate issue. Here are three >> screenshots: >> >> org-overview: >> org-content: >> show-all: > > Can you send me your file, for me to test if I have the same problem? I don't have that file any longer, but the problem occurs with all files. It is somewhat unpredictable -- I mess about with block show/hide, and global visibility cycling, and it happens eventually if not at first. E.g. this file - * heading #+begin_src emacs-lisp 1 #+end_src - > > FYI, I've seen that once when working on my patch[1], but never ever since the > last versions. Hence, just checking (plizz don't mind), are you really using > the version committed in the trunk, yes, clean, HEAD is 88b793946. Note I'm on OS X (cocoa builds). Maybe someone else with OSX could try to reproduce this? It occurs with a distributed binary of aquamacs, and when loading nothing but Org, so it doesn't seem to be any local stuff of mine that's the problem. Dan > or some older version I may have sent on > this list? > >> (Btw, that's with the box face attribute set with your patch. Just >> playing with it to see if I like it.) > > Maybe make a try with underline and overline -- discovered not that long ago. > I find that the nicest combination... As well for headings 1 and 2. I'll send > my newest color theme very soon for you to see this, if you're interested. > Nope: correction, I'll put it directly on Worg. I'll ask for access, and try > being autonomous for such things. > > Best regards, > Seb > > Footnotes: > [1] IIRC, Eric Fraga did see that as well, at some point in time. ___ 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] export weekly completed/late items
I'm a bit of a newbie to org-mode, so where should I start to look at this? Is there existing functionality in either org-agenda or org-export that would be a good starting point? Marcelo de Moraes Serpa wrote: > This is a great idea, and one I would use myself. I don't think you > could configure the agenda to build something like that though, I'd > say we'd need to come up with some custom elisp code or a script that > parses the org archive file and does the dirty job. > > Marcelo. > > On Mon, Feb 7, 2011 at 2:04 PM, Kyle Farrell wrote: > > I'm trying to create a weekly report of items completed or > > outstanding. I'd like to bucket these by status. I've got my entries > > with a DEADLINE calendar date set. > > > > For example given the org input: > > > > * TODO Fix bug for software project X > > DEADLINE: <2011-02-07 Mon> > > * DONE Update documentation for feature Y > > DEADLINE: <2011-02-09 Wed> > > * DONE Scope out new version of Z > > DEADLINE: <2011-02-09 Wed> > > * TODO Code new version of Z > > DEADLINE: <2011-02-17 Thu> > > > > I'd like to bucketize these based on the current date TODO status. If > > the date is 2/11/2011, based on the deadline and the status I'd like > > to see: > > > > Missed: > > 2011-02-07: Fix bug for software project X > > > > Completed: > > 2011-02-09: Update documentation for feature Y > > 2011-02-09: Scope out new version of Z > > > > Coming up: > > 2011-02-17: Code new version of Z > > > > > > Am I best using an agenda view to create this? Or would this be in a > > custom exporter? > > > > thanks! > > -Kyle > > > > ___ > > 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 > > > ___ 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
[Orgmode] Re: Problem exporting table with images
Hi Rainer,
Rainer M Krug wrote:
> #+TITLE: Export of images in table to pdf
> #+AUTHOR:Rainer M. Krug
> #+DATE: 2011-02-08 Tue
>
> Hi
>
> I have problems exporting this table with graphs to pdf:
> 1) when exporting, the links are retained, and okular tells me
> "malformed url"
> 2) I would like to have the graphs inserted instead of the links ---
> according to the manual, this should be done automatically, but it does
> not work.
>
> Is there something I am missing here?
> Cheers,
>
> Rainer
>
> * Generating the graphs
> #+begin_src R :results output org :exports both
> cat("|---|---|---|\n")
> for (x in 1:3) {
> for (y in 1:3) {
> pdf(paste("img", x, y, "pdf", sep="."))
> plot(runif(100))
> dev.off()
> }
> cat("|", paste(" [[file:img.1", x, "pdf", sep="."), "]] |",
> paste(" [[./img.2", x, "pdf", sep="."), "]] |", paste("[[./img.3", x,
> "pdf", sep="."), "]] |\n")
> }
> cat("|---|---|---|\n")
> #+end_src
>
> #+results:
> #+BEGIN_ORG
> |---++|
> | [[file:img.1.1.pdf ]] | [[./img.2.1.pdf ]] | [[./img.3.1.pdf ]] |
> | [[file:img.1.2.pdf ]] | [[./img.2.2.pdf ]] | [[./img.3.2.pdf ]] |
> | [[file:img.1.3.pdf ]] | [[./img.2.3.pdf ]] | [[./img.3.3.pdf ]] |
> |---++|
> #+END_ORG
Don't know if that can be the source of the problem, but it appears you have
spaces after the filename, in your links.
Best regards,
Seb
--
Sébastien Vauban
___
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: [ANN] Changes to lists
Hello, > Karl Maihofer writes: > This does not work for me. Lists in inline tasks are still exported > as follows: > * > item 1 > * > item 2 > What do I miss? Well, nothing. I just pushed a small patch to remove unneeded newline characters. It does help a bit in you situation. Though, the default HTML template for inline tasks encloses them in a tag. Thus, you have to keep in mind export will be very sensitive to white space or newlines anyway. If it doesn't fit your needs, you can always configure org-inlinetask-export-templates. Regards, -- Nicolas ___ 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
[Orgmode] Re: Fontification of blocks
Hi Dan, Dan Davison wrote: > Sébastien Vauban > writes: >> Dan Davison wrote: >>> Sébastien Vauban >>> >>> writes: Dan Davison wrote: > Just quickly, one thing I noticed is that the begin/end lines were > visible even inside folded trees. I.e., in a folded org file, containing > many src blocks, I could see the coloured backgrounds "poking out" of > the folded sections, extending to the right of the screen. Do you see > that? >>> >>> I would say this is a bug. >> >> Indeed, that's definitely a bug. >> Can you send me your file, for me to test if I have the same problem? > > I don't have that file any longer, but the problem occurs with all > files. It is somewhat unpredictable -- I mess about with block > show/hide, and global visibility cycling, and it happens eventually if > not at first. E.g. this file > > - > * heading > #+begin_src emacs-lisp > 1 > #+end_src > - I could reproduce it with your above file, if the file ends on the end_src line. The following: --8<---cut here---start->8--- * heading #+begin_src emacs-lisp 1 #+end_src * other heading --8<---cut here---end--->8--- also exhibits the problem, but this one: --8<---cut here---start->8--- * heading #+begin_src emacs-lisp 1 #+end_src * other heading --8<---cut here---end--->8--- does not. So, it is related to the fact that the block is the last line of the subtree or of the file. As I always have newlines before headings, I don't see such a problem on my docs. Dan, can you confirm the above observation? Knowing this, do you have an idea on how to fix it? If not, I'll try having a play with the patched file. Best regards, Seb -- Sébastien Vauban ___ 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: Export error. Have a look at my backtrace?
Forwarded to Aquamacs. Thanks. On Tue, Feb 8, 2011 at 11:55 AM, Lawrence Mitchell wrote: > Jeff Horn wrote: > >> Hey orgsters, > >> Export started behaving weirdly for me earlier this week. When I >> export to HTML or ASCII to a temporary buffer, I get the attached >> backtrace. This occurs in emacs 24 (Aquamacs) with org-mode 7.4. The >> error does not occur if I export to file. > >> Also, exporting to a temporary buffer works as expected in emacs 23.2 >> with org-mode 7.4 in terminal emacs. > >> Error occurs with every file I have tried in the past few days. Can >> anyone else reproduce? I'll come up with a minimal working example if >> needed. > > This is an Aquamacs specific issue, I believe. What happens is > that Emacs tries to guess the major mode of the temporary > buffer. Aquamacs has the following entry in either > magic-mode-alist, or magic-fallback-mode-alist. > > (objc-mode-buffer-check . objc-mode) > > So it calls the objc-mode-buffer-check function, and puts the > buffer in objc-mode if the former returns non-nil. Here's the > definition of said function: > > (defun objc-mode-buffer-check () > (if (string-match "\\.m$" buffer-file-name) > (save-restriction > (narrow-to-region (point-min) > (min (point-max) > (+ (point-min) magic-mode-regexp-match-limit))) > (looking-at "\\(.\\|\n\\)*#\\(include\\|define\\|import\\)" > > > The culprit is the first line, this function should first check > that buffer-file-name is a string before trying to match against > it. So you should probably shout at the Aquamacs developers :P. > > Lawrence > -- > Lawrence Mitchell > > > ___ > 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 > -- Jeffrey Horn http://www.failuretorefrain.com/jeff/ ___ 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
[Orgmode] Re: Table cells containing more than one line
orgmode tables do not allow row or column span. table.el allows you to do that but I haven't been able to get it to work in org files. ___ 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
[Orgmode] Re: [Feature Request] Cross headings in tables
If anybody wants to test the current state of affairs, I've just set up a fork repository to make it easier. Assuming you already have orgmode.git cloned, do a git remote add -t tableheadings remote-tableheadings git://repo.or.cz/org-mode/org-tableheadings.git git fetch remote-tableheadings tableheadings:local-tableheadings git checkout local-tableheadings to get it (change remote-tableheadings and local-tableheadings to suit your naming conventions for remotes and local branches, respectively). I will be _rebasing_ against master during development, so expect history in this branch to be volatile. As before, test cases and comments welcome. Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds ___ 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
[Orgmode] custom agenda view with tags-todo not work
I tried to set the custom view in the calendar, but does not work.
#+BEGIN_SRC elisp
(setq org-agenda-custom-commands
'(
("f" "FIXED" tags-todo
"+bug+TODO=\"DONE\"+STATUS=\"FIXED\"+CLOSED>=\"\"")
)
)
#+END_SRC
No error occurs when run:
#+BEGIN_EXAMPLE
Press key for an agenda command:< Buffer, subtree/region restriction
> Remove restriction
a Agenda for current week or day e Export agenda views
t List of all TODO entriesT Entries with special TODO kwd
m Match a TAGS/PROP/TODO queryM Like m, but only TODO entries
L Timeline for current buffer # List stuck projects (!=configure)
s Search for keywords C Configure custom agenda commands
/ Multi-occur ? Find :FLAGGED: entries
f FIXED : +bug+TODO="DONE"+STATUS="FIXED"+CLOSED>=""
Headlines with TAGS match: +bug+TODO="DONE"+STATUS="FIXED"+CLOSED>=""
Press `C-u r' to search again with new search string
-UUU:%*--F1 *Org Agenda* All L1 (Org-Agenda Ddl Grid)---
No event to add
#+END_EXAMPLE
Can someone tell me where is the error? thanks!
pd: I made a t-shirt with a custom logo of Unicorn [0], enjoy!
[0] http://pub.osiux.com/org-mode/org-mode-is-the-unics-of-organizers.svg
--
Osiris Alejandro Gomez (OSiUX) os...@osiux.com.ar
E1B1 EB8E E37B 10B3 47E9 D73A 2C09 297C FFB9 4410
http://wiki.buenosaireslibre.org/NodoOsiux
___
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
[Orgmode] Automatic noexport tag based on rules?
Hi, My apologies if this has been discussed. I couldn't find it. I write everything from work in org-mode for several reasons. Primarily, it's my documentation system for research in order to properly document Intellectual Property (IP) information. It's also for todos and contacts. When it comes to exporting my notes into PDF for use in an IP notebook... I dont' want my todos in there. Is there a way to automatically tag TODOs with :noexport:? Or simply add the TODO category to the noexport category altogether? I haven't turned up anything quite along these lines. One post suggested using "TODO keyword COMMENT" [1], but that just seems to perhaps exclude from export (didn't try) but I know for sure it removes it from agenda view. I want TODOs in agenda but don't want them showing up with my LaTeX export. I typically print out my work to-date each month or so and have to comb through my org file for that month, manually adding :noexport: to my TODOs. Even if I still do this for a few things here and there... it will save me a lot of time. I suppose I could keep a separate "TODO.org" file, but I really like the process of being able to add them anywhere -- it seems more natural to do that in the flow, particularly in meetings, than to constantly switch buffers or even use remember to keep sending things related to the current topic away to their own island. I'm 80% confident that the answer is ridiculously simply and I just haven't searched the right thing. Thanks for enlightening me! Thanks, John ___ 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] Automatic noexport tag based on rules?
I'm not handy with emacs-lisp, but perhaps someone could whip up a handy function that iterates org-refile over each TODO heading to move it into a new, top-level * Tasks headline? Then you can tag the tasks headline with :noexport:. This would destroy the "context", but I find keeping tasks in a separate heading fine for most of *my* medium sized projects. YMMV. On Tue, Feb 8, 2011 at 7:29 PM, John Hendy wrote: > Hi, > > My apologies if this has been discussed. I couldn't find it. I write > everything from work in org-mode for several reasons. Primarily, it's my > documentation system for research in order to properly document Intellectual > Property (IP) information. It's also for todos and contacts. When it comes > to exporting my notes into PDF for use in an IP notebook... I dont' want my > todos in there. > Is there a way to automatically tag TODOs with :noexport:? > Or simply add the TODO category to the noexport category altogether? > I haven't turned up anything quite along these lines. One post suggested > using "TODO keyword COMMENT" [1], but that just seems to perhaps exclude > from export (didn't try) but I know for sure it removes it from agenda view. > I want TODOs in agenda but don't want them showing up with my LaTeX export. > I typically print out my work to-date each month or so and have to comb > through my org file for that month, manually adding :noexport: to my TODOs. > Even if I still do this for a few things here and there... it will save me a > lot of time. > I suppose I could keep a separate "TODO.org" file, but I really like the > process of being able to add them anywhere -- it seems more natural to do > that in the flow, particularly in meetings, than to constantly switch > buffers or even use remember to keep sending things related to the current > topic away to their own island. > I'm 80% confident that the answer is ridiculously simply and I just haven't > searched the right thing. Thanks for enlightening me! > > Thanks, > John > ___ > 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 > > -- Jeffrey Horn http://www.failuretorefrain.com/jeff/ ___ 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] Automatic noexport tag based on rules?
On Tue, Feb 8, 2011 at 7:58 PM, Jeff Horn wrote: > I'm not handy with emacs-lisp, but perhaps someone could whip up a > handy function that iterates org-refile over each TODO heading to move > it into a new, top-level * Tasks headline? > > Thanks for the suggestion. I'm not a huge fan, but it would get done what I want to accomplish as far as the export goes. > Then you can tag the tasks headline with :noexport:. This would > destroy the "context", but I find keeping tasks in a separate heading > fine for most of *my* medium sized projects. YMMV. > Yeah.. most of my todos aren't medium-sized projects, though. Many of them are more along the lines of one-liner action items I need to jot to myself so I don't forget as well as keeping them as a sort of rolling "next actions" queue. For that reason, I'd much rather keep them in their original context. This can't be too hard. ,--- | sed '/[*]* TODO/ s/$/ :noexport:/g' `--- Or (facetious) ,--- | setq (prefix-for-noexport-custom-variable) | setq (default-tags-for-no-export-variable) `--- I just don't know what the elegant, "right" elisp/org method is for something like this. John > On Tue, Feb 8, 2011 at 7:29 PM, John Hendy wrote: > > Hi, > > > > My apologies if this has been discussed. I couldn't find it. I write > > everything from work in org-mode for several reasons. Primarily, it's my > > documentation system for research in order to properly document > Intellectual > > Property (IP) information. It's also for todos and contacts. When it > comes > > to exporting my notes into PDF for use in an IP notebook... I dont' want > my > > todos in there. > > Is there a way to automatically tag TODOs with :noexport:? > > Or simply add the TODO category to the noexport category altogether? > > I haven't turned up anything quite along these lines. One post suggested > > using "TODO keyword COMMENT" [1], but that just seems to perhaps exclude > > from export (didn't try) but I know for sure it removes it from agenda > view. > > I want TODOs in agenda but don't want them showing up with my LaTeX > export. > > I typically print out my work to-date each month or so and have to comb > > through my org file for that month, manually adding :noexport: to my > TODOs. > > Even if I still do this for a few things here and there... it will save > me a > > lot of time. > > I suppose I could keep a separate "TODO.org" file, but I really like the > > process of being able to add them anywhere -- it seems more natural to do > > that in the flow, particularly in meetings, than to constantly switch > > buffers or even use remember to keep sending things related to the > current > > topic away to their own island. > > I'm 80% confident that the answer is ridiculously simply and I just > haven't > > searched the right thing. Thanks for enlightening me! > > > > Thanks, > > John > > ___ > > 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 > > > > > > > > -- > Jeffrey Horn > http://www.failuretorefrain.com/jeff/ > ___ 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] Automatic noexport tag based on rules?
On Tue, Feb 8, 2011 at 9:39 PM, John Hendy wrote: > I just don't know what the elegant, "right" elisp/org method is for > something like this. I'll leave that to the experts. ;) Best wishes. -- Jeffrey Horn http://www.failuretorefrain.com/jeff/ ___ 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
[Orgmode] Re: Table cells containing more than one line
srinivas writes: > orgmode tables do not allow row or column span. I believe this is by design. > > table.el allows you to do that but I haven't been able to get it to work in > org files. > Could you please clarify what you mean by 'get it to work'. May be you are experiencing some issues with having them exported. I had filed a report few months back. See http://lists.gnu.org/archive/html/emacs-orgmode/2010-12/msg00978.html Jambunathan K. > > > ___ > 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 ___ 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
[Orgmode] org-agende changes mode in buffer to fundamental
Hi! Just trying to start my workday ... As always the first command is emacs todo.org Everthing looks like it should, mode is Org . But now, if I type C-a a to view my agenda, mode is reverted back to fundamental. That also happens if I use M-x org-agenda to start it. Mode line tells me: Agenda file todo.org not in org-mode. Message buffer: org-agenda-get-day-entries: Agenda file ~/.pim/todo.org is not in `org-mode' Well --- it was when I called you, org-mode! ;-) org-version release_7.4-324-gca7a Org-mode version 7.4 (release_7.4.324.gca7a) Any immediate help advice? Ok, the lecture starts 9:45 ... but what else was planned for today? :-) Detlef ___ 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: Using latexmk for LaTeX compilation
> This setting works for me to produce pdfs via latexmk. > > (setq org-latex-to-pdf-process (list "latexmk -f -pdf %f")) > This almost solved my problem - after changing %f to %s it worked as expected. Thnx! ___ 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
