[O] point out extra export options in manual
Whilst trying to figure out how to shut off the postamble in HTML export, I realized that there are far more export-related options available than those listed in section 12.2 (Export options) of the manual. I had never really looked at the Publishing section of the manual (13.1.5), because I've never wanted to publish whole projects. If the list of LaTeX/HTML export options in the Publishing section is the canonical full list, it would be nice to mention in section 12.2 that the options selectable through the #+OPTIONS syntax is only a subset of the full list, and provide a pointer to the Publishing section. I can bang together a documentation patch for this, if desirable, otherwise please let me know if I've missed some crucial part of the documentation that would have made this clear. Thanks, Eric PS: I've seen people provide links to Info pages directly in their emails (presumably only any good if the recipient is using an emacs-based mail client), how do you do that? Will a regular Org format link come through correctly? Well, why don't I try… [[info:org:Configuration][Publishing Configuration]]
Re: [O] org google weather
On 03/03/11 21:37, Simon Brown wrote: Evening all, Has anybody tried adding the functionality of %%(diary-sunrise-sunset) (sunrise, sunset time and daylight hours) to the google weather code? Simon I just have something like: #+CATEGORY: Day/Year %%(diary-day-of-year) #+CATEGORY: Sunrise %%(diary-sunrise-sunset) in one of my Agenda files. Sunrise then appears at sunrise time in my Agenda like: Sunrise: 6:53.. Sunrise (GMT), sunset 5:52pm (GMT) at Wilkesley (10:58 hours daylight) You need to have some magic fu like: #+BEGIN_SRC emacs-lisp (setq calendar-latitude 53) (setq calendar-longitude -2.6) (setq calendar-location-name Wilkesley) #+END_SRC in your .emacs so Emacs knows where you are. Ian.
Re: [O] org google weather
Hi Ian, Ian Barton wrote: Has anybody tried adding the functionality of %%(diary-sunrise-sunset) (sunrise, sunset time and daylight hours) to the google weather code? I just have something like: #+CATEGORY: Day/Year %%(diary-day-of-year) #+CATEGORY: Sunrise %%(diary-sunrise-sunset) in one of my Agenda files. Sunrise then appears at sunrise time in my Agenda like: Sunrise: 6:53.. Sunrise (GMT), sunset 5:52pm (GMT) at Wilkesley (10:58 hours daylight) Do you have a way to get the sunset located on a line on its own (different line from the sunrise one)? That'd be even much nicer... Best regards, Seb -- Sébastien Vauban
Re: [O] Re: Automatic Org-mode mailing list signature -- Was: Let's stick to one list for now
On Thu, Mar 03 2011, Nick Dokos wrote: There are a few times when I've needed to go to the listinfo page and I've followed the link from the banner. I'm sure there are other ways of doing that though, so it's a /small/ objection :-) Yes, look at the mail headers: List-Id: General discussions about Org-mode. emacs-orgmode.gnu.org List-Unsubscribe: http://lists.gnu.org/mailman/listinfo/emacs-orgmode, mailto:emacs-orgmode-requ...@gnu.org?subject=unsubscribe List-Archive: http://lists.gnu.org/archive/html/emacs-orgmode List-Post: mailto:emacs-orgmode@gnu.org List-Help: mailto:emacs-orgmode-requ...@gnu.org?subject=help List-Subscribe: http://lists.gnu.org/mailman/listinfo/emacs-orgmode, mailto:emacs-orgmode-requ...@gnu.org?subject=subscribe -- Julien Danjou ❱ http://julien.danjou.info pgp9BbNt0rKx1.pgp Description: PGP signature
[O] Title page in latex export
Hi Orgers,
I am trying to write my thesis as per my university style. It requires
I use the \title{Thesis title} command before the
\begin{document}
...
\end{document}
Is there any way to do that? Thanks for any thoughts.
--
Suvayu
Open source is the future. It sets us free.
[O] orgtbl export option :hlstart :hllstart
Dear orgers, I love orgtbl minor mode in auctex. I tried to set it up today for ctable and this is the work in progress: % % BEGIN RECEIVE ORGTBL systems headline headline \\NN second row second row \\NN % END RECEIVE ORGTBL systems #+ORGTBL: SEND systems orgtbl-to-latex :splice t :skip 0 :hline nil :lend \\NN :llend \\LL :hlstart \\FL :hlend \\ML | headline | headline | | second row | second row | all works nicely, except :hlstart \\FL :hlend \\ML, and hll variants of those which I found in the docstring for the orgtbl-to-latex function, do not work. Do I miss something? Michael
Re: [O] Title page in latex export
Hi,
I think that what it already does
But if you mean you should use \maketitlte before \begin{document} you could
do it like this:
#+BIND: org-export-latex-title-command
#+LATEX_HEADER: \maketitle
Regards,
CP
2011/3/4 Suvayu Ali fatkasuvayu+li...@gmail.com
Hi Orgers,
I am trying to write my thesis as per my university style. It requires
I use the \title{Thesis title} command before the
\begin{document}
...
\end{document}
Is there any way to do that? Thanks for any thoughts.
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Title page in latex export
Hi Camille,
Thanks a lot for your response.
On Fri, 4 Mar 2011 11:48:39 +0100
Camille persson camille.pers...@gmail.com wrote:
Hi,
I think that what it already does
I don't think it does that. e.g.
#+TITLE: Thesis title
#+AUTHOR:Suvayu Ali
#+LaTeX_CLASS: book
* Introduction
** Chapter 1
** Chapter 2
* My analysis
** Chapter 3
** Chapter 4
gets exported to latex as,
% Created 2011-03-04 Fri 03:19
\documentclass[11pt]{book}
\usepackage[utf8]{inputenc}
...
\tolerance=1000
\providecommand{\alert}[1]{\textbf{#1}}
\begin{document}
\title{Thesis title}
\author{Suvayu Ali}
\date{04 March 2011}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\part{Introduction}
\label{sec-1}
\chapter{Chapter 1}
\label{sec-1_1}
\chapter{Chapter 2}
\label{sec-1_2}
\part{My analysis}
\label{sec-2}
\chapter{Chapter 3}
\label{sec-2_1}
\chapter{Chapter 4}
\label{sec-2_2}
\end{document}
I would like the:
\title{Thesis title}
\author{Suvayu Ali}
\date{04 March 2011}
to be outside the
\begin{document}
...
\end{document}
I hope this clears any confusion.
But if you mean you should use \maketitlte before \begin{document}
you could do it like this:
#+BIND: org-export-latex-title-command
#+LATEX_HEADER: \maketitle
Regards,
CP
--
Suvayu
Open source is the future. It sets us free.
Re: [O] org google weather
Hi Ian, Ian Barton wrote: Has anybody tried adding the functionality of %%(diary-sunrise-sunset) (sunrise, sunset time and daylight hours) to the google weather code? I just have something like: #+CATEGORY: Day/Year %%(diary-day-of-year) #+CATEGORY: Sunrise %%(diary-sunrise-sunset) in one of my Agenda files. Sunrise then appears at sunrise time in my Agenda like: Sunrise: 6:53.. Sunrise (GMT), sunset 5:52pm (GMT) at Wilkesley (10:58 hours daylight) Do you have a way to get the sunset located on a line on its own (different line from the sunrise one)? That'd be even much nicer... No, but I would like one:) If there were separate diary functions for sunrise and sunset it would be easy. Maybe I need to look at the diary elisp and write my own separate functions. Ian.
Re: [O] Title page in latex export
Suvayu Ali wrote:
Hi Camille,
Thanks a lot for your response.
On Fri, 4 Mar 2011 11:48:39 +0100
Camille persson camille.pers...@gmail.com wrote:
Hi,
I think that what it already does
I don't think it does that. e.g.
Try this patch to org-latex.el:
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 19baa40..4db38d6 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -1352,9 +1352,6 @@ OPT-PLIST is the options plist for current buffer.
(org-export-apply-macros-in-string org-export-latex-append-header)
;; define alert if not yet defined
\n\\providecommand{\\alert}[1]{\\textbf{#1}}
- ;; beginning of the document
- \n\\begin{document}\n\n
- ;; insert the title
(format
\n\n\\title{%s}\n
;; convert the title
@@ -1374,6 +1371,9 @@ OPT-PLIST is the options plist for current buffer.
(format-time-string
(or (plist-get opt-plist :date)
org-export-latex-date-format)))
+ ;; beginning of the document
+ \n\\begin{document}\n\n
+ ;; insert the title
;; insert the title command
(when (string-match \\S- title)
(if (string-match %s org-export-latex-title-command)
--
Lawrence Mitchell we...@gmx.li
Re: [O] Title page in latex export
Hi Lawrence, On Fri, 04 Mar 2011 11:38:08 + Lawrence Mitchell we...@gmx.li wrote: Try this patch to org-latex.el: diff --git a/lisp/org-latex.el b/lisp/org-latex.el index 19baa40..4db38d6 100644 --- a/lisp/org-latex.el +++ b/lisp/org-latex.el That does the trick. :) Thanks a lot. I am not very familiar with LaTeX, is the org default the proper syntax and my university style is buggy? -- Suvayu Open source is the future. It sets us free.
Re: [O] Title page in latex export
Hi Suvayu,
Do you use the lastest update of org-mode ?
cause it works perfectly for me without any patch actually...
The following org :
#+begin_org
#+TITLE: My title
#+AUTHOR: Camille Persson
#+DATE: 2011
#+LATEX_CLASS: book
#+end_org
... produce the following latex code:
#+begin_latex
\documentclass[11pt,letter]{book}
%% package list
%%
\title{My title}
\author{Camille Persson}
\date{2011}
\begin{document}
\maketitle
% etc
#+end_latex
to use your university's custom style, you need to put it in your texmf
directory and use the following header lines:
#+LATEX_CLASS: MyUnivThesis
#+LATEX_CLASS_OPTIONS: [options...]
and then customize your .emacs file (or a file in your .emacs.d/) as
following
(add-to-list 'org-export-latex-classes
'(MyUnivThesis
\\documentclass{univstyle}
(\\part{%s} . \\part*{%s})
(\\chapter{%s} . \\chapter*{%s})
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s}))
See http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-6
Yours,
CP
2011/3/4 Suvayu Ali fatkasuvayu+li...@gmail.com
Hi Lawrence,
On Fri, 04 Mar 2011 11:38:08 +
Lawrence Mitchell we...@gmx.li wrote:
Try this patch to org-latex.el:
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 19baa40..4db38d6 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
That does the trick. :) Thanks a lot.
I am not very familiar with LaTeX, is the org default the proper syntax
and my university style is buggy?
--
Suvayu
Open source is the future. It sets us free.
[O] Re: TODO state change from TODO to DONE blocked
Hi Bastien, Bastien wrote: I've a really weird exception occurring: change state from TODO to DONE is blocked... while I'm on a leaf of the Org tree!? Debugger entered--Lisp error: (error #(TODO state change from TODO to DONE blocked 23 27 (face org-todo) 31 35 (face org-done))) Are you using `org-blocker-hook' or `org-trigger-hook'? Nope. Never heard of them. Maybe you can try to `edebug-defun' the `org-todo' function and follow it's execution step by step. Did it, but not obvious to follow -- I don't talk of the code itself, but of my edebug skills. Let us know. Though, hopping from one variable description to another, I remembered that I had set the variable =org-enforce-todo-dependencies= to =t=. Trying to set it to =nil= made the problem disappear... So, it was a bit narrowed. I could see in the description of that var that it could block state change if tasks were ordered and a previous one not done. But I never use the ordered property. ... Well, never, but well in that parent tree. Was it for test purpose? Did I have something else in mind? I dunno anymore, but that property was definitely the culprit. Doing so, I'm wondering: - if the output message could be updated to make it clear what the reason is, or can be? - why it allowed me to update the tasks state when I narrowed the buffer to that task only? Does that mean that *narrowing* somehow *drops the inherited properties*? Anyway, my fault... Best regards, Seb -- Sébastien Vauban
[O] org-crypt.el security problem (From: Milan Zamazal)
Here is an email I received from Milan Zamazal: , | I don't know whether you are aware of this, but I consider it a serious | security problem of org-crypt.el in (at least) Emacs 23.2: | | I've found out that when I edit a (decrypted) crypt entry and the edited | file is autosaved, the autosaved file contains the given crypt entry in | plain text. So unless the user has got a special arrangement of storing | autosave files to a secure location where they are also deleted | securely, the secret content may be accessed either in the autosave file | directly, or it may be later retrieved by an off-line attacker from the | deleted file content that remained stored somewhere on the disk. | | This should be fixed or at least a big warning should be placed in | org-crypt.el. ` I don't have time to look into this. Would someone please see if there is a way to prevent it. Off the top of my head, the only thing I can think of is disabling autosave for any org buffer that uses org-crypt. Hopefully there's an autosave hook where you can encrypt the headings and save to disk using a temporary buffer without having to alter the current buffer and interrupt the user by encrypting a heading that is being edited. -- Peter Jones - pmade inc. 303-219-0226 http://pmade.com
[O] [PATCH] Re: TODO state change from TODO to DONE blocked
Hi Bastien, Sébastien Vauban wrote: Bastien wrote: I've a really weird exception occurring: change state from TODO to DONE is blocked... while I'm on a leaf of the Org tree!? Debugger entered--Lisp error: (error #(TODO state change from TODO to DONE blocked 23 27 (face org-todo) 31 35 (face org-done))) Are you using `org-blocker-hook' or `org-trigger-hook'? Let us know. Though, hopping from one variable description to another, I remembered that I had set the variable =org-enforce-todo-dependencies= to =t=. Trying to set it to =nil= made the problem disappear... So, it was a bit narrowed. I could see in the description of that var that it could block state change if tasks were ordered and a previous one not done. But I never use the ordered property. ... Well, never, but well in that parent tree. Was it for test purpose? Did I have something else in mind? I dunno anymore, but that property was definitely the culprit. Doing so, I'm wondering: - if the output message could be updated to make it clear what the reason is, or can be? diff --git a/lisp/org.el b/lisp/org.el index 3a07cfd..fb60bc6 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -10927,7 +10927,10 @@ For calling through lisp, arg is also interpreted in the following way: (run-hook-with-args-until-failure 'org-blocker-hook change-plist))) (if (interactive-p) - (error TODO state change from %s to %s blocked this state) + (error (concat TODO state change from %s to %s blocked +(because of undone child, or +parent with ORDERED property and undone prior sibling)) +this state) ;; fail silently (message TODO state change from %s to %s blocked this state) (throw 'exit nil Best regards, Seb -- Sébastien Vauban
Re: [O] org google weather
FWIW/YMMV I use RUBY: I like the twilight info too--not sure emacs does
twilight info too--maybe you can reuse some of the code and put into
OrgMode: I do:
emacs -l .bja-sunrise-sunset-twilight.el
--where .bja-sunrise-sunset-twilight.el is:
(defun bja-sunrise ()
Display sunrise, sunset amp; twilight information.
(interactive)
(shell-command ~/sunrise_http_post.rb))
--excerption of sunrise_http_post.rb (available somewhere on the web)
...
require 'net/http'
YOUR_ID = 'BGPOWELL' # A unique ID per comment above
YOUR_CITY = 'Fairfax' # The name of your city
YOUR_STATE = 'VA' # Two letter state abbreviation
now = Time.now
month = now.month
day = now.day + 1 # Tomorrow
year = now.year
Net::HTTP.start('aa.usno.navy.mil') do |query|
response = query.post('/cgi-bin/aa_pap.pl',
FFX=1ID=#{YOUR_ID}xxy=#{year}xxm=#{month}xxd=#{day}st=#{YOUR_STATE}place=#{YOUR_CITY}ZZZ=END)
if response.body =~ /Begin civil twilight[^0-9]*(\d+:\d{2}
[ap].m.).*Sunrise[^0-9]*(\d+:\d{2} [ap].m.).*Sunset[^0-9]*(\d+:\d{2}
[ap].m.).*End civil twilight[^0-9]*(\d+:\d{2} [ap].m.)/m
puts #{month}/#{day}/#{year}
puts Begin Twilight: #{$1}
puts Sunrise : #{$2}
puts Sunset : #{$3}
puts End Twilight : #{$4}
end
end
On Fri, Mar 4, 2011 at 6:27 AM, Ian Barton li...@manor-farm.org wrote:
Hi Ian,
Ian Barton wrote:
Has anybody tried adding the functionality of %%(diary-sunrise-sunset)
(sunrise, sunset time and daylight hours) to the google weather code?
I just have something like:
#+CATEGORY: Day/Year
%%(diary-day-of-year)
#+CATEGORY: Sunrise
%%(diary-sunrise-sunset)
in one of my Agenda files. Sunrise then appears at sunrise time in my
Agenda
like:
Sunrise: 6:53.. Sunrise (GMT), sunset 5:52pm (GMT) at
Wilkesley (10:58 hours daylight)
Do you have a way to get the sunset located on a line on its own
(different
line from the sunrise one)? That'd be even much nicer...
No, but I would like one:) If there were separate diary functions for
sunrise and sunset it would be easy. Maybe I need to look at the diary elisp
and write my own separate functions.
Ian.
Re: [O] org-crypt.el security problem (From: Milan Zamazal)
On Fri, Mar 04 2011, Peter Jones wrote: Hopefully there's an autosave hook where you can encrypt the headings and save to disk using a temporary buffer without having to alter the current buffer and interrupt the user by encrypting a heading that is being edited. I've recently added caching of encrypted text, so that org-crypt will not recrypt the text once again if it has not been modified, but reuse the previous crypting value. That could be used to automagically re-encrypt all text before auto-saving. -- Julien Danjou ❱ http://julien.danjou.info pgp2P8cEXyrk3.pgp Description: PGP signature
[O] Re: [Orgmode] HTML export options are being ignored
Hi Jason, Jason Dunsmore emacs-orgm...@dunsmor.com writes: http://orgmode.org/w/org-mode.git/commitdiff/da8dc7bba7261 1) :preamble was renamed :html-preamble 2) :postamble was renamed :html-postamble 3) org-export-email-info is no longer checked before attempting export of email address. For the first two, the manual needs to be updated. Done, thanks. The third change seems like a bug. Yes. I've changed the default of org-export-html-preamble (and postamble) to nil, so that the default behavior reproduce the old one, and author/email/creator-info options will be honored. Setting :html-preamble in any fashing will override these options for the HTML export. I explained that in the manual. Following your suggestion, I also republished the online manual to reflect these changes: http://orgmode.org/manual/ Also, I have no title when I set the title with #+TITLE: on the first line. I'm not sure if this has to do with org-export-html-title-format being removed. Mhh.. I cannot reproduce this. Can you check again? Thanks, -- Bastien
[O] Re: [Orgmode] HTML export options are being ignored
Hi Cássio, Cássio Koshikumo ckoshik...@gmail.com writes: I think there's a bug with the html exporter. With this OPTIONS line: #+OPTIONS: num:nil author:nil creator:nil timestamp:nil toc:nil I get rid of the numbering and the TOC, but still get the creator, the timestamp and the author lines at the end of the page. Exporting to ASCII seem to exclude them properly. Fixed in latest git repo. Thanks for reporting this. -- Bastien
Re: [O] point out extra export options in manual
Hi Eric, Eric Abrahamsen e...@ericabrahamsen.net writes: Whilst trying to figure out how to shut off the postamble in HTML export, I realized that there are far more export-related options available than those listed in section 12.2 (Export options) of the manual. I had never really looked at the Publishing section of the manual (13.1.5), because I've never wanted to publish whole projects. The Export options section says this: The default values for these and many other options are given by a set of variables. For a list of such variables, the corresponding OPTIONS keys and also the publishing keys (*note Project alist::), see the constant `org-export-plist-vars'. Did you check `org-export-plist-vars'? If the list of LaTeX/HTML export options in the Publishing section is the canonical full list, it would be nice to mention in section 12.2 that the options selectable through the #+OPTIONS syntax is only a subset of the full list, and provide a pointer to the Publishing section. Maybe we can make this clearer (patch welcome) but it is mentioned. I can bang together a documentation patch for this, if desirable, otherwise please let me know if I've missed some crucial part of the documentation that would have made this clear. Please check the latest documentation update from git -- there is certainly room for improvement, and I'd be glad to apply a patch. On the overall, I think a Worg tutorial about publishing options (both infile and in projects publishing settings) would be *very* nice. Thanks for your help, -- Bastien
Re: [O] How to escape characters in tables
On 3/3/11 9:07 PM, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
On Wed, 2 Mar 2011 09:25:57 -0600
ken.willi...@thomsonreuters.com wrote:
The issue is that I've got tables whose cells contain the '|'
character (it's a table of regular expressions), and I can't seem to
figure out how to escape it so that it doesn't mean a delimiter
between cells. Anyone have advice or a pointer to the docs I can't
seem to find?
I don't think you can.
I'm making slight progress, actually.
On StackOverflow
(http://stackoverflow.com/questions/5144862/escape-pipe-character-in-org-mo
de), it was suggested to use the \vert{} character escape, which does
work.
However, since this is code (a regular expression), I want it to appear
monospaced, so I'm not out of the woods yet - here's a test case that
shows my intent:
| foo | =m/foo\vert{}foodfight/= |
The \vert{} seems not to work inside a =...= construction. Furthermore,
the =...= construction is problematic there because it conflicts with the
start-of-formula syntax.
--
Ken Williams
Senior Research Scientist
Thomson Reuters
http://labs.thomsonreuters.com
Re: [O] Re: HTML export options are being ignored
Bastien, Bastien wrote: Hi Jason, Jason Dunsmore emacs-orgm...@dunsmor.com writes: http://orgmode.org/w/org-mode.git/commitdiff/da8dc7bba7261 1) :preamble was renamed :html-preamble 2) :postamble was renamed :html-postamble 3) org-export-email-info is no longer checked before attempting export of email address. For the first two, the manual needs to be updated. Done, thanks. The third change seems like a bug. Yes. I've changed the default of org-export-html-preamble (and postamble) to nil, so that the default behavior reproduce the old one, and author/email/creator-info options will be honored. You meant to `t' (not to `nil'), as shown by lines 346--388 of `org-html.el': #+begin_src emacs-lisp (defcustom org-export-html-preamble t Non-nil means insert a preamble in HTML export. The format of the preamble is set as `org-export-html-preamble-format'. Setting :html-preamble in publishing projects will override this. :group 'org-export-html :type 'boolean) (defcustom org-export-html-preamble-format '((en h1 class=\title\%t/h1)) The format for the HTML preamble. %t stands for the title. If you need to use a \%\ character, you need to escape it like that: \%%\. :group 'org-export-html :type 'string) (defcustom org-export-html-postamble t Non-nil means insert a postamble in HTML export. The format of the postamble is set as `org-export-html-postamble-format'. Setting :html-postamble in publishing projects will override this. :group 'org-export-html :type 'boolean) (defcustom org-export-html-postamble-format '((en p class=\author\Author: %a (%e)/p p class=\date\Date: %d/p p class=\creator\Generated by %c/p p class=\xhtml-validation\%v/p )) The format for the HTML postamble. %a stands for the author. %e stands for the email(s). %d stands for the date. %c will be replaced by information about Org/Emacs. %v will be replaced by `org-export-html-validation-link'. If you need to use a \%\ character, you need to escape it like that: \%%\. :group 'org-export-html :type 'string) #+end_src Best regards, Seb -- Sébastien Vauban
Re: [O] Title page in latex export
Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
I am trying to write my thesis as per my university style. It requires
I use the \title{Thesis title} command before the
\begin{document}
...
\end{document}
Is there any way to do that? Thanks for any thoughts.
This is really a bug in your university's style. Lamport (p.21 of the
second edition) says:
The \maketitle command comes after the \begin{document}, usually
before any other text. The \title, \author, and \date commands can
come *anywhere* before the \maketitle.
[Emphasis added] \title etc. does not have to be in the
preamble. However, there are many styles out there that restrict the
placement of these macros to the preamble, just as your university's
style does (they probably cribbed from each other :-) ), so applying
Lawrence's patch is probably the best long term solution for org.
Nick
Re: [O] org google weather
Ian Barton li...@manor-farm.org wrote: Hi Ian, Ian Barton wrote: Has anybody tried adding the functionality of %%(diary-sunrise-sunset) (sunrise, sunset time and daylight hours) to the google weather code? I just have something like: #+CATEGORY: Day/Year %%(diary-day-of-year) #+CATEGORY: Sunrise %%(diary-sunrise-sunset) in one of my Agenda files. Sunrise then appears at sunrise time in my Agenda like: Sunrise: 6:53.. Sunrise (GMT), sunset 5:52pm (GMT) at Wilkesley (10:58 hours daylight) Do you have a way to get the sunset located on a line on its own (different line from the sunrise one)? That'd be even much nicer... No, but I would like one:) If there were separate diary functions for sunrise and sunset it would be easy. Maybe I need to look at the diary elisp and write my own separate functions. Quick hack just parsing the output of diary-sunrise-sunset. I added this early in my org-config file (which is sourced by .emacs) - modify latitude, longitude to taste: --8---cut here---start-8--- ;;; diary supplement - rich in Ca (setq calendar-latitude 42.3) (setq calendar-longitude -71.0) (defun diary-sunrise () (let ((dss (diary-sunrise-sunset))) (with-temp-buffer (insert dss) (goto-char (point-min)) (search-forward ,) (buffer-substring (point-min) (match-beginning 0) (defun diary-sunset () (let ((dss (diary-sunrise-sunset)) start end) (with-temp-buffer (insert dss) (goto-char (point-min)) (search-forward , ) (setq start (match-end 0)) (search-forward at) (setq end (match-beginning 0)) (goto-char start) (capitalize-word 1) (buffer-substring start end --8---cut here---end---8--- and this to one of my agenda files: --8---cut here---start-8--- #+CATEGORY: Weather %%(diary-sunrise) %%(diary-sunset) --8---cut here---end---8--- and I get: , | Friday 4 March 2011 | Weather: 6:16.. Sunrise (EST) |8:00.. | 10:00.. | 12:00.. | 14:00.. | 16:00.. | Weather:17:36.. Sunset (EST) | 18:00.. | 20:00.. ` Nick
Re: [O] Re: TODO state change from TODO to DONE blocked
Sébastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: Hi Bastien, Bastien wrote: I've a really weird exception occurring: change state from TODO to DONE is blocked... while I'm on a leaf of the Org tree!? Debugger entered--Lisp error: (error #(TODO state change from TODO to DONE blocked 23 27 (face org-todo) 31 35 (face org-done))) snip I could see in the description of that var that it could block state change if tasks were ordered and a previous one not done. But I never use the ordered property. ... Well, never, but well in that parent tree. Was it for test purpose? Did I have something else in mind? I dunno anymore, but that property was definitely the culprit. Doing so, I'm wondering: - if the output message could be updated to make it clear what the reason is, or can be? - why it allowed me to update the tasks state when I narrowed the buffer to that task only? Does that mean that *narrowing* somehow *drops the inherited properties*? If narrowing the buffer allows the state change when the parent (outside the narrowed region) has the ORDERED property - I think that's a bug that needs to be fixed. The behaviour shouldn't change if you narrow the buffer. -Bernt
Re: [O] How to escape characters in tables
Hi Ken,
2011/3/4 ken.willi...@thomsonreuters.com
On 3/3/11 9:07 PM, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
On Wed, 2 Mar 2011 09:25:57 -0600
ken.willi...@thomsonreuters.com wrote:
The issue is that I've got tables whose cells contain the '|'
character (it's a table of regular expressions), and I can't seem to
figure out how to escape it so that it doesn't mean a delimiter
between cells. Anyone have advice or a pointer to the docs I can't
seem to find?
I don't think you can.
I'm making slight progress, actually.
On StackOverflow
(
http://stackoverflow.com/questions/5144862/escape-pipe-character-in-org-mo
de), it was suggested to use the \vert{} character escape, which does
work.
However, since this is code (a regular expression), I want it to appear
monospaced, so I'm not out of the woods yet - here's a test case that
shows my intent:
| foo | =m/foo\vert{}foodfight/= |
The \vert{} seems not to work inside a =...= construction. Furthermore,
the =...= construction is problematic there because it conflicts with the
start-of-formula syntax.
=...= is used for code so it is printed as it written
You may use \texttt{}
| foo | \texttt{m\/foo\vert{}foodfight\/} |
I don't have emacs right now so I can test it... but it should work
CP
--
Ken Williams
Senior Research Scientist
Thomson Reuters
http://labs.thomsonreuters.com
[O] [PATCH] European date format
Greetings! I was annoyed that org only read the bassackwards american date format, and implemented european date format matching. I hope it's correct, it seems to work for dates with and without year. Regards, Jan org-patch.patch Description: Binary data
[O] Re: [Orgmode] Feature Request: attach link type
At Thu, 03 Mar 2011 11:18:06 +0100, Bastien b...@altern.org wrote: Hi Darlan, Darlan Cavalcante Moreira darc...@gmail.com writes: Using the functions already provided by org-attach I could get #+LINK: attach elisp:(org-open-file (org-attach-expand %s)) However, I always have to confirm the execution of the elisp code. You want to set `org-confirm-elisp-link-function' to nil. Thanks Bastien. I knew there was some variable to control this for all elisp links. I would prefer not to set this to nil, since I like the confirmation for other elisp links and since links for attached files are common for me I thought it could be a built-in link. But that's OK. Other useful things (just random thoughts) could be: - Perform some operation when a file is attached, such as replacing white-spaces in the file-name by underscores IMHO this goes beyond what org-attach.el should do: attach files. Besides, that would require even more confirmation steps. My common use scenario for org-attach is to store files associated to a sub-tree. For instance, when I receive a file by E-mail that I need to read I create a task for it and attach the file. I usually need to change the file name, since I don't like spaces and If would be practical if I could attach the file as it is and know that org-attach would store it the way I like. Is there a hook I could use to do this myself then? (I'm not a lisp programmer, but think I can google tips about how to do this). - When a file is attached a link to it could be stored in the kill ring, in case the user want to insert it in the current text. Alternatively, an interactive function to insert a link to an attached file (using the same completions we already get for opening attached files) would also be very handy. Yes, good idea. From latest git, set `org-attach-store-link-p' to `t' if you want a link to be stored in `org-stored-links' when attaching a file. This is even better then storing it in the kill ring. I noticed that the link points to the location of the original file and not to the location where it was attached (which is what thought it would do). Is this what you intended? Thanks, -- Bastien -- Darlan
Re: [O] Re: HTML export options are being ignored
Hi Sébastien, Sébastien Vauban wxhgmqzgw...@spammotel.com writes: You meant to `t' (not to `nil'), as shown by lines 346--388 of `org-html.el': No, I mean `nil' -- please check against the latest Org version. -- Bastien
Re: [O] [PATCH] Re: TODO state change from TODO to DONE blocked
Hi Sébastien, Sébastien Vauban wxhgmqzgw...@spammotel.com writes: - if the output message could be updated to make it clear what the reason is, or can be? diff --git a/lisp/org.el b/lisp/org.el index 3a07cfd..fb60bc6 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -10927,7 +10927,10 @@ For calling through lisp, arg is also interpreted in the following way: (run-hook-with-args-until-failure 'org-blocker-hook change-plist))) (if (interactive-p) - (error TODO state change from %s to %s blocked this state) + (error (concat TODO state change from %s to %s blocked + (because of undone child, or + parent with ORDERED property and undone prior sibling)) + this state) I'm not in favor of displaying such a long error message: I find it not easily readable, and it raises too many potential causes for the error. The user already knows about these various reasons by reading the docstring of `org-enforce-todo-dependencies', which defaults to `nil'. Thanks anyway for the patch! -- Bastien
Re: [O] Title page in latex export
Hi Nick, Nick Dokos nicholas.do...@hp.com writes: [Emphasis added] \title etc. does not have to be in the preamble. However, there are many styles out there that restrict the placement of these macros to the preamble, just as your university's style does (they probably cribbed from each other :-) ), so applying Lawrence's patch is probably the best long term solution for org. Thanks for the explanations -- I've now applied Lawrence's patch (thanks Lawrence!) -- Bastien
Re: [O] [PATCH] European date format
Jan Seeger jan.see...@thenybble.de wrote: Greetings! I was annoyed that org only read the bassackwards american date format, and implemented european date format matching. I hope it's correct, it seems to work for dates with and without year. It would help if you provided a few examples of what European format is. Deciphering long regexps is maybe fun the first time you do it, but after that it quickly loses its charm :-) BTW, if you (and I don't just mean Jan here) haven't tried re-builder, you should: add a few strings to a buffer, M-x re-builder and type in the regexp. It interactively and incrementally shows what matches. In any case, I tried to decipher your regexp and it seems to me that there is at least one (small) problem: a date without a year won't match without a final period. E.g. 4.3. == the fourth day of March, 2011 4.3 == does not match Thanks, Nick PS. Also, patches are just text, so please include them in the mail (or at least make sure that they are attached as text/plain or something similar, rather than application/octet-stream). Here's the patch for reference: --8---cut here---start-8--- diff --git a/lisp/org.el b/lisp/org.el index 3a07cfd..fa54d4e 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -14584,6 +14584,17 @@ user. (if ( year 100) (setq year (+ 2000 year))) (setq ans (replace-match (format %04d-%02d-%02d\\5 year month day) t nil ans))) +;; European date match +(when (string-match + ^ *\\(3[01]\\|0?[1-9]\\|[12][0-9]\\)\\.\\(0?[1-9]\\|1[012]\\)\\.\\([1-9][0-9][0-9][0-9]\\)? ans) + (setq year (if (match-end 3) +(string-to-number (match-string 3 ans)) + (progn (setq kill-year t) + (string-to-number (format-time-string %Y + day (string-to-number (match-string 1 ans)) + month (string-to-number (match-string 2 ans)) + ans (replace-match (format %04d-%02d-%02d\\5 year month day) +t nil ans))) ;; Help matching am/pm times, because `parse-time-string' does not do that. ;; If there is a time with am/pm, and *no* time without it, we convert ;; so that matching will be successful. --8---cut here---end---8---
Re: [O] [PATCH] European date format
Hey! Ah, I'm sorry. Yeah, european format is Day.Month.Year (optional). And the final trailing dot is intentional, because I think it looks nicer (and I think it simplifies the regex). Also, my last mail was missing a smiley, I was only kidding of course. Regards, Jan
[Accepted] [O] Title page in latex export
Patch 649 (http://patchwork.newartisans.com/patch/649/) is now Accepted.
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3Cm34o7j5d5r.fsf%40e4300lm.epcc.ed.ac.uk%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: [O] Title page in latex export
Date: Fri, 04 Mar 2011 16:38:08 -
From: Lawrence Mitchell we...@gmx.li
X-Patchwork-Id: 649
Message-Id: m34o7j5d5r@e4300lm.epcc.ed.ac.uk
To: emacs-orgmode@gnu.org
Suvayu Ali wrote:
Hi Camille,
Thanks a lot for your response.
On Fri, 4 Mar 2011 11:48:39 +0100
Camille persson camille.pers...@gmail.com wrote:
Hi,
I think that what it already does
I don't think it does that. e.g.
Try this patch to org-latex.el:
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 19baa40..4db38d6 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -1352,9 +1352,6 @@ OPT-PLIST is the options plist for current buffer.
(org-export-apply-macros-in-string org-export-latex-append-header)
;; define alert if not yet defined
\n\\providecommand{\\alert}[1]{\\textbf{#1}}
- ;; beginning of the document
- \n\\begin{document}\n\n
- ;; insert the title
(format
\n\n\\title{%s}\n
;; convert the title
@@ -1374,6 +1371,9 @@ OPT-PLIST is the options plist for current buffer.
(format-time-string
(or (plist-get opt-plist :date)
org-export-latex-date-format)))
+ ;; beginning of the document
+ \n\\begin{document}\n\n
+ ;; insert the title
;; insert the title command
(when (string-match \\S- title)
(if (string-match %s org-export-latex-title-command)
Re: [O] using org-mode with MS Outlook
Hi Dirk-Jan, Dirk-Jan C. Binnema djcb.b...@gmail.com writes: The approach is a bit fragile, and there are quite a few cases which are not handled very well; still it may be useful; so find attached org-exchange-capture.el; ideas for improvements are welcome. I'm not using MS Exchange myself, but I hope your code is useful for others. Would you consider putting it on Worg/org-hacks.org? I can do it for you if you want. Thanks for sharing it! -- Bastien
Re: [O] org google weather
Hi Nick, Nick Dokos nicholas.do...@hp.com writes: Quick hack just parsing the output of diary-sunrise-sunset. Nice one -- a good candidate for Worg/org-hacks.org ;) -- Bastien
Re: [O] scheduling items question
Hi Stuart, stuart smclean0...@gmail.com writes: ** class Monday ** class Wednesday ** class Friday I would use a weekly repeater for these tasks. , | * class Monday | SCHEDULED: 2011-03-07 lun. +1w | | * class Wednesday | SCHEDULED: 2011-03-09 mer. +1w | | * class Friday | SCHEDULED: 2011-03-11 ven. +1w ` ... but do you really need to take the *habit* of attending class?? :) -- Bastien
Re: [O] org google weather
On 4 Mar 2011, at 17:38, Nick Dokos wrote: Quick hack just parsing the output of diary-sunrise-sunset. ... Nice! Is there a way to get this inserted only into the day view, but not into the week view? In fact, I would like to have that choice for agenda items in general. It makes sense (to me at least) to have more information in the day view than in the week view. Konrad.
Re: [O] [PATCH] European date format
Jan Seeger jan.see...@thenybble.de wrote: Hey! Ah, I'm sorry. Yeah, european format is Day.Month.Year (optional). And the final trailing dot is intentional, because I think it looks nicer (and I think it simplifies the regex). Also, my last mail was missing a smiley, I was only kidding of course. You mean about the bassackwards comment? I think you got it exactly right :-) The problem with the required final trailing dot (if you want to leave out the year) is that it is not obvious - at least to me: the equivalent ISO would be -03-04 and the equivalent American would be 3/4/ which look horrible - however, I don't know what the general practice is in Europe. Nick PS. BTW, another reason to avoid application/octet-stream is that patches sent to the list are saved in Patchwork - but not if they are application/octet-stream: see the thread http://thread.gmane.org/gmane.emacs.orgmode/25513 and in particular http://thread.gmane.org/gmane.emacs.orgmode/25513/focus=25560 In this case, my reposting of your patch inline has archived it to Patchwork so you don't need to do it again, but keep it in mind if you submit patches in the future.
Re: [O] [OT] Custom inline reply quotes
Jeff Horn jrhorn...@gmail.com writes: JH Hey orgsters, JH What MUA/package/magic... Supercite does for instance, but you will be hated by almost everyone not using supercite. 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
Re: [O] Title page in latex export
Hi Camille,
On Fri, 4 Mar 2011 15:17:58 +0100
Camille persson camille.pers...@gmail.com wrote:
Hi Suvayu,
Do you use the lastest update of org-mode ?
cause it works perfectly for me without any patch actually...
Yes, my org-mode is less than a day old. But I didn't have any LaTeX
customisations in my setup. I am not sure why our exports are
different. However with Lawerence's patch things work very smoothly.
to use your university's custom style, you need to put it in your
texmf directory and use the following header lines:
#+LATEX_CLASS: MyUnivThesis
#+LATEX_CLASS_OPTIONS: [options...]
and then customize your .emacs file (or a file in your .emacs.d/) as
following
(add-to-list 'org-export-latex-classes
'(MyUnivThesis
\\documentclass{univstyle}
(\\part{%s} . \\part*{%s})
(\\chapter{%s} . \\chapter*{%s})
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s}))
Thanks for pointing it out. This will be very helpful. :)
See http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-6
Yours,
CP
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Title page in latex export
Hi Nick,
On Fri, 04 Mar 2011 10:45:08 -0500
Nick Dokos nicholas.do...@hp.com wrote:
This is really a bug in your university's style. Lamport (p.21 of the
second edition) says:
The \maketitle command comes after the \begin{document}, usually
before any other text. The \title, \author, and \date commands can
come *anywhere* before the \maketitle.
[Emphasis added] \title etc. does not have to be in the
preamble. However, there are many styles out there that restrict the
placement of these macros to the preamble, just as your university's
style does (they probably cribbed from each other :-) ), so applying
Lawrence's patch is probably the best long term solution for org.
Thanks a lot for clarifying that. :)
Nick
--
Suvayu
Open source is the future. It sets us free.
Re: [O] org google weather
Konrad Hinsen konrad.hin...@fastmail.net wrote: Is there a way to get this inserted only into the day view, but not into the week view? In fact, I would like to have that choice for agenda items in general. It makes sense (to me at least) to have more information in the day view than in the week view. Not that I know of, which means one of two things: it's there but I don't know about it (something that has happened many times in the past with org) or it's not there and Carsten will have it implemented by tomorrow morning :-) Nick PS. FWIW, I'd like that feature too...
[O] Re: [PATCH] European date format
ND == Nick Dokos nicholas.do...@hp.com writes: ND The problem with the required final trailing dot (if you want to ND leave out the year) is that it is not obvious - at least to me: ND the equivalent ISO would be -03-04 and the equivalent American ND would be 3/4/ which look horrible - however, I don't know what ND the general practice is in Europe. The dots are not separators, they mark ordinal numbers. And at least here in Czech Republic the correct typeset form is e.g. 4. 3. 2011 although the compact form 4.3.2011 is often used.
Re: [O] Re: [PATCH] European date format
Milan Zamazal p...@zamazal.org wrote: ND == Nick Dokos nicholas.do...@hp.com writes: ND The problem with the required final trailing dot (if you want to ND leave out the year) is that it is not obvious - at least to me: ND the equivalent ISO would be -03-04 and the equivalent American ND would be 3/4/ which look horrible - however, I don't know what ND the general practice is in Europe. The dots are not separators, they mark ordinal numbers. And at least here in Czech Republic the correct typeset form is e.g. 4. 3. 2011 although the compact form 4.3.2011 is often used. Interesting - I never thought of that. So I take it that if the year is left out (implying the current year), the trailing dot is included because it is significant: the fourth day of the third month - is that correct? Thanks, Nick
Re: [O] org google weather
At Fri, 04 Mar 2011 08:40:23 +, Ian Barton wrote: On 03/03/11 21:37, Simon Brown wrote: Has anybody tried adding the functionality of %%(diary-sunrise-sunset) (sunrise, sunset time and daylight hours) to the google weather code? I just have something like: #+CATEGORY: Day/Year %%(diary-day-of-year) #+CATEGORY: Sunrise %%(diary-sunrise-sunset) That's where I am at the moment, with the weather forecast, sunrise and sunset times on different lines. I was wondering if the two could be integrated to make a one line weather forecast, sunrise and sunset times. ? eg. Location: (icon) Chance of Rain, [-1,6] ℃, Sunrise 0658 Sunset 1759 1101 hrs of daylight Simon
Re: [O] Re: [PATCH] European date format
On Fri, 04 Mar 2011 16:21:47 -0500, Nick Dokos nicholas.do...@hp.com wrote: Milan Zamazal p...@zamazal.org wrote: The dots are not separators, they mark ordinal numbers. And at least here in Czech Republic the correct typeset form is e.g. 4. 3. 2011 although the compact form 4.3.2011 is often used. Interesting - I never thought of that. So I take it that if the year is left out (implying the current year), the trailing dot is included because it is significant: the fourth day of the third month - is that correct? Same in German. When you pronounce 3.4., you'd say dritter vierter, i.e. third (of) fourth.
Re: [O] Re: TODO state change from TODO to DONE blocked
Hi Bernt, Bernt Hansen wrote: Sébastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: Bastien wrote: I've a really weird exception occurring: change state from TODO to DONE is blocked... while I'm on a leaf of the Org tree!? Debugger entered--Lisp error: (error #(TODO state change from TODO to DONE blocked 23 27 (face org-todo) 31 35 (face org-done))) snip I could see in the description of that var that it could block state change if tasks were ordered and a previous one not done. But I never use the ordered property. ... Well, never, but well in that parent tree. Was it for test purpose? Did I have something else in mind? I dunno anymore, but that property was definitely the culprit. Doing so, I'm wondering: - if the output message could be updated to make it clear what the reason is, or can be? - why it allowed me to update the tasks state when I narrowed the buffer to that task only? Does that mean that *narrowing* somehow *drops the inherited properties*? If narrowing the buffer allows the state change when the parent (outside the narrowed region) has the ORDERED property - I think that's a bug that needs to be fixed. Yes, it does. That has been my workaround once -- before searching more to find the root cause. The behaviour shouldn't change if you narrow the buffer. We share the same point of view. Best regards, Seb -- Sébastien Vauban
Re: [O] [PATCH] Re: TODO state change from TODO to DONE blocked
Hi Bastien, Bastien wrote: Hi Sébastien, Sébastien Vauban wxhgmqzgw...@spammotel.com writes: - if the output message could be updated to make it clear what the reason is, or can be? diff --git a/lisp/org.el b/lisp/org.el index 3a07cfd..fb60bc6 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -10927,7 +10927,10 @@ For calling through lisp, arg is also interpreted in the following way: (run-hook-with-args-until-failure 'org-blocker-hook change-plist))) (if (interactive-p) - (error TODO state change from %s to %s blocked this state) + (error (concat TODO state change from %s to %s blocked + (because of undone child, or + parent with ORDERED property and undone prior sibling)) + this state) I'm not in favor of displaying such a long error message: I find it not easily readable, and it raises too many potential causes for the error. I know, too long. The user already knows about these various reasons by reading the docstring of `org-enforce-todo-dependencies', which defaults to `nil'. It was a matter of allowing people to loose less time next time they'll see that message. Thanks anyway for the patch! Not a problem. Just discard it. Best regards, Seb -- Sébastien Vauban
Re: [O] Re: Feature Request: attach link type
Hi Darlan and Bastien, Darlan Cavalcante Moreira wrote: Other useful things (just random thoughts) could be: - Perform some operation when a file is attached, such as replacing white-spaces in the file-name by underscores IMHO this goes beyond what org-attach.el should do: attach files. Besides, that would require even more confirmation steps. My common use scenario for org-attach is to store files associated to a sub-tree. For instance, when I receive a file by E-mail that I need to read I create a task for it and attach the file. I usually need to change the file name, since I don't like spaces and If would be practical if I could attach the file as it is and know that org-attach would store it the way I like. Is there a hook I could use to do this myself then? (I'm not a lisp programmer, but think I can google tips about how to do this). Just to comment on that point: reworking the filename is exactly what Gnus do with attachment files, once you want to save them. It (optionally) do whatever is needed to make them better, such as removing spaces, replacing accents, etc... Best regards, Seb -- Sébastien Vauban
Re: [O] org google weather
Simon Brown li...@700c.org wrote: At Fri, 04 Mar 2011 08:40:23 +, Ian Barton wrote: On 03/03/11 21:37, Simon Brown wrote: Has anybody tried adding the functionality of %%(diary-sunrise-sunset) (sunrise, sunset time and daylight hours) to the google weather code? I just have something like: #+CATEGORY: Day/Year %%(diary-day-of-year) #+CATEGORY: Sunrise %%(diary-sunrise-sunset) That's where I am at the moment, with the weather forecast, sunrise and sunset times on different lines. I was wondering if the two could be integrated to make a one line weather forecast, sunrise and sunset times. ? eg. Location: (icon) Chance of Rain, [-1,6] ℃, Sunrise 0658 Sunset 1759 1101 hrs of daylight Just write your own function to take the individual results and concatenate them, e.g. --8---cut here---start-8--- (defun full-catastrophe () (format %s :: %s (org-google-weather) (diary-sunrise-sunset))) --8---cut here---end---8--- and add --8---cut here---start-8--- %%(full-catastrophe) --8---cut here---end---8--- to some agenda file. Nick
[O] Re: [Orgmode] [PATCH] org-agenda: rewrite mode-line
Hi, Carsten Dominik carsten.domi...@gmail.com writes: I like the patch, but since it is not critical it remains on ice until :eval is supported by XEmacs. Michael, it would be nice if you could put :eval into XEmacs so that we can use this improved code for the mode line. Please make sure to let us know when this is done. Michael, did you had time to progress on this? Thanks! -- Bastien
Re: [O] scheduling items question
On Fri, Mar 4, 2011 at 1:31 PM, Bastien b...@altern.org wrote: Hi Stuart, stuart smclean0...@gmail.com writes: ** class Monday ** class Wednesday ** class Friday I would use a weekly repeater for these tasks. , | * class Monday | SCHEDULED: 2011-03-07 lun. +1w | | * class Wednesday | SCHEDULED: 2011-03-09 mer. +1w | | * class Friday | SCHEDULED: 2011-03-11 ven. +1w ` ... but do you really need to take the *habit* of attending class?? I wonder why the OP uses a habit of these classes. They'd probably work better as just regular appointments, like this: * Class Monday 2011-03-04 Fri +1w Personally, I use org-habit to /hide/ a headline until the day it's due. I love that feature, and use it for 50% of my scheduled things. --Nate
Re: [O] org google weather
Nick Dokos nicholas.do...@hp.com wrote: Just write your own function to take the individual results and concatenate= them, e.g. (defun full-catastrophe () (format %s :: %s (org-google-weather) (diary-sunrise-sunset))) and add %%(full-catastrophe) to some agenda file. BTW, I noticed that semicolons followed by spaces cause trouble: --8---cut here---start-8--- (defun full-catastrophe () (format a; b)) --8---cut here---end---8--- puts a on one agenda line and b in another. It does not happen if there is no space after the semicolon. And in case you are wondering, I saw it when trying Ian's (diary-day-of-year) example, which includes ; in its output. Nick
[O] [feature request] org-post-export-hook
Would it be trivial to add a post-export hook? If so, it would be helpful for me. I've been experimenting with latexmk for document compilation. If I add `latexmk -CA` (it cleans extraneous files) to the command sequence for `org-latex-to-pdf-process`, I trigger an annoying notification that the PDF file wasn't produced, and the *Org Export PDF Output* (or whatever) buffer is overwritten with this new command's output (not very interesting). Perhaps it would be best to have a general `org-post-export-hook` and specific `org-post-latex-export-hook` and `org-post-html-export-hook`. It wouldn't make sense to run `latexmk -CA` when producing a webpage, afterall. -- Jeffrey Horn http://www.failuretorefrain.com/jeff/
Re: [O] org google weather
At Fri, 04 Mar 2011 17:05:55 -0500, Nick Dokos wrote: Simon Brown li...@700c.org wrote: At Fri, 04 Mar 2011 08:40:23 +, Ian Barton wrote: On 03/03/11 21:37, Simon Brown wrote: Has anybody tried adding the functionality of %%(diary-sunrise-sunset) (sunrise, sunset time and daylight hours) to the google weather code? I just have something like: #+CATEGORY: Day/Year %%(diary-day-of-year) #+CATEGORY: Sunrise %%(diary-sunrise-sunset) That's where I am at the moment, with the weather forecast, sunrise and sunset times on different lines. I was wondering if the two could be integrated to make a one line weather forecast, sunrise and sunset times. ? eg. Location: (icon) Chance of Rain, [-1,6] ℃, Sunrise 0658 Sunset 1759 1101 hrs of daylight Just write your own function to take the individual results and concatenate them, e.g. --8---cut here---start-8--- (defun full-catastrophe () (format %s :: %s (org-google-weather) (diary-sunrise-sunset))) --8---cut here---end---8--- and add --8---cut here---start-8--- %%(full-catastrophe) --8---cut here---end---8--- Excellent, I like your style :-) Simon
[O] Re: [feature request] org-post-export-hook
On Fri, Mar 4, 2011 at 5:40 PM, Jeff Horn jrhorn...@gmail.com wrote: I've been experimenting with latexmk for document compilation. If I add `latexmk -CA` (it cleans extraneous files) to the command sequence for `org-latex-to-pdf-process`, I trigger an annoying notification that the PDF file wasn't produced, and the *Org Export PDF Output* (or whatever) buffer is overwritten with this new command's output (not very interesting). Oops! Adding the `-CA` flag instead of `-c` wipes out pdf files! Still, the output log buffer is destroyed, and that's not good for me (I make many errors when typing up tables, drawing tikz pictures, etc.). -- Jeffrey Horn http://www.failuretorefrain.com/jeff/
Re: [O] org google weather
Hi Nick, Nick Dokos wrote: Ian Barton li...@manor-farm.org wrote: Ian Barton wrote: Has anybody tried adding the functionality of %%(diary-sunrise-sunset) (sunrise, sunset time and daylight hours) to the google weather code? I just have something like: #+CATEGORY: Day/Year %%(diary-day-of-year) #+CATEGORY: Sunrise %%(diary-sunrise-sunset) in one of my Agenda files. Sunrise then appears at sunrise time in my Agenda like: Sunrise: 6:53.. Sunrise (GMT), sunset 5:52pm (GMT) at Wilkesley (10:58 hours daylight) Do you have a way to get the sunset located on a line on its own (different line from the sunrise one)? That'd be even much nicer... No, but I would like one:) If there were separate diary functions for sunrise and sunset it would be easy. Maybe I need to look at the diary elisp and write my own separate functions. Quick hack just parsing the output of diary-sunrise-sunset. Excellent hack, for at least 2 reasons: the feature itself, and showing us the way how to enhance the agenda... Thanks a lot. I added this early in my org-config file (which is sourced by .emacs) [...] and this to one of my agenda files: #+CATEGORY: Weather %%(diary-sunrise) %%(diary-sunset) and I get: , | Friday 4 March 2011 | Weather: 6:16.. Sunrise (EST) |8:00.. | 10:00.. | 12:00.. | 14:00.. | 16:00.. | Weather:17:36.. Sunset (EST) | 18:00.. | 20:00.. ` Because of this: #+begin_src emacs-lisp (setq org-agenda-default-appointment-duration 60) #+end_src I get: , | 2011-03-05 Sat |0:01-1:01 now | Weather: 7:18-8:18 Sunrise (+0100) |8:00-9:00 | 10:00-11:00 | 12:00-13:00 | 14:00-15:00 | 16:00-17:00 | 18:00-19:00 | Weather:18:24-19:24 Sunset (+0100) ` i.e, a not-that-clear indication of when the sunrise/sunset is supposed to happen. In this case, it's clearly a one-minute event. Is there, then, a way to avoid the + 1 hour range computation for it, while keeping the above variable for other common tasks? Best regards, Seb -- Sébastien Vauban
Re: [O] Re: [PATCH] European date format
Hi Milan, Milan Zamazal wrote: ND == Nick Dokos nicholas.do...@hp.com writes: ND The problem with the required final trailing dot (if you want to ND leave out the year) is that it is not obvious - at least to me: ND the equivalent ISO would be -03-04 and the equivalent American ND would be 3/4/ which look horrible - however, I don't know what ND the general practice is in Europe. The dots are not separators, they mark ordinal numbers. And at least here in Czech Republic the correct typeset form is e.g. 4. 3. 2011 although the compact form 4.3.2011 is often used. I don't think we have a real European format: in Belgium, a date is 16/03/2011, or 16/3/2011 for the sixteenth of March. So, here, the common separator is the dash, but the order is well day/month/year... Best regards, Seb -- Sébastien Vauban
Re: [O] org google weather
Sébastien Vauban wxhgmqzgw...@spammotel.com wrote: Because of this: #+begin_src emacs-lisp (setq org-agenda-default-appointment-duration 60) #+end_src I get: , | 2011-03-05 Sat |0:01-1:01 now | Weather: 7:18-8:18 Sunrise (+0100) |8:00-9:00 | 10:00-11:00 | 12:00-13:00 | 14:00-15:00 | 16:00-17:00 | 18:00-19:00 | Weather:18:24-19:24 Sunset (+0100) ` i.e, a not-that-clear indication of when the sunrise/sunset is supposed to happen. In this case, it's clearly a one-minute event. Is there, then, a way to avoid the + 1 hour range computation for it, while keeping the above variable for other common tasks? Not that I know of, but maybe a generalization of the feature that Konrad was looking for might be what's needed: give properties to agenda entry generators, so e.g. they cause the agenda entry to be only displayed today, or to be of a given duration (0 in this case, 10 mins in some other case, 1 hour by default), etc. The difficult thing is to make it general enough, concise enough and undestandable enough for mere mortals to have a chance. Nick
Re: [O] [feature request] org-post-export-hook
Hi Jeff, Jeff Horn jrhorn...@gmail.com writes: Would it be trivial to add a post-export hook? If so, it would be helpful for me. I've been experimenting with latexmk for document compilation. If I add `latexmk -CA` (it cleans extraneous files) to the command sequence for `org-latex-to-pdf-process`, I trigger an annoying notification that the PDF file wasn't produced, and the *Org Export PDF Output* (or whatever) buffer is overwritten with this new command's output (not very interesting). Perhaps it would be best to have a general `org-post-export-hook` and specific `org-post-latex-export-hook` and `org-post-html-export-hook`. It wouldn't make sense to run `latexmk -CA` when producing a webpage, afterall. See org-export-latex-final-hook, org-export-latex-after-save-hook and sisters. C-h v org-export-hook TAB TAB to see all of them. -- Bastien
Re: [O] scheduling items question
Nathan Neff nathan.n...@gmail.com writes: I wonder why the OP uses a habit of these classes. They'd probably work better as just regular appointments, like this: Well, I was actually trying to make a joke... when I was young, we were forced to go to class -- this was not a habit we had to take :) * TODO Make better jokes SCHEDULED: 2011-03-05 sam. ++1d :PROPERTIES: :Effort: 2:30 :END: -- Bastien
[O] Re: [Babel] Handling of errors when using Ledger
Hi Eric, Seb and any other ledger users, Is anyone using a version of ledger that does not support reading from stdin with -f - ? Thanks, Dan Eric S Fraga e.fr...@ucl.ac.uk writes: Dan Davison dandavis...@gmail.com writes: [...] Hi Eric, I've asked on the ledger list and the 3.0 (and perhaps some older) versions of ledger do support -f - to read from stdin. Could you try this version of the patch? I was about to say that I could not because the most up to date version on Debian (testing) is 2.6.2 and this version does not support the -f - option. However, I have just noticed that version 3.0.0 is now in Debian experimental. I will have a look to see what kind of repercussions there may be from installing that version on my systems and I will get back to you (but probably not until after xmas...).
[O] typo in org.texi
diff --git a/doc/org.texi b/doc/org.texi index 50febbc..bc66319 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -2282,7 +2282,7 @@ operator that looks like this: @end example @noindent -and allows relative relative references, i.e. references relative to the +and allows relative references, i.e. references relative to the row/column of the field whose value is being computed. These relative references make it possible to store a formula only once and use it in many fields without copying and modifying it. Nick
[Accepted] [O] typo in org.texi
Patch 652 (http://patchwork.newartisans.com/patch/652/) is now Accepted. Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C9447.1299285313%40alphaville.usa.hp.com%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: [O] typo in org.texi Date: Sat, 05 Mar 2011 05:35:13 - From: Nick Dokos nicholas.do...@hp.com X-Patchwork-Id: 652 Message-Id: 9447.1299285...@alphaville.usa.hp.com To: emacs-orgmode@gnu.org Cc: nicholas.do...@hp.com Nick diff --git a/doc/org.texi b/doc/org.texi index 50febbc..bc66319 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -2282,7 +2282,7 @@ operator that looks like this: @end example @noindent -and allows relative relative references, i.e. references relative to the +and allows relative references, i.e. references relative to the row/column of the field whose value is being computed. These relative references make it possible to store a formula only once and use it in many fields without copying and modifying it.
[O] Why does a column's name need to start with a letter? Changed source with no perceivable side-effects
Greetings, First and foremost, I must say I'm a new Org-mode user... as well as a new emacs user... and have only limited experience with lisp. I'm using a table in org-mode as a database, from which I retrieve information as needed from other tables. This database stores multiples components with names starting by numbers and with the character - in them. For example: 10K-AN-D8. I want to be able to refer to its column with $10K-AN-D8. Yet, this is impossible at the moment. I've looked in org-table.el and found, at line 2038: (if (string-match ^[a-zA-Z][a-zA-Z0-9]*$ name) which, once replaced by this: (if (string-match ^[-_a-zA-Z0-9]*$ name) Provides me with the ability to name (and refer) columns in any way I want. However, I'm reluctant to use this feature; surely there was a reason for this limitation. Could someone point it out for me? If there's no reason not to name columns as we want, perhaps it could be modified in future versions? Thank you very much in advance! Christian
Re: [O] Why does a column's name need to start with a letter? Changed source with no perceivable side-effects
Hi Christian, On 5.3.2011, at 04:35, Frozenlock wrote: Greetings, First and foremost, I must say I'm a new Org-mode user... as well as a new emacs user... and have only limited experience with lisp. I'm using a table in org-mode as a database, from which I retrieve information as needed from other tables. This database stores multiples components with names starting by numbers and with the character - in them. For example: 10K-AN-D8. I want to be able to refer to its column with $10K-AN-D8. Yet, this is impossible at the moment. I've looked in org-table.el and found, at line 2038: (if (string-match ^[a-zA-Z][a-zA-Z0-9]*$ name) which, once replaced by this: (if (string-match ^[-_a-zA-Z0-9]*$ name) Provides me with the ability to name (and refer) columns in any way I want. However, I'm reluctant to use this feature; surely there was a reason for this limitation. Could someone point it out for me? This is limitation is present to disambiguate formulas. In you example $10K-AN-D8, D8 is already a field reference, so Org does not know if you mean $10K-AN - @8$4. Furthermore, you could easily arrive at variables like $10-AN-D8, and then what should the $10 mean? Of cause one could disambiguate heuristically by checking which names have been defined. In fact, name replacement happens first, and this is why your patch appears to work. But the side effect would be that introducing new names could change the interpretation of an existing equation. All this is unstable and unpredictable. Hope this makes it clear. - Carsten
Re: [O] [PATCH] European date format
Nick Dokos nicholas.do...@hp.com writes: 4.3. == the fourth day of March, 2011 4.3 == does not match As it should, IMHO. This format is relying on interpreting dates as ordinals (fourth day of the third month). Also there'd be no way for a regex to distinguish some dates from some FP numbers, at least when the point is, well, . (in Germany at least it would be ,). But really, there isn't any european date format that I'm aware of and the only standard date format is ISO8601:2004. If you use the extended format (with the dashes), dates are easily recognizable and most important of all there are no ambiguities. the equivalent ISO would be -03-04 No, this has nothing to do with ISO dates. Dropping must always occur from the least significant part, so you can't leave out the year. Truncating the year designator to two digits was allowed in a former version by agreement, but has been eliminated from the standard, BTW. Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
