Bug: Hole in `org-html-format-drawer-function' variable documentation [9.4.4 (9.4.4-21-g61336f-elpaplus @ /home/jmazon/.emacs.d/elpa/org-plus-contrib-20210208/)]
Hello, The documentation for customizable variable `org-html-format-drawer-function' currently reads as such: Function called to format a drawer in HTML code. The function must accept two parameters: NAME the drawer name, like "LOGBOOK" CONTENTS the contents of the drawer. The function should return the string to be exported. For example, the variable could be set to the following function in order to mimic default behavior: The default value simply returns the value of CONTENTS. There is obviously something missing between the two last paragraphs. Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30) of 2020-10-08 Package: Org mode version 9.4.4 (9.4.4-21-g61336f-elpaplus @ /home/jmazon/.emacs.d/elpa/org-plus-contrib-20210208/)
Re: [O] ODT exporter does not seem to respect quotation mark for list items
Hi, I do confirm that it is fixed for me. Thank YOU. -- *Le jeu., juil. 24 2014, Nicolas Goaziou a écrit* Hello, This should be fixed in maint. Thank you for reporting it. Regards, -- Nicolas Goaziou -- ~~^v^~~ Baptiste
[O] ODT exporter does not seem to respect quotation mark for list items
Hi, I do not manage to get all my lists correctly exported in odt. The main point seems the respect of quotation marks … See example below. Thank you, -- ~^v^~ Baptiste - #+TITLE: Test for lists in quotes and Odt export #+AUTHOR: Baptiste #+DATE: 2014-07-23 * Rational =ODT= exporter does not seem to manage quotation style for lists (may be other elements). : org-mode 8.3.15.g2241054 (git) * Org source #+BEGIN_QUOTE This is a quotation text, with a list inside - First item 1. sub item 2. second sub-item - Second item Text in quote after the list #+END_QUOTE I am now out of quote * From odt file, =content.xml= The list is made out of /Quotation/ style, then back to normal margin and so on. #+BEGIN_SRC xml Org source This is a quotation text, with a list inside First item sub item second sub-item Second item Text in quote after the list I am now out of quote #+END_SRC * What I would expect I would expect the /Quotation/ style to be respected even in list item, something like : #+BEGIN_SRC xml Org source This is a quotation text, with a list inside First item sub item second sub-item Second item Text in quote after the list I am now out of quote #+END_SRC
[O] Org entries from tables
Hi, it is a nice feature to be able to export structured org entries as a table (through column view generated table). Is there a way back (or the other way), that is, create org entries with associated properties from a table. Lot of people is using spreadsheet to organise its data, then it would be nice if their is an easy way to import this information formated as table into an org file (structured as org entries, which is better for in many ways). Thanks. --- Bat.
[O] Internal link with custom caption
Hi, I would like to be able to manage internal link that is exported with a custom reference text. I mean define somewhere an anchor *plus the reference caption* and then use link mechanism to create a reference to this point with its given caption. I do not find a way to do so. Has I imagine it, it would look like #+BEGIN_EXAMPLE * Books Presentation of the <>. … some text … * What you have to read … you should have a look at [[ref_book_1]] … … some text … * Where to find books … [[ref_book_1]] is a free book from … #+END_EXAMPLE that would export as #+BEGIN_EXAMPLE * Books Presentation of the /Important Book/. … some text … * What you have to read … you should have a look at /Important Book/ … ### (as a link to <>) … some text … * Where to find books … /Important Book/ is a free book from …### (as a link to <>) #+END_EXAMPLE Did I miss something and there is a way to achieve this ? Or am-I the only one looking for such a function ? Thank you -- : ~^v^~ Bat
Re: [O] ox-taskjuggler : Correct a small typo and deal with Scheduled and deadline in task
Hi, you will find hereafter the patch after the little cleanup. BTW, there is a way (by code reading, not tested) to force a milestone with both start and end : if I am not wrong, you may use a :milestone property of an org-entry to create a milestone task. Not to say that it is not advised to both use :start properties and :SCHEDULED mechanism in an org entry (you would end with two /start/ elements in tj3). *Le lun., avril 22 2013, Christian Egli a écrit* Bastien writes: > Hi Baptiste and Christian, > > Christian Egli writes: > >> This looks a bit fishy. Shouldn't this be >> >> ((start) (format " start %s\n" start)) > > I guess this should be > > (start (format " start %s\n" start)) Doh, yes of course. -- : ~^v^~ Bat >From d36be8faf6ecbc722d75950f5bc664f2b9d87e27 Mon Sep 17 00:00:00 2001 From: Baptiste Fouques Date: Mon, 22 Apr 2013 10:59:15 +0200 Subject: [PATCH] ox-taskjuggler.el: use :SCHEDULED and :DEADLINE as start and end for tasks as a special behavior, for milestones, if both :SCHEDULED and :DEADLINE ar specified, then :SCHEDULED will be mark as the milestone date, and :DEADLINE will be checked against actual scheduled date by TJ3. TINYCHANGE --- contrib/lisp/ox-taskjuggler.el | 10 ++ 1 file changed, 10 insertions(+) diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el index 4724ec3..2c1dee7 100644 --- a/contrib/lisp/ox-taskjuggler.el +++ b/contrib/lisp/ox-taskjuggler.el @@ -754,6 +754,8 @@ a unique id will be associated to it." (org-element-property :COMPLETE task))) (depends (org-taskjuggler-resolve-dependencies task info)) (effort (org-element-property :EFFORT task)) + (start (org-taskjuggler-get-start task)) + (end (org-taskjuggler-get-end task)) (milestone (or (org-element-property :MILESTONE task) (not (or (org-element-map (org-element-contents task) 'headline @@ -775,6 +777,14 @@ a unique id will be associated to it." (org-taskjuggler-get-id task info) (org-taskjuggler-get-name task)) ;; Add default attributes. + (and milestone + (cond + ((and start end) (format " start %s\n maxend %s\n" start end)) + (start (format " start %s\n" start)) + (end (format " start %s\n" end + (and start (not milestone) (format " start %s\n" start)) + (and end (not milestone) (format " end %s\n" end)) + (and depends (format " depends %s\n" (org-taskjuggler-format-dependencies depends task info))) -- 1.8.1.2
[O] ox-taskjuggler : Correct a small typo and deal with Scheduled and deadline in task
Hi, hereafter a small typo correction, plus the capability to use DEADLINE: and SCHEDULED: in task (special export format for milestones). -- : ~^v^~ Bat ox-taskjuggler : Correct a small typo and deal with Scheduled and deadline in task diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el index 16f0e8d..113aa29 100644 --- a/contrib/lisp/ox-taskjuggler.el +++ b/contrib/lisp/ox-taskjuggler.el @@ -754,16 +754,18 @@ a unique id will be associated to it." (org-element-property :COMPLETE task))) (depends (org-taskjuggler-resolve-dependencies task info)) (effort (org-element-property :EFFORT task)) + (start (org-taskjuggler-get-start task)) + (end (org-taskjuggler-get-end task)) (milestone (or (org-element-property :MILESTONE task) (not (or (org-element-map (org-element-contents task) 'headline @@ -775,6 +777,14 @@ a unique id will be associated to it." (org-taskjuggler-get-id task info) (org-taskjuggler-get-name task)) ;; Add default attributes. + (and milestone + (cond + ((and start end) (format " start %s\n maxend %s\n" start end)) + ((and start) (format " start %s\n" start)) + ((and end) (format " start %s\n" end + (and start (not milestone) (format " start %s\n" start)) + (and end (not milestone) (format " end %s\n" end)) + (and depends (format " depends %s\n" (org-taskjuggler-format-dependencies depends task info))) @@ -790,7 +800,7 @@ a unique id will be associated to it." (let* ((minutes (org-duration-string-to-minutes effort)) (hours (/ minutes 60.0))) (format "%.1fh" hours - (and priority (format " priority %s\n" complete)) + (and priority (format " priority %s\n" priority)) (and milestone " milestone\n") ;; Add other valid attributes. (org-taskjuggler--indent-string
Re: [O] Taskjuggler export deals badly with first parent match
This patch works fine for me. Thanks I still have other issues in my move to the new exporter, but I am moving forward (then I am sorry if I report problems one after another). Regards, -- *Le ven., avril 19 2013, Nicolas Goaziou a écrit* Hello, Baptiste writes: > I found ox-taskjuggler broken in /task_id/ identification when it is > non trivial. Oops. It looks like I made a typo. Thank you for reporting it. Would the following patch solve the problem? Regards, -- : ~^v^~ Bat --text follows this line--
Re: [O] Taskjuggler export deals badly with first parent match
This patch works fine for me. Thanks I still have other issues in my move to the new exporter, but I am moving forward (then I am sorry if I report problems one after another). Regards, -- *Le ven., avril 19 2013, Nicolas Goaziou a écrit* Hello, Baptiste writes: > I found ox-taskjuggler broken in /task_id/ identification when it is > non trivial. Oops. It looks like I made a typo. Thank you for reporting it. Would the following patch solve the problem? Regards, -- : ~^v^~ Bat
[O] Taskjuggler export deals badly with first parent match
Hi,
first of all, thanks for the hard work to make 8.0 get out.
I found ox-taskjuggler broken in /task_id/ identification when it is non
trivial.
here is an example this is not fine at my side
: Org-mode version 8.0 (release_8.0-1-g5ef07d @ …)
#+BEGIN_EXAMPLE
* Project :taskjuggler_project:
** Training material
:PROPERTIES:
:task_id: training_material
:END:
*** Markup Guidelines
:PROPERTIES:
:Effort: 2d
:task_id: markup
:END:
*** Workflow Guidelines
:PROPERTIES:
:Effort: 2d
:END:
** Presentation
:PROPERTIES:
:Effort: 2d
:BLOCKER: markup
:END:
#+END_EXAMPLE
At export, it gives
#+BEGIN_EXAMPLE
task project "Project" {
purge allocate
allocate cancelled
task training_material "Training material" {
task markup "Markup Guidelines" {
effort 16.0h
}
task workflow "Workflow Guidelines" {
effort 16.0h
}
}
task presentation "Presentation" {
depends !!training_material.markup
effort 16.0h
}
}
#+END_EXAMPLE
which fails compiling (for good reasons) with
: Error in scenario plan: Task project.presentation has unknown depends
training_material.markup
actually, the line
: depends !!training_material.markup
should be
: depends !training_material.markup
– this is an easy fix is this baby example, but on my whole project, I have
tons of false references :'( –
again, thanks :)
--
: ~^v^~ Bat
Re: [O] Sync Org with Google Calendar using google API (rather than caldav)
Adam Spiers adamspiers.org> writes: > Sounds interesting. It would be very helpful if you could explain how it is > different from the other synchronization possibilities out there, e.g. > > http://orgmode.org/worg/org-tutorials/org-google-sync.html > https://code.google.com/p/emacs-google/ > https://github.com/travisbhartwell/Emacs-Google-Calendar-Sync > http://www.emacswiki.org/emacs/GoogleClient two main things make my sync different (also this does not make it more interesting ;) - it does not rely on external command - it does not rely on ics I always found that relying on external commands makes thing more complex : you have to configure that command, in its configuration file or through scripted call by passing right arguments, and then you have to integrate it in your Emacs workflow. Using command in Emacs, configured through convenient customization group is so natural … Then, my sync. uses Google json API (and authentification using oauth, stored in crypted file, for no secret in your config file or anywhere else). This make it by far less portable. But, with Google dropping standards, or juts maintaining it at there minimal level, it makes it more close to what you can get from Google calendar and events. Also using elisp Json library is so easy and robust in regard to parsing ics files that it sounds very natural to use it. I don't mean it is better than caldav sync tools, but that I could not find myself satisfied with those tools, worried about Google call to drop caldav compatibility, that I feel I need something more close to Google API possibilities. Then I started it, and just offer to share (that how it works, right ? ;) Thanks for the work of the community, Bat.
[O] Sync Org with Google Calendar using google API (rather than caldav)
Hi, I have started a google calendar synchronization Emacs module. Rather than using ical format, I use directly Google API. For sure it is less usefull for other calendar services, but it will keep working when Google is stopping supporting caldav. For now, only fetch from Google is implemented, but extension (then push and sync) should be quiet easy to manage. You will find it here (github). If this can be usefull for you, -- ~^v^~ Bat
[O] flet fixed in emacs trunk (Was: Is Org mode gonna break on emacs 24.50.1x ?)
Hi all, thanks for your answers, I do confirm that 'flet' is now working in emacs following emacs patch http://lists.gnu.org/archive/html/emacs-devel/2012-06/msg00515.html Org mode is working like a charm with in emacs, trunk version. -- ~^v^~ Bat Baptiste Fouques writes: > Hi, > > thanks all for org. > > I wonder whether org-mode is going to break badly on next emacs > cleanup. > > --- > commit 1e211d886c96420904ad197cfee7fce7ae7b9d83 (HEAD, refs/heads/master) > Author: Stefan Monnier > Date: Fri Jun 22 09:42:38 2012 -0400 > > … > * lisp/emacs-lisp/cl.el (flet): Don't autoload. > … > --- > > Makes my org not working in several places (babel, coupling with > remenber, …). I think that the point in using 'flet' has appears > several times in this group. It seems to become more crucial here. > > Don't think that the problem of emacs, but org … > > Thanks.
[O] Is Org mode gonna break on emacs 24.50.1x ?
Hi, thanks all for org. I wonder whether org-mode is going to break badly on next emacs cleanup. --- commit 1e211d886c96420904ad197cfee7fce7ae7b9d83 (HEAD, refs/heads/master) Author: Stefan Monnier Date: Fri Jun 22 09:42:38 2012 -0400 … * lisp/emacs-lisp/cl.el (flet): Don't autoload. … --- Makes my org not working in several places (babel, coupling with remenber, …). I think that the point in using 'flet' has appears several times in this group. It seems to become more crucial here. Don't think that the problem of emacs, but org … Thanks. -- ~^v^~ Bat
Re: [Orgmode] Latex export format control - emphasis and radio link
Hi, thank you for having answered quickly my questions On Thu, Dec 24, 2009 at 9:31 AM, Carsten Dominik wrote: > first of all, why don't you just use not-a-lint instead of not_a_link? > Using underscore sort-of asks for problems in this context. Guess that I am not really looking for problems (I am not this type of guy ;) ), but where I work, symbol names are defined with underscores as word separators, and I need a tool that handle it ... And I prefer facing the the problems when they come (well, first trying to find the correct way, before asking for help). > Also, why do you want the links to be in typewriter font? still, it is about symbol names ... so the typewriter font, Then they are defined once, then any reference should link to the definition ... > This is unusual. > Maybe instead of modifying org-emph-alist, you'd want to add to it and > create a new emphasis with is texttt but not verbatim? It do work, thanks for the advice. Also now I have to handle to prefix for word that are radio-linked and those who are not ... >> <<>> > > it is indeed a bug that this is not exported with escaped underscores. > I have fixed this issue. Thank you. Got it and confirm that it works. Have a good Christmas --- Bat ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Latex export format control - emphasis and radio link
Hi,
I am using Org for a while, and I actually do like it a lot. I'd like
to extend my usage a bit, but I have some difficulties with export
format.
Basically, my point is about expanding/escaping control sequences in
latex output.
My sample org file is :
#+TITLE: Org Test
#+AUTHOR:Baptiste Fouques
#+EMAIL: b...@m4tp.org
#+DESCRIPTION: org mode link test
#+OPTIONS: ^:nil
* org-export-latex-emphasis-alist difficutlies
# <<>>
=link_radio=
=not_a_link=
* Radio Link format
<<>>
EOF-
What I would expect as a Latex export would be :
\section{org-export-latex-emphasis-alist difficutlies}
\label{sec-1}
\label{link_radio}
\texttt{\hyperref[link_radio]{link\_radio}}
\texttt{not\_a\_link}
\section{Radio Link format}
\label{sec-2}
\label{other_radio_link}other\_radio\_link
EOF
But, I naturally get
...
\texttt{[[link\_radio][link\_radio]]} {1}
...
\label{other_radio_link}other_radio_link {2}
which does not work at all as {1} is just a no-sense for LaTeX, and
{2} has not escaped the _ in plain text output (also the org header
has #+OPTIONS: ^:nil ).
I can manage to get {1} quite correct, manipulating
org-export-latex-emphasis-alist : ( ... ("=" "\\texttt{%s}" nil) ... )
...
\texttt{\hyperref[link_radio]{link\_radio}}
...
but then, =not_a_link= became naturally broken ( _ are no more escaped ... )
And I found no such parameter that can be used to manipulate radio
link export format (to get <<>> beeing exported as
\label{other_radio_link}other\_radio\_link .
If you could help me on this issue, I will be able to use Org mode
more widely in my everyday work (and propose it to my co-worker).
Thanks a lot,
---Bat
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
