Re: [O] Attributes on HTML tables?
Hi François, François Pinard writes: > #+CAPTION: This is a table with lines around and between cells > #+ATTR_HTML: border="2" rules="all" frame="border" You need to use :options now: #+CAPTION: This is a table with lines around and between cells #+ATTR_HTML: :options border="2" rules="all" frame="border" We are in the process of documenting this. -- Bastien
Re: [O] CSS link in html export for v. 7.9.3e woes
François Pinard writes: > There does not seem to be any reference to HTML_STYLE in the Org manual. > (Org version 7.9.3e (7.9.3e-1751-g8c47da) — taken this morning). I guess Sébastien meant #+HTML_HEAD -- #+HTML_STYLE does not exist anymore. -- Bastien
Re: [O] VCard export problems
Hi Simon, Simon Thum writes: > I now get: This should be fixed by Feng patch that I just applied, thanks for reporting it. -- Bastien
Re: [O] Inconsistent handling of html images and image links
Hi Dieter, Dieter Wilhelm writes: > before 8pre images [[file:example.png]] where imported left aligned into > html now they are centred. I don't see this. Maybe you configure the the #figure class in your CSS so that figures are centered? > Image links > [[http://example.com][file:example.png]] are *still* imported left > aligned!? The first link you quote is a figure, the second link is a link with an image as a description -- so I think using the #figure class for the first one is relevant, while using a paragraph for the second one is good. Let me know, -- Bastien
Re: [O] Fix bugs introduced by "[patch] add 'tel' and 'note' property'
Hi Feng, Feng Shu writes: > From 4eb305cdf2f7c59b8e014514c0409d4da2eb9eab Mon Sep 17 00:00:00 2001 > From: Feng Shu > Date: Sun, 7 Apr 2013 11:12:09 +0800 > Subject: [PATCH] [PATCH] org-contacts.el , fix bugs about 'tel and 'note > properties Applied, thanks. -- Bastien
Re: [O] Effort Per Day
Thank you. Appreciate your help. - Daya On Thu, Apr 4, 2013 at 6:08 AM, Bastien wrote: > Hello, > > daya writes: > > > There are some tasks on which I would like spend a specified time of the > day. I > > would like to set a per-day effort on these tasks. The current effort > system > > seem to support effort per task, not effort per day. What is the > recommended > > way of doing this? > > Using a daily repeater for your task should be enough. > > Also check `org-clock-mode-line-total' for more options. > > HTH, > > -- > Bastien >
Re: [O] Does '#+OPTIONS LaTeX:dvipng' deprecated in 8.0 pre or a bug?
Hello,
** Nicolas Goaziou [2013-04-06 22:58:43 +0200]:
> Hello,
> Vladimir Lomov writes:
>> Hello, the following simple Org document
>> #+BEGIN_SRC org
>> ,#+OPTIONS: LaTeX:dvipng ^:{}
>> This is small example $\exp^{\imath\phi}=\cos\phi+\imath\sin\phi$.
>> #+END_SRC
>> gives me wrong HTML export, see attached html file.
> It should be #+OPTIONS: tex:dvipng
Thank you Nicolas.
---
WBR, Vladimir Lomov
--
The Ranger isn't gonna like it, Yogi.
[O] Fix bugs introduced by "[patch] add 'tel' and 'note' property'
>From 4eb305cdf2f7c59b8e014514c0409d4da2eb9eab Mon Sep 17 00:00:00 2001 From: Feng Shu Date: Sun, 7 Apr 2013 11:12:09 +0800 Subject: [PATCH] [PATCH] org-contacts.el , fix bugs about 'tel and 'note properties * contrib/lisp/org-contacts.el (org-contacts-vcard-format): fix bug prvious intruduced ,add 'tel and 'note --- contrib/lisp/org-contacts.el |2 ++ 1 个文件被修改，插入 2 行(+) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index f529014..65eeea8 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -834,6 +834,8 @@ to do our best." (name (org-contacts-vcard-escape (car contact))) (n (org-contacts-vcard-encode-name name)) (email (cdr (assoc-string org-contacts-email-property properties))) + (tel (cdr (assoc-string org-contacts-tel-property properties))) + (note (cdr (assoc-string org-contacts-note-property properties))) (bday (org-contacts-vcard-escape (cdr (assoc-string org-contacts-birthday-property properties (addr (cdr (assoc-string org-contacts-address-property properties))) (nick (org-contacts-vcard-escape (cdr (assoc-string org-contacts-nickname-property properties -- 1.7.10.4 --
[O] Attributes on HTML tables?
Hi, Org people. I took a few hours today to move the Org generation for a few of my Web pages to the new exporter, and after a bit of debugging to understand how some changes were meant, got the impression that it mainly works! I'll have to wander around when I'll find some more free time, looking at the generated pages, to check that everything is OK. There is one little thing that does not seem to work, but I do not remember if it worked with the old exporter. The Org manual says: 12.5.5 Tables - Org mode tables are exported to HTML using the table tag defined in `org-html-table-tag'. The default setting makes tables without cell borders and frame. If you would like to change this for individual tables, place something like the following before the table: #+CAPTION: This is a table with lines around and between cells #+ATTR_HTML: border="2" rules="all" frame="border" Captions work indeed, but I do not see that attributes are transported on the generated element. It seems to be always produced with the exact value of org-html-table-tag. François
[O] generic page breaks for export?
It seems like enough of org's export formats have the concept of page breaks that a generic syntax might be warranted -- I'm finding myself doing lots of exporting to multiple formats. What do people think of that? Emacs already has a convention of using ascii 12 as a page delimiter (though control characters in the buffer look ugly), or we could introduce something like #+PAGEBREAK, or perhaps both. If this seems desirable, I'll take a stab at a patch. Eric
Re: [O] Latex export of longtable with multiline heading
At Sat, 6 Apr 2013 13:07:03 -0500, John Hendy wrote: > > What's the output of =M-x org-version= ? Hi John, I was using 7.9.2. Following your suggestions, I upgraded to 8.0-pre, and switched to the new syntax for selecting longtable. It's all perfect now, thanks, very much appreciated! cheers, Simon
Re: [O] Org-mode outside Org-mode
Thorsten Jolitz writes: > Samuel Wales writes: > > Hi Samuel, > >> IIUC, I don't think this is related. The idea is not to edit source >> code in Org buffers, and it is not to use a Navi buffer or to do >> navigation. >> >> The idea is to be in my-lisp.el, and do C-c ', and get to a canonical >> entry in my-org.org, then do C-c ' again and get back to my-lisp.el. >> That could be handy. For jumping back and for by function name, the following simple implementation might be sufficient. It relies on file local variables to know which src and Org-mode files are related to each other. org-src-jump.el Description: application/emacs-lisp Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Highlighting bug with org-agenda-set-restriction-lock
Bastien writes:
> Bernt Hansen writes:
>
>> I've noticed some differences since upgrading for creating headlines but
>> I haven't checked if this is due to my local setup yet.
>
> Feel free to throw all oddities that you notice, even with no deep
> test, it will help a lot.
>
>> Here is what I'm currently experiencing:
>>
>> I used to be able to just have a bunch of lines likes this
>>
>> ,
>> | one
>> | two
>> | three
>> | four
>> `
>>
>> and M-S-RET in the first column would create a TODO headline with this
>> as the heading
>>
>> ie.
>>
>> ,
>> | * TODO one
>> | two
>> | three
>> | four
>> `
>>
>> but now it seems to jump past the line before creating the heading.
>>
>> ,
>> | one
>> |
>> | * TODO
>> | two
>> | three
>> | four
>> `
>
> I get the correct behavior with emacs -Q and latest master, so it must
> surely be in your setup.
>
>> I have a heading hook that runs and inserts a timestamp when headings
>> are created so using this as a workaround and converting this to a list
>> with C-u C-c - and then to headings with C-c * doesn't give me the
>> result I want (inactive timestamps on all headings that were created)
Hi Bastien,
I'm not convinced it is in my setup yet.
emacs -Q works for me ... but that is org 7.5 in my
GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.1) of 2013-01-08
on murphy, modified by Debian
My minimal emacs setup has the same broken behaviour
,[ minimal.emacs ]
| (add-to-list 'load-path "~/git/org-mode/lisp/")
| ;(add-to-list 'load-path (expand-file-name "~/git/org-mode/lisp"))
| (add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" .
org-mode))
| (require 'org)
|
| (global-set-key "\C-cl" 'org-store-link)
| (global-set-key "\C-ca" 'org-agenda)
| (global-set-key "\C-cb" 'org-iswitchb)
`
,[ minimal-emacs ]
| #!/bin/sh
| TESTEL=
| TESTFILE=/tmp/test.el
| if test -e $TESTFILE
| then
| TESTEL="-l /tmp/test.el"
| fi
| emacs -q -l ~/minimal.emacs $TESTEL $1
`
/tmp/test.el does not exist currently on my system
I can reproduce this with
~/bin/minimal-emacs
C-x b foo RET
M-x org-mode
Org file has this
,
| * One
| two
| three
| four
| five
`
Put the cursor on first column of line two and hit M-S-RET gives me this
,
| * One
| two
| * TODO
| three
| four
| five
`
but I'm expecting
* TODO two
org-insert-heading-respect-content is nil.
It seems to work correctly when there is no heading above the text
(ie. One is not a headline)
M-x org-version reports
Org-mode version 8.0-pre (release_8.0-pre-299-g40f390 @
/home/bernt/git/org-mode/lisp/)
Regards,
Bernt
[O] Inconsistent handling of html images and image links
Dear list, before 8pre images [[file:example.png]] where imported left aligned into html now they are centred. Image links [[http://example.com][file:example.png]] are *still* imported left aligned!? I could live with a new default for images or links when #+attr_html: :options align="left" would give me a single image per row left aligned but I'm getting a left aligned image with text floating around it. Thanks for your time Dieter -- Best wishes H. Dieter Wilhelm Darmstadt Germany
Re: [O] New Exporter BUG/Change in behaviour
Nicolas Goaziou writes: > Thorsten Jolitz writes: > >> Nicolas Goaziou writes: >> >>> No. The "d:" item only applies to regular drawers. >>> >>> `property-drawer' elements are not among them. Back-ends handle these >>> beasts as they see fit (they usually ignore them, as you can tell). >> >> I actually have a use-case where I would like to export the >> property-drawer to ASCII, but that would involve writing new code - no way >> to configure it, right? > > There's no direct option, if that's your question. One possibility is, > from `org-export-before-processing-hook', to copy each property drawer > into an example block below. But it involves writing a couple lines of > code, indeed. Ok, I can do that, thanks for the hint. -- cheers, Thorsten
Re: [O] New Exporter BUG/Change in behaviour
Thorsten Jolitz writes: > Nicolas Goaziou writes: > >> No. The "d:" item only applies to regular drawers. >> >> `property-drawer' elements are not among them. Back-ends handle these >> beasts as they see fit (they usually ignore them, as you can tell). > > I actually have a use-case where I would like to export the > property-drawer to ASCII, but that would involve writing new code - no way > to configure it, right? There's no direct option, if that's your question. One possibility is, from `org-export-before-processing-hook', to copy each property drawer into an example block below. But it involves writing a couple lines of code, indeed. Regards, -- Nicolas Goaziou
Re: [O] [WORG] How to ediff folded Org files?
On Sat Apr 06 2013 at 17:24, Michael Brand wrote: > But instead of the above I use this for ediff generally, it persists > in Org mode: You just solved the most annoying little usage problem I've had - thanks! Cheers - bw -- Bill White . bi...@wolfram.com "No ma'am, we're musicians."
Re: [O] New Exporter BUG/Change in behaviour
Nicolas Goaziou writes: > No. The "d:" item only applies to regular drawers. > > `property-drawer' elements are not among them. Back-ends handle these > beasts as they see fit (they usually ignore them, as you can tell). I actually have a use-case where I would like to export the property-drawer to ASCII, but that would involve writing new code - no way to configure it, right? -- cheers, Thorsten
Re: [O] [WORG] How to ediff folded Org files?
Michael Brand writes: Hi Michael, > On Sat, Apr 6, 2013 at 11:32 PM, Thorsten Jolitz wrote: >> the problem is, if I call e (ediff) from Magit and want to merge (e.g.) >> my branch with the master branch, I don't really have access to both >> versions - only to the version from the checked out branch. >> >> ediff then gives me both versions in an ediff session (folded), but if I >> try to change major-mode to fundamental I break the ediff session. > > You should be able to refresh the ediff session with "!". I'll try that ... > But instead of the above I use this for ediff generally, it persists > in Org mode: > > #+BEGIN_SRC emacs-lisp > (add-hook 'ediff-prepare-buffer-hook 'f-ediff-prepare-buffer-hook-setup) > (defun f-ediff-prepare-buffer-hook-setup () > ;; specific modes > (cond ((eq major-mode 'org-mode) >(f-org-vis-mod-maximum)) > ;; room for more modes > ) > ;; all modes > (setq truncate-lines nil)) > (defun f-org-vis-mod-maximum () > "Visibility: Show the most possible." > (cond > ((eq major-mode 'org-mode) > (visible-mode 1) ; default 0 > (setq truncate-lines nil) ; no `org-startup-truncated' in hook > (setq org-hide-leading-stars t)) ; default nil > (t > (message "ERR: not in Org mode") > (ding > #+END_SRC very useful, thanks, I already put this into my .emacs. -- cheers, Thorsten
Re: [O] VCard export problems
Hi Bastien, Thanks for the fast response! I now get: Debugger entered--Lisp error: (void-variable tel) (if tel (progn (progn (setq phones-list (split-string tel "[,;: ]+")) (setq result "") (while phones-list (setq result (concat result "TEL:" (car phones-list) "\n")) (setq phones-list (cdr phones-list))) result))) (when tel (progn (setq phones-list (split-string tel "[,;: ]+")) (setq result "") (while phones-list (setq result (concat result "TEL:" (car phones-list) "\n")) (setq phones-list (cdr phones-list))) result)) (concat head (when email (progn (setq emails-list (split-string email "[,;: ]+")) (setq result "") (while emails-list (setq result (concat result "EMAIL:" (car emails-list) "\n")) (setq emails-list (cdr emails-list))) result)) (when addr (format "ADR:;;%s\n" (replace-regexp-in-string "\\, ?" ";" addr))) (when tel (progn (setq phones-list (split-string tel "[,;: ]+")) (setq result "") (while phones-list (setq result (concat result "TEL:" (car phones-list) "\n")) (setq phones-list (cdr phones-list))) result)) (when bday (let ((cal-bday (calendar-gregorian-from-absolute (org-time-string-to-absolute bday (format "BDAY:%04d-%02d-%02d\n" (calendar-extract-year cal-bday) (calendar-extract-month cal-bday) (calendar-extract-day cal-bday (when nick (format "NICKNAME:%s\n" nick)) (when note (format "NOTE:%s\n" note)) "END:VCARD\n\n") (let* ((properties (caddr contact)) (name (org-contacts-vcard-escape (car contact))) (n (org-contacts-vcard-encode-name name)) (email (cdr (assoc-string org-contacts-email-property properties))) (bday (org-contacts-vcard-escape (cdr (assoc-string org-contacts-birthday-property properties (addr (cdr (assoc-string org-contacts-address-property properties))) (nick (org-contacts-vcard-escape (cdr (assoc-string org-contacts-nickname-property properties (head (format "BEGIN:VCARD\nVERSION:3.0\nN:%s\nFN:%s\n" n name))) (concat head (when email (progn (setq emails-list (split-string email "[,;: ]+")) (setq result "") (while emails-list (setq result (concat result "EMAIL:" (car emails-list) "\n")) (setq emails-list (cdr emails-list))) result)) (when addr (format "ADR:;;%s\n" (replace-regexp-in-string "\\, ?" ";" addr))) (when tel (progn (setq phones-list (split-string tel "[,;: ]+")) (setq result "") (while phones-list (setq result (concat result "TEL:" (car phones-list) "\n")) (setq phones-list (cdr phones-list))) result)) (when bday (let ((cal-bday (calendar-gregorian-from-absolute (org-time-string-to-absolute bday (format "BDAY:%04d-%02d-%02d\n" (calendar-extract-year cal-bday) (calendar-extract-month cal-bday) (calendar-extract-day cal-bday (when nick (format "NICKNAME:%s\n" nick)) (when note (format "NOTE:%s\n" note)) "END:VCARD\n\n")) org-contacts-vcard-format(... On 04/06/2013 10:53 PM, Bastien wrote: Hi Simon, Simon Thum writes: I suspect some require is missing in org-contacts. In fact, `org-install-letbind' was called while not existing in current Org. So org-contacts.el tried to load the org-exp.el file that comes with your Emacs and that we never want to load when using pre-8.0. I removed this function. Anyway, if I invoke this line now it fails, although interactively things load fine with the org file on the command line: emacs someOrg.org -batch -l ~/.emacs.d/init.el [...] Symbol's value as variable is void: org-list-allow-alphabetical To me, all of this points to some incorrect dependencies of load logic to -batch. Unfortunately I don't know how to diagnose such problems. It's not urgent but seems like a clear bug to me. Indeed. Thanks for reporting this. Please test again and let me know if something else needs to be fixed. Best,
Re: [O] [WORG] How to ediff folded Org files?
Hi Thorsten On Sat, Apr 6, 2013 at 11:32 PM, Thorsten Jolitz wrote: > the problem is, if I call e (ediff) from Magit and want to merge (e.g.) > my branch with the master branch, I don't really have access to both > versions - only to the version from the checked out branch. > > ediff then gives me both versions in an ediff session (folded), but if I > try to change major-mode to fundamental I break the ediff session. You should be able to refresh the ediff session with "!". But instead of the above I use this for ediff generally, it persists in Org mode: #+BEGIN_SRC emacs-lisp (add-hook 'ediff-prepare-buffer-hook 'f-ediff-prepare-buffer-hook-setup) (defun f-ediff-prepare-buffer-hook-setup () ;; specific modes (cond ((eq major-mode 'org-mode) (f-org-vis-mod-maximum)) ;; room for more modes ) ;; all modes (setq truncate-lines nil)) (defun f-org-vis-mod-maximum () "Visibility: Show the most possible." (cond ((eq major-mode 'org-mode) (visible-mode 1) ; default 0 (setq truncate-lines nil) ; no `org-startup-truncated' in hook (setq org-hide-leading-stars t)) ; default nil (t (message "ERR: not in Org mode") (ding #+END_SRC Michael
Re: [O] New Exporter BUG/Change in behaviour
Hello, Thorsten Jolitz writes: > Shouldn't the > > ,- > | :EXPORT_OPTIONS: d:t > `- > > setting in the following minimal org-file export the property-drawer for > this subtree too? > > ,--- > | * header1 > | :PROPERTIES: > | :EXPORT_OPTIONS: d:t > | :END: > | > | hello world > | > | |hello| table| > | > `--- No. The "d:" item only applies to regular drawers. `property-drawer' elements are not among them. Back-ends handle these beasts as they see fit (they usually ignore them, as you can tell). Regards, -- Nicolas Goaziou
Re: [O] MobileOrg app not available in the Belgian App Store?
On 05/04/13 17:51, Holger Wenzel wrote: Hi Guido, I wanted to install the MobileOrg app on my iPhone, but iTunes claims that there is no such app in the Belgian App Store?! Did I miss something? did you go to, http://mobileorg.ncogni.to/ ? It looks like it's currently not available in the app store. At least in Germany I don't get it as well. And with that OS running on the smartphone there is little chance to get the app installed through a different channel. I wish I had my android back, unfortunately I work for an employer that constantly chooses mediocre tools. Cheers, Holger Yes. I think there was a problem with the Dropbox API changing. It looks like a patch has been submitted that fixes the issue but I think there was also some complication with api keys or something. The change-over of maintainer probably complicates things as well. So it should re-appear at some stage but it's hard to know when. Cheers, Dave.
Re: [O] Question about reftex mode in org-mode
"Robert P. Goldman" writes:
> Quite some time ago, I incorporated reftex into my use of org mode, per
> a suggestion on Worg:
>
> ;;;---
> ;;; Use reftex with org-mode, per Worg
> ;;;---
>
> (autoload 'turn-on-reftx "reftex" "Turn on RefTeX mode." t)
> (defun org-mode-reftex-setup ()
> (turn-on-reftex))
> (add-hook 'org-mode-hook 'org-mode-reftex-setup)
>
> Now I find that this has a bad behavior at least with Aquamacs: it can
> cause attempts to use the menu bar to be interrupted by a cryptic popup
> file selector that says "Master file:"
>
> This seems to be reftex trying to set a value for TeX-master.
>
> So maybe reftex is unhappy when it's not invoked inside of AucTeX (where
> TeX-master is defined and set).
>
> Anyone else seen this? Have a solution (e.g., have org files assume
> that TeX-master is t)?
I haven't seen it. This is my setup:
#+begin_src emacs-lisp
(setq reftex-default-bibliography
(quote ("~/documents/literature/lit.bib")))
(defun org-mode-reftex-setup ()
(load-library "reftex")
(and (buffer-file-name)
(file-exists-p (buffer-file-name))
(reftex-parse-all))
(make-local-variable 'reftex-cite-format)
(setq reftex-cite-format 'org)
(define-key org-mode-map (kbd "C-c )") 'reftex-citation))
(add-hook 'org-mode-hook 'org-mode-reftex-setup)
(eval-after-load 'reftex-vars
'(progn
(add-to-list 'reftex-cite-format-builtin
'(org "Org-mode citation"
((?\C-m . "[[cite:%l]]")
(?t . "[[textcite:%l]]")
(?p . "[[parencite:%l]]")
(?s . "[[citepos:%l]]")
(?a . "[[citeauthor:%l]]")
(?y . "[[citeyear:%l]]")
(?n . "%l")
;; the following depends on
org-link-search-must-match-exact-headline
(?o .
"[[file:~/documents/literature/lit.org::*%t][%2a (%y). %T]]"))
#+end_src
--
A page of history is worth a volume of logic
Re: [O] New Exporter BUG/Change in behaviour
Nicolas Goaziou writes: Hello, > The new exporter distinguishes between subtree export (toggled with C-s > key within the dispatcher) and region export. In the old exporter, C-c @ > + export command would give you a subtree export. This is not the case > in the new exporter. You have to explicitly mention you want a subtree > export. On the other hand, you don't need to select a region beforehand. > In other words, you don't trigger a subtree export anymore with C-c @ > (but it triggers a region export). > > If you export a subtree in the new exporter jargon, you can override > locally #+options: line by setting top headline's :EXPORT_OPTIONS: > property to an appropriate value, e. g. :EXPORT_OPTIONS: tasks:t. Shouldn't the ,- | :EXPORT_OPTIONS: d:t `- setting in the following minimal org-file export the property-drawer for this subtree too? ,--- | * header1 | :PROPERTIES: | :EXPORT_OPTIONS: d:t | :END: | | hello world | | |hello| table| | `--- Exporting to an ASCII buffer: , | C-c C-e t A ` gives ,-- | Thorsten Jolitz | | | Table of Contents | _ | | 1 header1 | | | 1 header1 | = | | hello world | | hello| table| `-- -- cheers, Thorsten
Re: [O] CSS link in html export for v. 7.9.3e woes
"Sebastien Vauban" writes: > I got into the same trouble days ago. Nicolas' answer was to use the new > syntax therefore, that is: > #+HTML_STYLE: ... There does not seem to be any reference to HTML_STYLE in the Org manual. (Org version 7.9.3e (7.9.3e-1751-g8c47da) — taken this morning). François
Re: [O] [WORG] How to ediff folded Org files?
Marc-Oliver Ihm writes: Hi, > if I need to ediff two org-files, I just switch their buffers back to > fundamental mode temporarily. Not elegant, but works. the problem is, if I call e (ediff) from Magit and want to merge (e.g.) my branch with the master branch, I don't really have access to both versions - only to the version from the checked out branch. ediff then gives me both versions in an ediff session (folded), but if I try to change major-mode to fundamental I break the ediff session. > Am 06.04.2013 11:47, schrieb Thorsten Jolitz: >> >> Hi List, >> >> many files on Worg have this startup option: >> >> ,-- >> | +STARTUP:... fold ... >> `-- >> >> what leads to trouble when there is a merge-conflict in (Ma)git to be >> resolved manually with e(diff), because the different versions of the >> Org-file are then presented in folded state in the ediff session, so the >> diffs are invisible. >> >> But when I call 'show-all' or so on them, it breaks the ediff session. >> Is there a simple trick to avoid this problem? >> >> PS >> I don't recieve any new messages from my gmane groups any more since >> yesterday - am I the only one? -- cheers, Thorsten
Re: [O] Highlighting bug with org-agenda-set-restriction-lock
Hi Bernt, Bernt Hansen writes: > I've noticed some differences since upgrading for creating headlines but > I haven't checked if this is due to my local setup yet. Feel free to throw all oddities that you notice, even with no deep test, it will help a lot. > Here is what I'm currently experiencing: > > I used to be able to just have a bunch of lines likes this > > , > | one > | two > | three > | four > ` > > and M-S-RET in the first column would create a TODO headline with this > as the heading > > ie. > > , > | * TODO one > | two > | three > | four > ` > > but now it seems to jump past the line before creating the heading. > > , > | one > | > | * TODO > | two > | three > | four > ` I get the correct behavior with emacs -Q and latest master, so it must surely be in your setup. > I have a heading hook that runs and inserts a timestamp when headings > are created so using this as a workaround and converting this to a list > with C-u C-c - and then to headings with C-c * doesn't give me the > result I want (inactive timestamps on all headings that were created) You can directly convert a normal line to a heading with C-c * Also, C-u C-c - will have the same effect if no region is selected: to convert the normal line at point to a list item. Beware that the default behavior changed when you select a region and want to convert it to a list: now C-c - will convert all lines in the region to list items; use C-u C-c - to convert the whole region as a single item. This behavior is more in sync with the one of C-c *. HTH, -- Bastien
Re: [O] Highlighting bug with org-agenda-set-restriction-lock
Bastien writes: > Hi Bernt, > > Bernt Hansen writes: > >> My workaround for the adding items to the ends is to remark the subtree >> restriction. I have added speed keys P, F, W, and N in my setup for >> narrow to project, narrow to file, widen, and narrow to subtree >> respectively. > > Note that you can narrow to subtree with the `s' speed key already. > > 2 cts -- and thanks for upgrading! Your feedback is most welcome > and awaited :) I've already remapped 's' to save all org buffers and I want the same key in both the agenda and org file so N works for me :) I've noticed some differences since upgrading for creating headlines but I haven't checked if this is due to my local setup yet. Here is what I'm currently experiencing: I used to be able to just have a bunch of lines likes this , | one | two | three | four ` and M-S-RET in the first column would create a TODO headline with this as the heading ie. , | * TODO one | two | three | four ` but now it seems to jump past the line before creating the heading. , | one | | * TODO | two | three | four ` I have a heading hook that runs and inserts a timestamp when headings are created so using this as a workaround and converting this to a list with C-u C-c - and then to headings with C-c * doesn't give me the result I want (inactive timestamps on all headings that were created) I haven't tried this with a minimal emacs setup yet. Regards, Bernt
Re: [O] Problems PlantUML
Hi Volker, writes: > running Org-mode version 7.8.11 under GNU Emacs 23.4.1 > (x86_64-pc-linux-gnu, GTK+ Version 2.24.10) I am stumbling over a > problem with babel/plantuml: Exporting a file with simple demo data > leads to a png file with error msg "@startuml empty > description". Evaluating the code block results in a correct > diagramm. Where am I wrong? Unless there are other Org 7.8.11 users out there that can help, I suggest upgrading to the current stable version 7.9.4: http://orgmode.org/ http://orgmode.org/org.html#Installation Sorry I cannot help more, best, -- Bastien
Re: [O] Does '#+OPTIONS LaTeX:dvipng' deprecated in 8.0 pre or a bug?
Hello,
Vladimir Lomov writes:
> Hello, the following simple Org document
> #+BEGIN_SRC org
> ,#+OPTIONS: LaTeX:dvipng ^:{}
>
> This is small example $\exp^{\imath\phi}=\cos\phi+\imath\sin\phi$.
> #+END_SRC
>
> gives me wrong HTML export, see attached html file.
It should be #+OPTIONS: tex:dvipng
Regards,
--
Nicolas Goaziou
Re: [O] phone links...
Hi Simon, Simon Thum writes: > (setq org-contacts-matcher "BIRTHDAY<>\"\"|ADR<>\"\"|EMAIL<>\"\"|TEL<>\"\"") > > to be able to find contacts not having an email. Something like it would > need to become the new default. This now uses (mapconcat 'identity (list org-contacts-email-property org-contacts-tel-property org-contacts-address-property org-contacts-birthday-property) "<>\"\"|") Thanks for suggesting this, -- Bastien
Re: [O] We're doing it wrong. [WAS]: Zip utility on Windows for ODT exporter
John Hendy writes: > I'll keep thinking through it. For now, I got Windows working by > simply editing ox-odt directly and replacing zip with zip.exe :) The only reason I can think of why this should help is that you somewhere have a file named "zip" (without any extension) in your path and before it gets to the directory where zip.exe resides. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] VCard export problems
Hi Simon, Simon Thum writes: > I suspect some require > is missing in org-contacts. In fact, `org-install-letbind' was called while not existing in current Org. So org-contacts.el tried to load the org-exp.el file that comes with your Emacs and that we never want to load when using pre-8.0. I removed this function. > Anyway, if I invoke this line now it fails, although interactively things > load fine with the org file on the command line: > > emacs someOrg.org -batch -l ~/.emacs.d/init.el > [...] > Symbol's value as variable is void: org-list-allow-alphabetical > > To me, all of this points to some incorrect dependencies of load logic to > -batch. Unfortunately I don't know how to diagnose such problems. > > It's not urgent but seems like a clear bug to me. Indeed. Thanks for reporting this. Please test again and let me know if something else needs to be fixed. Best, -- Bastien
Re: [O] Org-mode as a metalanguage: calling SQL "functions"
Eric Schulte writes: > Alternately this could be a page on Worg, but I think it is > important enough to be included in the manual. Agreed. In such cases, Worg can be used as a "sand-box" for fast writing and quick review by others. Then when the doc is mature enough, a patch against the manual would do. Just to say: feel free to use Worg in this "agile" perspective. -- Bastien
Re: [O] [PATCH] Using org babel for generating ASCII art using PlantUML
Hi Mats, Mats Kindahl writes: > I've got the necessary papers and am working on it. I don't expect any > problems, it's just red tape. Great, I added you to this page: http://orgmode.org/worg/org-contribute.html#sec-6-2 > I'll be back once I have the signatures I need. Thanks! -- Bastien
Re: [O] Highlighting bug with org-agenda-set-restriction-lock
Hi Bernt, Bernt Hansen writes: > My workaround for the adding items to the ends is to remark the subtree > restriction. I have added speed keys P, F, W, and N in my setup for > narrow to project, narrow to file, widen, and narrow to subtree > respectively. Note that you can narrow to subtree with the `s' speed key already. 2 cts -- and thanks for upgrading! Your feedback is most welcome and awaited :) -- Bastien
Re: [O] SETUPFILE: file open failure hardly noticeable
Hi Michael, Michael Brand writes: > Is there any opinion or help on how to improve this? I used (sit-for 3) after the message to increase the odds that the user gets it. -- Bastien
Re: [O] [WORG] How to ediff folded Org files?
Hi, if I need to ediff two org-files, I just switch their buffers back to fundamental mode temporarily. Not elegant, but works. regards, Marc Am 06.04.2013 11:47, schrieb Thorsten Jolitz: Hi List, many files on Worg have this startup option: ,-- | +STARTUP:... fold ... `-- what leads to trouble when there is a merge-conflict in (Ma)git to be resolved manually with e(diff), because the different versions of the Org-file are then presented in folded state in the ediff session, so the diffs are invisible. But when I call 'show-all' or so on them, it breaks the ediff session. Is there a simple trick to avoid this problem? PS I don't recieve any new messages from my gmane groups any more since yesterday - am I the only one?
Re: [O] MobileOrg app not available in the Belgian App Store?
Hi Guido, > > I wanted to install the MobileOrg app on my iPhone, but iTunes claims > that there is no such app in the Belgian App Store?! > > Did I miss something? did you go to, http://mobileorg.ncogni.to/ ? It looks like it's currently not available in the app store. At least in Germany I don't get it as well. And with that OS running on the smartphone there is little chance to get the app installed through a different channel. I wish I had my android back, unfortunately I work for an employer that constantly chooses mediocre tools. Cheers, Holger
Re: [O] Org tutorials
Hi Bastien, On 4/5/2013 8:57 PM, Bastien wrote: Hi Charles, Charles writes: Is there a reason why Richard Dillon's YouTube Hack Emacs org-mode talks are not included in the Org Tutorials? For instance An overview of Org Mode - http://www.youtube.com/watch?v=6W82EdwQhxU Actually this one was already there: http://orgmode.org/worg/org-tutorials/org-screencasts/ Feel free to add others to Worg, The screen cast that you brought to my attention was prepared by Richard Moreland, not Richard Dillon. That said, thank you! Your direction to the Moreland Worg section pointed me to the obvious way to add the Dillon screen casts to Worg. Charlie
Re: [O] Org-mode outside Org-mode
Samuel Wales writes: Hi Samuel, > IIUC, I don't think this is related. The idea is not to edit source > code in Org buffers, and it is not to use a Navi buffer or to do > navigation. > > The idea is to be in my-lisp.el, and do C-c ', and get to a canonical > entry in my-org.org, then do C-c ' again and get back to my-lisp.el. > > The navi buffer seems like it wouldn't do that. that sounds like a different idea. I have heard about programming environments that keep comments and source-code in two different (but sync'd) files to minimize distraction from the source code - maybe a possible use case for your idea? -- cheers, Thorsten
Re: [O] How to export property values of agenda selection?
Christian Moe christianmoe.com> writes: > I don't know how to do it from the agenda selection, but here's a pretty > simple way to do it in the document buffer using Babel: > > #+NAME: list2csv > #+BEGIN_SRC emacs-lisp :var match="topic2" > (mapconcat 'identity > (org-map-entries > '(org-entry-get (point) "EMAIL") > match nil) > ",") > #+END_SRC > > Now you can use a CALL line with a tags match as a parameter, like > > #+CALL: list2csv(match="topic2") > > to get > > #+RESULTS: list2csv(match="topic2") > : peter mayer.com,karl august.com Does anybody know how to get the results via Emacs batch mode on the command line? I'd like to embed the results in a webpage. The following is my starting point and of course terribly wrong and it doesn't work. It's hard for me to find documentation (that I understand). $ emacs -batch -l ~/.emacs -eval (progn (find-file \"~/test.org\") (org-babel-execute-src-block 'list2csv) (kill-buffer))" Thanks, Karl
[O] [WORG] How to ediff folded Org files?
Hi List, many files on Worg have this startup option: ,-- | +STARTUP:... fold ... `-- what leads to trouble when there is a merge-conflict in (Ma)git to be resolved manually with e(diff), because the different versions of the Org-file are then presented in folded state in the ediff session, so the diffs are invisible. But when I call 'show-all' or so on them, it breaks the ediff session. Is there a simple trick to avoid this problem? PS I don't recieve any new messages from my gmane groups any more since yesterday - am I the only one? -- cheers, Thorsten
[O] [babel] Bugs for Emacs Lisp code blocks
Hello, Here are some tests with the colnames parameter *and* the Emacs Lisp language for the "echo" code block. They're giving results I don't understand... Note that functionally the same "echo" code block in other languages (I tested R and sh) does return the expected results. * Input table Consider this input table, with 2 rows, and a header row. #+name: input | id | var1 | |--+--| | obs1 | foo | | obs2 | bar | * Interactive calls Let's try different calls, changing the =:colnames= parameter. 1. Using =:colnames yes= #+name: ELisp-echo-1 #+begin_src emacs-lisp :var data=input :colnames yes :exports results data #+end_src #+results: ELisp-echo-1 | id | var1 | |--+--| | obs1 | foo | | obs2 | bar | OK; the result is what I expected. 2. Using =:colnames no= #+name: ELisp-echo-2 #+begin_src emacs-lisp :var data=input :colnames no :exports results data #+end_src #+results: ELisp-echo-2 | id | var1 | |--+--| | obs1 | foo | | obs2 | bar | Here, I was expecting: | id | var1 | | obs1 | foo | | obs2 | bar | 3. Using no =:colnames= header argument #+name: ELisp-echo-3 #+begin_src emacs-lisp :var data=input :exports results data #+end_src #+results: ELisp-echo-3 | id | var1 | |--+--| | obs1 | foo | | obs2 | bar | Here, I was expecting: | obs1 | foo | | obs2 | bar | * Call at export time #+call: ELisp-echo-1(data=input) I get: | id | var1 | | id | var1 | | obs1 | foo | | obs2 | bar | Not at all what I was expecting... Best regards, Seb -- Sebastien Vauban
Re: [O] We're doing it wrong. [WAS]: Zip utility on Windows for ODT exporter
John Hendy writes: > I'll keep thinking through it. For now, I got Windows working by > simply editing ox-odt directly and replacing zip with zip.exe :) Is this that easy? And is it needed for all Windows users who do not install Cygwin? If so, the simple variable could do. -- Bastien
Re: [O] We're doing it wrong. [WAS]: Zip utility on Windows for ODT exporter
On Sat, Apr 6, 2013 at 1:09 PM, Bastien wrote:
> Hi John,
>
> John Hendy writes:
>
>> I guess there's no time like the present for learning some lisp.
>
> :)
>
>> *If* I can figure out how to do this, it would be a simple variable to
>> set the name of the zip utility. I'd add documentation specific to
>> Windows linking to INFO-zip or some other utility, instructions, and
>> then to set the variable to "C:/path/to/zip.exe" instead of just
>> "zip."
>
> There are three occurrences of "zip" in ox-odt.el.
>
> But two of them come with switches (see lines 4101):
>
> (cmds `(("zip" "-mX0" ,target-name "mimetype")
> ("zip" "-rmTq" ,target-name "."
>
> Two problems: (1) I don't know what these switches do, and
> (2) I infer there are specific to zip.
>
> So you would need to find out if there are necessary and what
> equivalent switches are needed for other zip utilities. If they
> are not necessary, let's remove them. If these switches are the
> same for all zip utilities (we can dream, right?), let's only
> have an option `org-odt-zip-executable'.
That's what I want, but it has to allow for a specific path to get
around having to specifically add the zip utility on Windows to the
actual $PATH environment. I'd rather leave the switches along, as then
one doesn't have to figure out a bunch of other zip utility stuff.
The current documentation requires that one have a *nix-equivalent
(wrt syntax) zip utility, hence other mailing list suggestions to use
INFO-zip.
If we want to go another route, say allowing for 7zip, it would
require more more cases to check for the actual zip utility being
used. INFO-zip was simple enough, so I think it would be fair to have
the user download it, move zip.exe somewhere, and then point to it
with the variable.
>
> If they are pecualiar to zip, then maybe the option should be an
> alist of executables to search for, along with formatting strings
> for those two occurrences -- something like:
>
> (setq org-odt-zip-executable
> '(("zip" "zip -mX0 %s mimetype" "zip -rmTq %s .")))
>
>> *nix users could simply leave the default variable, "zip", or change
>> to a direct path as well if they wanted.
>
> Yes. The problem is with the switches. That would be too simple
> otherwise :) Let us know if you can come up with something that
> is good enough for you!
>
I'll keep thinking through it. For now, I got Windows working by
simply editing ox-odt directly and replacing zip with zip.exe :)
John
> --
> Bastien
Re: [O] We're doing it wrong. [WAS]: Zip utility on Windows for ODT exporter
Hi John,
John Hendy writes:
> I guess there's no time like the present for learning some lisp.
:)
> *If* I can figure out how to do this, it would be a simple variable to
> set the name of the zip utility. I'd add documentation specific to
> Windows linking to INFO-zip or some other utility, instructions, and
> then to set the variable to "C:/path/to/zip.exe" instead of just
> "zip."
There are three occurrences of "zip" in ox-odt.el.
But two of them come with switches (see lines 4101):
(cmds `(("zip" "-mX0" ,target-name "mimetype")
("zip" "-rmTq" ,target-name "."
Two problems: (1) I don't know what these switches do, and
(2) I infer there are specific to zip.
So you would need to find out if there are necessary and what
equivalent switches are needed for other zip utilities. If they
are not necessary, let's remove them. If these switches are the
same for all zip utilities (we can dream, right?), let's only
have an option `org-odt-zip-executable'.
If they are pecualiar to zip, then maybe the option should be an
alist of executables to search for, along with formatting strings
for those two occurrences -- something like:
(setq org-odt-zip-executable
'(("zip" "zip -mX0 %s mimetype" "zip -rmTq %s .")))
> *nix users could simply leave the default variable, "zip", or change
> to a direct path as well if they wanted.
Yes. The problem is with the switches. That would be too simple
otherwise :) Let us know if you can come up with something that
is good enough for you!
--
Bastien
Re: [O] Latex export of longtable with multiline heading
On Fri, Apr 5, 2013 at 9:40 PM, Simon Guest wrote:
> Dear Org-mode people,
>
> I have an Org mode document containing a longtable, which has its
> heading row split over two lines. Exporting this to Latex doesn't work.
What's the output of =M-x org-version= ?
If it's > 7.9.4f, you're on the new exporter, and syntax has changed.
>
> Here's a really small example (for which I wouldn't need longtable,
> but you get the point):
>
> #+ATTR_LaTeX: longtable align=|r|r|
> |---+-|
> | First | Age |
> | Name | (years) |
> |---+-|
> | Bob | 6 |
> | Dave | 7 |
> | Wendy | 9 |
> |---+-|
>
Try this:
#+ATTR_LaTeX: :environment longtable :align |r|r|
> The PDF document is missing the first line of the header. Looking at
> the Latex file which is generated, there appear to be too many
> (i.e. 2) instances of \endhead (but I'm no expert on longtables in
> Latex).
Your example with the #+attr_latex line above gives this:
#+begin_src latex
\begin{longtable}{|r|r|}
\toprule
First & Age\\
Name & (years)\\
\midrule
\endhead
...
...
#+end_src
Keep in mind I'm using booktabs, so instead of \[top/mid]rule, you'd
get \hline with a default setup. Things look decent to me in the
output.
If you're on the "old exporter," see here for upgrading:
- http://orgmode.org/worg/org-8.0.html
Good luck!
John
>
> It's important that I get this working, or find a work-around.
>
> Any suggestions?
>
> cheers,
> Simon
>
Re: [O] org-html-postamble-format and #+DATE: specification in 8.0pre
Alan Schmitt writes:
> Here is the postamble that is generated here:
>
>
> Author: Me
> Created: 2013-04-06 Sat 19:25
> Generated by http://orgmode.org";>Org mode
> 8.0-pre in http://www.gnu.org/software/emacs/";>Emacs
> 24.2.93.1.
> href="http://validator.w3.org/check?uri=referer";>Validate XHTML 1.0
>
>
> It has the date.
It isn't the date but the document time stamp (see
`org-export-time-stamp-file').
> But there is something weird, in the default option:
>
> (("en" "Author: %a (%e)\nDate:
> %d\nGenerated by %c\n class=\"xhtml-validation\">%v"))
>
> the text is "Date" and not "Created".
This variable is used iff `org-html-postamble' is set to `t'. You
probably have it set to `auto'.
Regards,
--
Nicolas Goaziou
Re: [O] css link colors for Worg are difficult to spot
John Hendy writes: > Agreed as well. +1 > It drives me crazy to have posted to the list a couple times > recently for someone to tell me where, exactly, something is only to > find out there was, indeed, a link in the paragraph I was looking at > but didn't see it! I hereby declare you "Head of Worg Design Department"! Please be bold. -- Bastien
Re: [O] We're doing it wrong. [WAS]: Zip utility on Windows for ODT exporter
On Fri, Apr 5, 2013 at 7:10 PM, Bastien wrote: > Hi John and David, > > If one of you can provide a patch for this, that'd be great. > I guess there's no time like the present for learning some lisp. *If* I can figure out how to do this, it would be a simple variable to set the name of the zip utility. I'd add documentation specific to Windows linking to INFO-zip or some other utility, instructions, and then to set the variable to "C:/path/to/zip.exe" instead of just "zip." *nix users could simply leave the default variable, "zip", or change to a direct path as well if they wanted. John > Thanks, > > -- > Bastien
Re: [O] css link colors for Worg are difficult to spot
On Sat, Apr 6, 2013 at 3:23 AM, Alexander Poslavsky
wrote:
>
> On 1 Apr 2013, at 15:14, John Hendy wrote:
>
> I find the links difficult to spot in Worg sometimes, especially
> depending on monitor angle and current brightness setting. Is this an
> issue for anyone else?
>
> I fiddled around in /style/worg.css a bit and didn't land on anything
> too great. I'm wondering if anyone with a design background might have
> suggestions for link colors? I guess if no one else is affected by
> this... I'll just deal with it and mine sweep wildly with my mouse
> when I think a link should be in there somewhere :)
>
>
> In the old days lines used to be underlined, nowadays it is considered a bit
> dated, but an underlined item in a sentence is generally understood to be a
> link.
>
> A good example is http://docs.webplatform.org/wiki/html/elements/a
>
> Which uses:
>
> a { text-decoration: underline }
>
> and for external links:
>
> a.external {
> padding-right: 15px;
> margin-right: 5px;
> background-image: url(skins/webplatform/images/link-external.png);
> background-repeat: no-repeat;
> background-position: right 3px;
> }
I wouldn't mind this at all. Or perhaps the same color link, but
unvisited is underlined and visited is not? Or reddish + underline for
unvisited, greenish + underline for visited, and hover simply
brightens up each respective color or something?
>
> Design as this won't do on behance or dribble, but worg is primarily for
> documentation. Usability and readability should trump superficial aesthetics
> in a case like this.
Agreed as well. It drives me crazy to have posted to the list a couple
times recently for someone to tell me where, exactly, something is
only to find out there was, indeed, a link in the paragraph I was
looking at but didn't see it!
John
Re: [O] [PATCH] Process hlines in imported tables
Bastien writes: > Hi Eric, > > Eric Schulte writes: > >> I'm nervous about such a patch at the last minute. > > Please go ahead and apply it, that's the best way to find problems. Done. Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte
[O] Problems PlantUML
Hi, running Org-mode version 7.8.11 under GNU Emacs 23.4.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.10) I am stumbling over a problem with babel/plantuml: Exporting a file with simple demo data leads to a png file with error msg "@startuml empty description". Evaluating the code block results in a correct diagramm. Where am I wrong? Thank you in advance Volker BTW: Thank you for this great tool!!
Re: [O] org-html-postamble-format and #+DATE: specification in 8.0pre
Hello,
Nicolas Goaziou writes:
> I cannot reproduce your problem.
>
> With the current Org buffer:
>
> --8<---cut here---start->8---
> #+language: en
> #+author: Me
> #+options: postamble:t author:t date:t
> * Headline
> Body
> --8<---cut here---end--->8---
>
> I get no date in the (default) postamble.
Here is the postamble that is generated here:
Author: Me
Created: 2013-04-06 Sat 19:25
Generated by http://orgmode.org";>Org mode
8.0-pre in http://www.gnu.org/software/emacs/";>Emacs 24.2.93.1.
http://validator.w3.org/check?uri=referer";>Validate XHTML 1.0
It has the date. But there is something weird, in the default option:
(("en" "Author: %a (%e)\nDate:
%d\nGenerated by %c\n%v"))
the text is "Date" and not "Created".
Alan
Re: [O] [PATCH] Process hlines in imported tables
Hi Eric, Eric Schulte writes: > I'm nervous about such a patch at the last minute. Please go ahead and apply it, that's the best way to find problems. -- Bastien
Re: [O] [PATCH] Process hlines in imported tables
> > Of these I would guess that the following 7 should be updated to use the > org-babel-result-cond macro. > > scheme ruby ocaml matlab js haskell asymptote > > I don't know if we want to try to make these changes before the 8.0 > release. I personally could update and test js, scheme, ocaml and > haskell this weekend. The attached tarball patches these four languages to use the org-babel-result-cond macro. I've tested them all and they seem to work. Any reason not to apply these changes? patches.tar.bz2 Description: BZip2 compressed data > I do not have ruby, matlab or asymptote installed on my laptop. > > Thanks, > >> >> >> Regards, >> Achim. -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] org-html-postamble-format and #+DATE: specification in 8.0pre
Hello,
Alan Schmitt writes:
> Ah, I see. What I don't understand is why the default postamble can
> display the date, as it's also using %d:
>
> Original value was
> (("en" "Author: %a (%e)\nDate:
> %d\nGenerated by %c\n class=\"xhtml-validation\">%v"))
I cannot reproduce your problem.
With the current Org buffer:
--8<---cut here---start->8---
#+language: en
#+author: Me
#+options: postamble:t author:t date:t
* Headline
Body
--8<---cut here---end--->8---
I get no date in the (default) postamble.
Regards,
--
Nicolas Goaziou
Re: [O] [PATCH] Process hlines in imported tables
"Sebastien Vauban" writes: > Eric, > > Eric Schulte wrote: >> I would agree that this (meaning raw implies scalar) should either occur >> for all languages or for none. > > I think this is something interesting, but I wonder now if we wouldn't loose > more than we would win. I mean: how would one be able to output a real "raw" > result, then, that is one where pipes are not interpreted as table field > separator which have to be aligned in some specific way. > > Do we need another argument for that? > > I mean: at the end, raw should really be raw (no interpretation). If we want > some cycling for table alignment purpose (BTW, do you have lots of such code > blocks?), maybe it'd be better to introduce a `cycle' argument or so? > >> If we do have such header argument implications, then we'd want to put them >> into the weakest portion of the default header argument hierarchy. Currently >> this hierarchy looks something like >> >> 1. default header arguments shipped with Org-mode >> 2. user-set default header arguments >> 3. default languages-specific header arguments shipped with Org-mode >> 4. user-set default language-specific header arguments >> 5. buffer or file level header arguments >> 6. subtree header arguments >> 7. code block header arguments >> >> I think this raw implies verbatim action should probably take place >> somewhere between 3 and 4, but there could be arguments for other >> positions. Also, without looking at the code, I'm not sure how >> difficult adding such implications would be. > > Maybe I don't understand the problem correctly, but I'd think this "raw > implies verbatim" would have to take place after _each_ above step. > Actually I think I was confused when I wrote the above, so please disregard, sorry for the noise. Best, > > If between 3 and 4, then a raw specified on the block level (step 7) > wouldn't imply verbatim? Does that make sense? > > I think every raw (be it default, language, buffer, subtree or block-local) > would have to imply the same reasoning. > >> Are there other header argument implication rules which would make code >> blocks "do what I mean" more naturally in more situations? > > Best regards, > Seb -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [PATCH] Process hlines in imported tables
Achim Gratz writes: > Sebastien Vauban writes: >> Achim Gratz wrote: >>> Elisp is different from all other languages: it doesn't do any >>> processing of strings to begin with for value returns. The reason that >>> Perl processes "raw" results is that org-babel-result-cond does not >>> switch to the "scalar" path for this condition, which is why you need >>> the extra "verbatim". It probably should, though, so if Eric agrees >>> then I will push a change that does this. >> >> IIUC, wouldn't that be changing the default answer to "how to >> interpret the results" just for Perl? While the default answer for >> all languages seems to be "table"? > > Again, org-babel-result-cond doesn't interpret "raw" at all at the > moment, which I think is a bug. This leads to the interpretation of > multiline strings and strings with separators in the return value as > tables. The attached patch updates the org-babel-result-cond macro so that "raw", "org" and "drawer" all imply verbatim results *unless* the ":results table" header argument is explicitly specified. I think this is an improvement and should (hopefully) be merged before the 8.0 release. Could everyone on this thread test this patch and let me know what you think before I apply it? I'm nervous about such a patch at the last minute. >From c12003708f691862086aac30c675868cd69d6bb3 Mon Sep 17 00:00:00 2001 From: Eric Schulte Date: Sat, 6 Apr 2013 10:18:35 -0600 Subject: [PATCH] raw org and drawer imply verbatim results This unifies the results handling across a number of different languages. It is still possible to force tabular output by adding the ":results table" argument. The following example demonstrates the results in shell python and perl. ** drawer and table #+begin_src sh :results drawer table echo -e "1\n2\n3" #+end_src #+RESULTS: :RESULTS: | 1 | | 2 | | 3 | :END: #+begin_src perl :results drawer table "1\n2\n3" #+end_src #+RESULTS: :RESULTS: | 1 | | 2 | | 3 | :END: #+begin_src python :results drawer table return "1\n2\n3" #+end_src #+RESULTS: :RESULTS: | 1\n2\n3 | :END: ** drawer #+begin_src sh :results drawer echo -e "1\n2\n3" #+end_src #+RESULTS: :RESULTS: 1 2 3 :END: #+begin_src perl :results drawer "1\n2\n3" #+end_src #+RESULTS: :RESULTS: 1 2 3 :END: #+begin_src python :results drawer return "1\n2\n3" #+end_src #+RESULTS: :RESULTS: 1 2 3 :END: ** raw #+begin_src sh :results raw echo -e "1\n2\n3" #+end_src #+RESULTS: 1 2 3 #+begin_src perl :results raw "1\n2\n3" #+end_src #+RESULTS: 1 2 3 #+begin_src python :results raw return "1\n2\n3" #+end_src #+RESULTS: 1 2 3 * lisp/ob-core.el (org-babel-result-cond): The "raw", "org" and "drawer" :results header argument values preclude table processing unless the "table" argument is given as well. --- lisp/ob-core.el | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/lisp/ob-core.el b/lisp/ob-core.el index bba2dfe..b8f863f 100644 --- a/lisp/ob-core.el +++ b/lisp/ob-core.el @@ -2637,10 +2637,14 @@ Emacs shutdown.")) (member "html" ,result-params) (member "code" ,result-params) (member "pp" ,result-params) - (and (member "output" ,result-params) + (and (or (member "output" ,result-params) + (member "raw",result-params) + (member "org",result-params) + (member "drawer" ,result-params)) (not (member "table" ,result-params ,scalar-form ,@table-forms))) +(def-edebug-spec org-babel-result-cond (form form body)) (defun org-babel-temp-file (prefix &optional suffix) "Create a temporary file in the `org-babel-temporary-directory'. -- 1.8.2 > Not all Babel languages are using that macro, so these implementations > might have a different interpretation (which may or may not be a bug > in itself). > Every general purpose language should be using this macro. The following lists those ob*.el files which don't use this macro. $ grep -rc org-babel-result-cond lisp/ob*el|grep 0|sed 's/:.*$//' lisp/ob-asymptote.el lisp/ob-calc.el lisp/ob-comint.el lisp/ob-css.el lisp/ob-ditaa.el lisp/ob-dot.el lisp/ob.el lisp/ob-eval.el lisp/ob-exp.el lisp/ob-gnuplot.el lisp/ob-haskell.el lisp/ob-js.el lisp/ob-keys.el lisp/ob-latex.el lisp/ob-ledger.el lisp/ob-lilypond.el lisp/ob-lob.el lisp/ob-makefile.el lisp/ob-matlab.el lisp/ob-mscgen.el lisp/ob-ocaml.el lisp/ob-octave.el lisp/ob-org.el lisp/ob-plantuml.el lisp/ob-ref.el lisp/ob-ruby.el lisp/ob-sass.el lisp/ob-scheme.el lisp/ob-screen.el lisp/ob-table.el lisp/ob-tangle.el Of these I would guess that the following 7 should be updated to use the org-babel-result-cond macro. scheme ruby ocaml matlab js haskell asymptote I don't know if we want to try to make these changes before the 8.0 release. I personally could update and test js, scheme, ocaml and haskell this weekend. I do not have ruby, matlab or a
Re: [O] Org as a static site generator
On 06/04/13 16:15, Christopher Allan Webber wrote: Cool, thanks for that info! Ian Barton writes: On Fri, Apr 05, 2013 at 11:02:56AM -0500, Christopher Allan Webber wrote: Ian Barton writes: On 01/04/13 13:08, Vincent Beffara wrote: Yes, I mean, I know which html you need for that, simply within o-blog you need to manage between relative paths, absolute paths, canonical paths and so on in the template, to match the right section, - mainly it should be a matter of let-ing the right variable to the right value at the right point in the template and catching it when generating the toc, but I never took the time to get it right ... I've also just found this, which uses Org only as a markup tool and Jekyll to generate the site: http://orgmode.org/worg/org-tutorials/org-jekyll.html I had a look at the too, but it felt just a little bit too convoluted compared to managing everything from Org. Besides, it seems to lose fontification of code snippets and the like? /v As the original author of that page, I agree that using Jekyll is convoluted, but it gives you much more control. However I now use Pelican: https://pelican.readthedocs.org/en/3.1.1/ There are a few reasons for this. Pelican is written in Python, which I find easier to hack on. It is more flexible than Jekyll, which I found hard to get to work the way I wanted with categories and tags. I wrote a yaml importer for Pelican so I could use my old jekyll posts. However, Pelican understands Markdown, which I think the new exporter supports. So my work flow now is Emacs-> export as html -> run Jekyll Ian. Heya Ian, I've been planning to switch my blog over to pelican. It's cool to hear you say this. Is there any special elisp you use for the export, including converting things like the title, etc? Thanks! - Chris Hi Chris, No, nothing special. I just use org's standard publish functions. However, I publish only the body part of the html and place the yaml tags in the org file. A typical org file for a blog post would look like: #+STARTUP: showall indent #+STARTUP: hidestars #+OPTIONS: H:2 num:nil tags:nil toc:nil timestamps:nil #+BEGIN_HTML --- title: My Fire Steel Crumbles to Dust. date: 2013-02-17 tags: [gear] category: blog --- #+END_HTML After my walk over Moel Famau and Moel Arthur I was looking forward to making a hot drink. My brew kit lives permanently in the boot of org pubish then creates a file with a yaml header and html body text. Then I just run Pelican to publish the post. I have written a Pelican yaml reader which converts the yaml files to allow Pelican to process them. I'll document the whole process over the next couple of days and put it on Worg. I keep meaning to contribute my yaml reader back to Pelican, but it's quite specific to publishing org-mode files and not really a general purpose yaml importer. -- I have just written a short post at: http://www.ian-barton.com/posts/2013/Apr/06/blogging-with-emacs-org-mode-and-pelican/ which describes how I use org-mode and Pelican. I'll write a more comprehensive explanation for Worg. Ian.
Re: [O] Org as a static site generator
Cool, thanks for that info! Ian Barton writes: > On Fri, Apr 05, 2013 at 11:02:56AM -0500, Christopher Allan Webber wrote: >> Ian Barton writes: >> >> > On 01/04/13 13:08, Vincent Beffara wrote: >> > >> >> Yes, I mean, I know which html you need for that, simply within o-blog >> >> you need to manage between relative paths, absolute paths, canonical >> >> paths and so on in the template, to match the right section, - mainly it >> >> should be a matter of let-ing the right variable to the right value at >> >> the right point in the template and catching it when generating the toc, >> >> but I never took the time to get it right ... >> >>> I've also just found this, which uses Org only as a markup tool and >> >>> Jekyll to generate the site: >> >>> >> >>> http://orgmode.org/worg/org-tutorials/org-jekyll.html >> >> I had a look at the too, but it felt just a little bit too convoluted >> >> compared to managing everything from Org. Besides, it seems to lose >> >> fontification of code snippets and the like? >> >> >> >> /v >> >> >> > As the original author of that page, I agree that using Jekyll is >> > convoluted, but it gives you much more control. However I now use >> > Pelican: https://pelican.readthedocs.org/en/3.1.1/ >> > >> > There are a few reasons for this. Pelican is written in Python, which I >> > find easier to hack on. It is more flexible than Jekyll, which I found >> > hard to get to work the way I wanted with categories and tags. >> > >> > I wrote a yaml importer for Pelican so I could use my old jekyll posts. >> > However, Pelican understands Markdown, which I think the new exporter >> > supports. >> > >> > So my work flow now is Emacs-> export as html -> run Jekyll >> > >> > Ian. >> >> Heya Ian, >> >> I've been planning to switch my blog over to pelican. It's cool to hear >> you say this. >> >> Is there any special elisp you use for the export, including converting >> things like the title, etc? >> >> Thanks! >> - Chris > > > Hi Chris, > > No, nothing special. I just use org's standard publish functions. However, I > publish only the body part of the html and place the yaml tags in the org > file. A typical org file for a blog post would look like: > > > #+STARTUP: showall indent > #+STARTUP: hidestars > #+OPTIONS: H:2 num:nil tags:nil toc:nil timestamps:nil > #+BEGIN_HTML > --- > title: My Fire Steel Crumbles to Dust. > date: 2013-02-17 > tags: [gear] > category: blog > > --- > #+END_HTML > > After my walk over Moel Famau and Moel Arthur I was looking forward > to making a hot drink. My brew kit lives permanently in the boot of > > > > org pubish then creates a file with a yaml header and html body text. Then I > just run Pelican to publish the post. I have written a Pelican yaml reader > which converts the yaml files to allow Pelican to process them. I'll document > the whole process over the next couple of days and put it on Worg. I keep > meaning to contribute my yaml reader back to Pelican, but it's quite specific > to publishing org-mode files and not really a general purpose yaml importer. > > > -- > > Best wishes, > > Ian.
Re: [O] [ox-html] Using a different title in the head and in the body
Bastien writes: > Hi Alan, > > Alan Schmitt writes: > >> I'm building a small web site using org-mode, and I cannot find out how >> to have a short title in the head of the generated html, and a longer >> one in the body. >> >> Is this possible? > > Nope, this is not possible -- or maybe a ugly hack would be to set > your own ... in #+HTML_HEAD and pray so that browsers > interpret the last one they see. Thanks for the suggestion. I tried it, and it does not work with Firefox (only the first title is used). I could do it with some JavaScript, but it's not that important to bother at the moment. Alan
Re: [O] org-html-postamble-format and #+DATE: specification in 8.0pre
Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> I have a more serious issue: it seems that '%d' is no longer taken into
>> account. To reproduce, try exporting the following:
>>
>> #+BEGIN_SRC org
>> # -*- org-export-allow-bind-keywords: t -*-
>>
>> #+TITLE: Testing the date
>> #+BIND: org-html-postamble-format (("en" "Test %d %a"))
>
>>
>> Hello World
>> #+END_SRC
>
> You didn't specify any date.
Ah, I see. What I don't understand is why the default postamble can
display the date, as it's also using %d:
Original value was
(("en" "Author: %a (%e)\nDate:
%d\nGenerated by %c\n%v"))
Alan
[O] VCard export problems
Hi, I just updates to the latest org and found the vcard export no longer works. I get Exporting... let*: Symbol's function definition is void: org-install-letbind Debug gets me: Debugger entered--Lisp error: (void-function org-install-letbind) (org-install-letbind) (let* ((filename (or file org-contacts-vcard-file)) (buffer (if to-buffer (get-buffer-create to-buffer) (find-file-noselect filename (message "Exporting...") (set-buffer buffer) (let ((inhibit-read-only t)) (erase-buffer)) (fundamental-mode) (org-install-letbind) (when (fboundp (quote set-buffer-file-coding-system)) (set-buffer-file-coding-system coding-system-for-write)) (loop for contact in (org-contacts-filter name) do (insert (org-contacts-vcard-format contact))) (if to-buffer (current-buffer) (progn (save-buffer) (kill-buffer org-contacts-export-as-vcard() I use make and emacs 24.2.1. I'm not sure it's related but on my server I get the same error - after changing the invocation. I now use emacs -batch -l ~/.emacs.d/init.el -f org-contacts-export-as-vcard --kill leading to aforementioned error. Before the update, I had to invoke emacs someOrgFile.org -batch -l ~/.emacs.d/init.el -f org-contacts-export-as-vcard --kill because otherwise it would fail to load some stuff required by org-contacts. Other exporters never had this issue. I suspect some require is missing in org-contacts. Anyway, if I invoke this line now it fails, although interactively things load fine with the org file on the command line: emacs someOrg.org -batch -l ~/.emacs.d/init.el [...] Symbol's value as variable is void: org-list-allow-alphabetical To me, all of this points to some incorrect dependencies of load logic to -batch. Unfortunately I don't know how to diagnose such problems. It's not urgent but seems like a clear bug to me. Cheers, Simon
Re: [O] org-html-postamble-format and #+DATE: specification in 8.0pre
Nicolas Goaziou écrivit : > I have pushed a fix in master branch. Does it solves the problem? It solves, Maurice should practice writing in English to submit the first.
Re: [O] [PATCH] Was: How to apply multiple TBLFM rules?
Hi Ippei, Ippei FURUHASHI writes: > Thanks for looking at these patch. > I found a bug introduced at > http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=bd8ff1aade6c46f701f466035ef75ab8ee82c8fe > which I made. > Could you apply this (attached) patch for them please? Done, thanks! -- Bastien
Re: [O] [PATCH] Was: How to apply multiple TBLFM rules?
Hi Bastien, Thanks for looking at these patch. I found a bug introduced at http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=bd8ff1aade6c46f701f466035ef75ab8ee82c8fe which I made. Could you apply this (attached) patch for them please? Thanks in advance, IP >From 24a18f1ffdc38dfd297960d9b06a12f35a256e82 Mon Sep 17 00:00:00 2001 From: Ippei FURUHASHI Date: Fri, 5 Apr 2013 16:07:00 +0900 Subject: [PATCH] org-table.el: Fix a bug of leaving the inserted TBLFM line * org-table.el (org-calc-current-TBLFM): Ensure to remove the currently inserted TBLFM line, when calling `org-table-recalculate' returns an error and the processing stops. * testing/lisp/test-org-table.el: Add test. When you hit =C-c C-c= at the line of "#+TBLFM: $2=$1*2::$2=$1**2" in | 1 | | | 2 | | #+TBLFM: $2=$1*1 #+TBLFM: $2=$1*2::$2=$1**2 you got: | 1 | | | 2 | | #+TBLFM: $2=$1*2::$2=$1**2 #+TBLFM: $2=$1*1 #+TBLFM: $2=$1*2::$2=$1**2 with the error message of: user-error: Double definition `$2=' in TBLFM line, please fix by hand In this case, you expected: | 1 | | | 2 | | #+TBLFM: $2=$1*1 #+TBLFM: $2=$1*2::$2=$1**2 --- lisp/org-table.el |7 --- testing/lisp/test-org-table.el | 25 + 2 files changed, 29 insertions(+), 3 deletions(-) diff --git a/lisp/org-table.el b/lisp/org-table.el index ccd1735..460d249 100644 --- a/lisp/org-table.el +++ b/lisp/org-table.el @@ -3190,10 +3190,11 @@ (defun org-calc-current-TBLFM (&optional arg) (beginning-of-line 0) ; move to the inserted line (skip-chars-backward " \r\n\t") (if (org-at-table-p) - (org-call-with-arg 'org-table-recalculate (or arg t))) + (unwind-protect + (org-call-with-arg 'org-table-recalculate (or arg t)) - ;; Delete the formula inserted temporarily - (delete-region s e + ;; delete the formula inserted temporarily + (delete-region s e)) (defun org-TBLFM-begin () "Find the beginning of the TBLFM lines and return its position. diff --git a/testing/lisp/test-org-table.el b/testing/lisp/test-org-table.el index dda8561..01adf52 100644 --- a/testing/lisp/test-org-table.el +++ b/testing/lisp/test-org-table.el @@ -929,6 +929,31 @@ (defconst references/target-special " (should (string= got expect) +(ert-deftest test-org-table/org-calc-current-TBLFM-when-stop-because-of-error () + "org-calc-current-TBLFM should preserve the input as it was." + (org-test-with-temp-text-in-file + " +| 1 | 1 | +| 2 | 2 | +#+TBLFM: $2=$1*1 +#+TBLFM: $2=$1*2::$2=$1*2 +#+TBLFM: $2=$1*3 +" +(let ((expect " +| 1 | 1 | +| 2 | 2 | +#+TBLFM: $2=$1*1 +#+TBLFM: $2=$1*2::$2=$1*2 +#+TBLFM: $2=$1*3 +")) + (goto-char (point-min)) + (forward-line 4) + (should-error (org-calc-current-TBLFM)) + (setq got (buffer-string)) + (message "%s" got) + (should (string= got + expect) + (provide 'test-org-table) ;;; test-org-table.el ends here -- 1.7.9.msysgit.0 Bastien writes: >> This patch enables user to applies a temporal TBLFM line where you are in. >> It is useful when you switch a formula to another. >> I hope you liked this. > > I do! I've applied the patches (with some minor changes) on my local > branch, it will be available when I push it later today.
Re: [O] org-html-postamble-format and #+DATE: specification in 8.0pre
Hello,
> #+DATE: {{{modification-time(%Y-%m-%d)}}}
>
> is working when I'm exporting individual files but now when I'm trying
> to publish I'm getting:
>
> Generating tree-style sitemap for Die Dünenhof-Seite [15 times]
> byte-code: Bad timestamp `((macro (:key modification-time :value
> {{{modification-time(%Y-%m-%d)}}} :args (%Y-%m-%d) :begin 1 :end 34
> :post-blank 0 :parent #0)))'
> Error was: (stringp ((macro (:key modification-time :value
> {{{modification-time(%Y-%m-%d)}}} :args (%Y-%m-%d) :begin 1 :end 34
> :post-blank 0 :parent #1
>
> Seemingly this macro wreaks havoc with the automatic sitemap
> generation...
Indeed, there's a bug. Thank you for letting me know.
I have pushed a fix in master branch. Does it solves the problem?
Regards,
--
Nicolas Goaziou
Re: [O] phone links...
Bastien, one more thing: I have (setq org-contacts-matcher "BIRTHDAY<>\"\"|ADR<>\"\"|EMAIL<>\"\"|TEL<>\"\"") to be able to find contacts not having an email. Something like it would need to become the new default. Cheers, Simon On 04/05/2013 08:42 AM, Bastien wrote: Hi Simon, Simon Thum writes: Since you're at it: I keep the attached patch personally. I use it to sync org-contacts entries to my phone. I applied Feng's patches against org-contacts.el, maybe you don't need your patch anymore. Best,
Re: [O] phone links...
Hi, seem like I am losing the work/home distinction. Not terribly useful (to me at least), so ok. I do have several contact with more than one number though, and I also like to use spaces to delineate phone number part, like [country SPACE city SPACE subscriber]. Therefore it would be useful to have docs on how the splitting would work, e.g. in the property docstring. Cheers, Simon On 04/05/2013 08:42 AM, Bastien wrote: Hi Simon, Simon Thum writes: Since you're at it: I keep the attached patch personally. I use it to sync org-contacts entries to my phone. I applied Feng's patches against org-contacts.el, maybe you don't need your patch anymore. Best,
Re: [O] org-html-postamble-format and #+DATE: specification in 8.0pre
Nicolas Goaziou writes:
> Hello,
>
>> Sorry I don't get it completely.
>> I'd like to have as the DATE value the current change time of the file.
>> You mean that I should set this with the Emacs timestamp facility? Like:
>
>> #+DATE: Time-stamp: " "
>
> If you're exporting a buffer associated to a file, you may use:
>
> #+DATE: {{{modification-time(%Y-%m-%d)}}}
Thank you for the explanation, I really appreciate that and I'm happy to
learn new possibilities in org. At first I thought it just a regression
that I had additionally to put in a macro but on the other hand it is
much more precise for my needs then
#+DATE %Y-%m-%d
which gave me in 7.xx only the current time. So far so good.
#+DATE: {{{modification-time(%Y-%m-%d)}}}
is working when I'm exporting individual files but now when I'm trying
to publish I'm getting:
Generating tree-style sitemap for Die Dünenhof-Seite [15 times]
byte-code: Bad timestamp `((macro (:key modification-time :value
{{{modification-time(%Y-%m-%d)}}} :args (%Y-%m-%d) :begin 1 :end 34 :post-blank
0 :parent #0)))'
Error was: (stringp ((macro (:key modification-time :value
{{{modification-time(%Y-%m-%d)}}} :args (%Y-%m-%d) :begin 1 :end 34 :post-blank
0 :parent #1
Seemingly this macro wreaks havoc with the automatic sitemap
generation...
Thanks
Dieter
>
> Regards,
--
Best wishes
H. Dieter Wilhelm
Darmstadt
Germany
[O] best way of customizing generated css to match bootstrap css
Hi, After using jekyll and o-blog a while I just fiddled around more in depth with org-publishing. I must say it is starting to convince me to stop using to wrapp my org generated html files with a wrapper like jekyll etc. Org-publishing seems to have all I need to do it directly. But I need an advice how to get better integration with twitter bootstrap css which I realy like. I know there is HTML_CONTAINER_CLASS etc. but I don't want to define the class and the id once for every heading, table etc. What would be the best option for setting this globally? Should I edit org-htmlize.el or something like this or is there a way of defining the different class names with an easier way? Regards Marc Seibert
Re: [O] Gmane orgmode down?
Hi Christian, Christian Moe writes: > Looks like gmane has a problem. The most recent message I see is 5 April > 10:05. Ah, thanks for confirming. I dropped an email to Lars, but I guess he knows. -- Bastien
Re: [O] Gmane orgmode down?
Hi, Looks like gmane has a problem. The most recent message I see is 5 April 10:05. Yours, Christian Bastien writes: > I'm reading emacs-orgmode through Gmane and was surprised to not see > any new message for the last few hours. Maybe Gmane does not deliver > emails properly -- can anyone confirm the problem is on Gmane and not > on my side ? > > I'm reading through the mailing list for now. > > Thanks,
[O] Gmane orgmode down?
I'm reading emacs-orgmode through Gmane and was surprised to not see any new message for the last few hours. Maybe Gmane does not deliver emails properly -- can anyone confirm the problem is on Gmane and not on my side ? I'm reading through the mailing list for now. Thanks, -- Bastien
Re: [O] css link colors for Worg are difficult to spot
On 1 Apr 2013, at 15:14, John Hendy wrote:
> I find the links difficult to spot in Worg sometimes, especially
> depending on monitor angle and current brightness setting. Is this an
> issue for anyone else?
>
> I fiddled around in /style/worg.css a bit and didn't land on anything
> too great. I'm wondering if anyone with a design background might have
> suggestions for link colors? I guess if no one else is affected by
> this... I'll just deal with it and mine sweep wildly with my mouse
> when I think a link should be in there somewhere :)
In the old days lines used to be underlined, nowadays it is considered a bit
dated, but an underlined item in a sentence is generally understood to be a
link.
A good example is http://docs.webplatform.org/wiki/html/elements/a
Which uses:
a { text-decoration: underline }
and for external links:
a.external {
padding-right: 15px;
margin-right: 5px;
background-image: url(skins/webplatform/images/link-external.png);
background-repeat: no-repeat;
background-position: right 3px;
}
Design as this won't do on behance or dribble, but worg is primarily for
documentation. Usability and readability should trump superficial aesthetics in
a case like this.
Re: [O] Org as a static site generator
On Fri, Apr 05, 2013 at 11:02:56AM -0500, Christopher Allan Webber wrote: > Ian Barton writes: > > > On 01/04/13 13:08, Vincent Beffara wrote: > > > >> Yes, I mean, I know which html you need for that, simply within o-blog you > >> need to manage between relative paths, absolute paths, canonical paths and > >> so on in the template, to match the right section, - mainly it should be > >> a matter of let-ing the right variable to the right value at the right > >> point in the template and catching it when generating the toc, but I never > >> took the time to get it right ... > >>> I've also just found this, which uses Org only as a markup tool and > >>> Jekyll to generate the site: > >>> > >>> http://orgmode.org/worg/org-tutorials/org-jekyll.html > >> I had a look at the too, but it felt just a little bit too convoluted > >> compared to managing everything from Org. Besides, it seems to lose > >> fontification of code snippets and the like? > >> > >> /v > >> > > As the original author of that page, I agree that using Jekyll is > > convoluted, but it gives you much more control. However I now use > > Pelican: https://pelican.readthedocs.org/en/3.1.1/ > > > > There are a few reasons for this. Pelican is written in Python, which I > > find easier to hack on. It is more flexible than Jekyll, which I found > > hard to get to work the way I wanted with categories and tags. > > > > I wrote a yaml importer for Pelican so I could use my old jekyll posts. > > However, Pelican understands Markdown, which I think the new exporter > > supports. > > > > So my work flow now is Emacs-> export as html -> run Jekyll > > > > Ian. > > Heya Ian, > > I've been planning to switch my blog over to pelican. It's cool to hear > you say this. > > Is there any special elisp you use for the export, including converting > things like the title, etc? > > Thanks! > - Chris Hi Chris, No, nothing special. I just use org's standard publish functions. However, I publish only the body part of the html and place the yaml tags in the org file. A typical org file for a blog post would look like: #+STARTUP: showall indent #+STARTUP: hidestars #+OPTIONS: H:2 num:nil tags:nil toc:nil timestamps:nil #+BEGIN_HTML --- title: My Fire Steel Crumbles to Dust. date: 2013-02-17 tags: [gear] category: blog --- #+END_HTML After my walk over Moel Famau and Moel Arthur I was looking forward to making a hot drink. My brew kit lives permanently in the boot of org pubish then creates a file with a yaml header and html body text. Then I just run Pelican to publish the post. I have written a Pelican yaml reader which converts the yaml files to allow Pelican to process them. I'll document the whole process over the next couple of days and put it on Worg. I keep meaning to contribute my yaml reader back to Pelican, but it's quite specific to publishing org-mode files and not really a general purpose yaml importer. -- Best wishes, Ian.
