Re: [O] Bug: org-babel-tangle purges comma at the beginning of a line ]
Hello,
Simon Campese writes:
> I just noticed that org-babel-tangle removes the comma if its at the
> beginning of a line inside a source block. This seems to be independent from
> the
> language indicated (tried with sh, js and emacs-lisp) and also
> independent from the characters that follow (',' gets tangled to a blank
> line, ',,,' gets tangled to ',,', ',sometext' gets tangled to 'sometext'
> etc.).
That looks like a bug, indeed. Thank you for reporting it.
Would the following patch fix it?
Regards,
--
Nicolas Goaziou
>From c9dc22ea651056d6411dd27b57a252007d97bc00 Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou
Date: Wed, 27 Feb 2013 08:58:32 +0100
Subject: [PATCH] ob-tangle: Correctly unescape code when tangling
* lisp/ob-tangle.el (org-babel-spec-to-string): Use dedicated function
for unescaping code.
---
lisp/ob-tangle.el | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lisp/ob-tangle.el b/lisp/ob-tangle.el
index 6c79794..2c2e7dd 100644
--- a/lisp/ob-tangle.el
+++ b/lisp/ob-tangle.el
@@ -346,8 +346,7 @@ form
(insert
(format
"%s\n"
- (replace-regexp-in-string
- "^," ""
+ (org-unescape-code-in-string
(org-babel-trim body (if org-src-preserve-indentation "[\f\n\r\v]")
(when link-p
(funcall
--
1.8.1.4
[O] Exporter interface question
Hi, I have a question about the exporter dispatcher. I much appreciate that `C-u C-c C-e' repeats the previous export action, that is extremely useful. I often only export a subtree of a document, and I was wondering if others would also find this proposal useful: When exporting a subtree, lets drop a mark at the headline and then go to this mark when C-c C-e is called with a prefix arguments. This would allow to keep the cursor somewhere deep in the subtree while working on it, and still be able to quickly repeat the export command. If others would find this useful, I'd make a patch. - Carsten
[O] BUG copyright sign
When evaluating the source examples attached, it fails sending Traceback (most recent call last): File "", line 1, in UnicodeEncodeError: 'ascii' codec can't encode character u'\xa9' in position 0: ordinal not in range(128) UnicodeEncodeError-lp-550661-test.org Description: Lotus Organizer
Re: [O] [PATCH] ox-latex: provide width and height options for images
Hello,
Aaron Ecay writes:
Thank you for your patch. Here are a few comments.
> These are implemented with \resizebox, and thus are uniform across
> different types of image inclusion (\includegraphics, \input of tikz
> images). This differs from the older way of using width and height
> optional args to \includegraphics.
I tend to agree with Rasmus. It would be better to keep height and width
options in \includegraphics when possible.
> Thus, the default value for org-latex-image-default-options is left
> untouched, to avoid breaking compatibility with older code. After a
> transition period, the 0.9\linewidth value should be moved into
> org-latex-image-default-width, and the -options variable set to the
> empty string.
We don't need this precaution. The exporter code for 8.0 introduced many
incompatibilities already. Also, this one is easy to discover.
> +(defun org-not-nil-or-empty (v)
> + "Return V if V is not nil, the string \"nil\", or a string
> +consisting of solely whitespace. Otherwise return nil."
> + (and (org-not-nil v)
> + (org-string-nw-p v)
> + v))
I'm not sure it's worth creating a new function for it. Anyway, the
first line of a docstring should be a sentence on its own.
> (defcustom org-latex-image-default-option "width=.9\\linewidth"
>"Default option for images."
>:group 'org-export-latex
>:type 'string)
We can set it to "".
> +(defcustom org-latex-image-default-width ""
> + "Default option for images."
> + :group 'org-export-latex
> + :type 'string)
> +
> +(defcustom org-latex-image-default-height ""
> + "Default option for images."
> + :group 'org-export-latex
> + :type 'string)
I think it's a good step forward. It will need to be documented in the
comments at the beginning of ox-latex.el, where all attributes
properties relative to different syntactical elements are explained.
> (defcustom org-latex-default-figure-position "htb"
>"Default position for latex figures."
>:group 'org-export-latex
> @@ -1755,6 +1768,15 @@ used as a communication channel."
> (format "[%s]" org-latex-default-figure-position))
> (t ""
>(comment-include (if (plist-get attr :comment-include) "%" ""))
> + ;; It is possible to specify width and height in the
> + ;; ATTR_LATEX line, and also via default variables.
> + (width (format "%s" (or (plist-get attr :width)
> + org-latex-image-default-width)))
> + (height (format "%s" (or (plist-get attr :height)
> + org-latex-image-default-height)))
> + (resize (format "\\resizebox{%s}{%s}{%%s}"
> + (if (org-not-nil-or-empty width) width "!")
> + (if (org-not-nil-or-empty height) height "!")))
Here, you can obtain \resizebox{!}{!}{%s}, which is wrong, isn't it?
>;; Options for "includegraphics" macro. Make sure it is
>;; a string with square brackets when non empty. Default to
>;; `org-latex-image-default-option' when possible.
> @@ -1766,9 +1788,10 @@ used as a communication channel."
> ((eq float 'float) "[width=0.7\\textwidth]")
> ((eq float 'wrap) "[width=0.48\\textwidth]")
> (t ""
This needs to be changed as these options would interfere with :width
argument. For example, (eq float 'float) could set :width property if it
is undefined. Obviously, this means the check has to be done before
WIDTH and HEIGHT strings are built.
> - (image-code (if (equal filetype "tikz")
> - (format "\\input{%s}" path)
> -(format "\\includegraphics%s{%s}" options path
> + (image-code (format resize
> + (if (equal filetype "tikz")
> + (format "\\input{%s}" path)
> +(format "\\includegraphics%s{%s}" options
> path)
See comments above.
Thank you again,
Regards,
--
Nicolas Goaziou
Re: [O] BUG copyright sign
Andreas Röhler writes: > When evaluating the source examples attached, it fails sending > > Traceback (most recent call last): > File "", line 1, in > UnicodeEncodeError: 'ascii' codec can't encode character u'\xa9' in position > 0: ordinal not in range(128) This is a Python error, not an Org error. I guess you are using Python 2.x? The way Python handles encoding changed in Python 3.0. -- Bastien
Re: [O] logdone enhancement
Hi Arun, Arun Persaud writes: > * project > ** TODO headline :repeat: >a longer description of what the todo item is about >SCHEDULED: <2013-06-18 Tue +1m> The SCHEDULED line should be right after the headline, see the manual. It can sometimes work when it is on another line, but this is accidental, you should put the line right after the headline. HTH, -- Bastien
Re: [O] [org-contacts] need help for making gnus/message-mode integration optional
Hi Simon, Simon Campese writes: > My reason for this request: > For email address completion in message mode, I use a program that scans > through my whole email database (I use notmuch to manage emails and have > all my mails stored locally). This program is stored in > 'notmuch-address-command' and the integration has so far been done by > 'notmuch-address'. However, the recent version of org-contacts breaks > this behaviour, i.e. I only get the emails from my org-contacts file > when I try to complete recipients. As I don't want to add all the people > I correspond with electronically to my org-contacts file, this is a huge > annoyance. CC'ing Grégoire, as I think this is related to a change he made. Grégoire, do you know how to fix this? Thanks! -- Bastien
Re: [O] 5f095f5 is the first bad commit (for my use case)
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> Since updating to latest Org this morning, I couldn't open anymore my file
>> ~/org/work.org.
>>
>> Symptom? Org-mode gets loaded, but buffer remains blank, and Emacs is
>> (apparently) inflooping, with letting me stop it (with C-g).
>>
>> Solution? Kill Emacs through the task manager, and bisect:
>>
>> ╭
>> │ 5f095f59099e77eda5cf7cae64119f9f246c4c70 is the first bad commit
>> │ commit 5f095f59099e77eda5cf7cae64119f9f246c4c70
>> │ Author: Nicolas Goaziou
>>
>> │ Date: Sun Feb 10 00:07:48 2013 +0100
>> │
>> │ Fontify latex, entities and sub/superscript again
>> ╰
>>
>> Now, having my Git tip on commit 3f95d81, everything's OK. I can work again,
>> but the most difficult problem is that I don't see how to debug further the
>> above problem.
>>
>> Any idea why this fails?
>
> Probably an infloop, as you suggest. It would be great if you could
> provide an ECM (even not "M") for that problem. You can send it through
> private mail if you want.
>
> Also, what's your value for `org-highlight-latex-and-related'?
You've directly put me on the right track: some (untested) code I added just
before leaving on vacation...
--8<---cut here---start->8---
;; highlight LaTeX and related syntax
(setq org-highlight-latex-and-related
'('latex
'script
'entities))
--8<---cut here---end--->8---
This is obviously wrong (shame on me!), but has the interesting effect of
causing an infloop on opening Org files...
Thanks!
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [PATCH] ob-core: do not ask for confirmation if cached value is current
Hi Achim, Achim Gratz writes: > Babel asks for confirmation to evaluate a source block even when it is > going to use the cached value. This patch skips the superfluous > confirmation in that case (no evaluation takes place, the cached value > is used). thanks for the patch. I applied it but renamed cache? and cache-current? to cache-p and cache-current-p. Let's avoid the ? character in variables and functions, as this character is not self-inserted when in the prompt of C-h v and C-h f, you have to use C-q ? to insert it. -- Bastien
Re: [O] Exporter interface question
Hello, Carsten Dominik writes: > I much appreciate that `C-u C-c C-e' repeats the > previous export action, that is extremely useful. > > I often only export a subtree of a document, and I > was wondering if others would also find this proposal > useful: > > When exporting a subtree, lets drop a mark at the > headline and then go to this mark when C-c C-e is > called with a prefix arguments. This would allow > to keep the cursor somewhere deep in the subtree while > working on it, and still be able to quickly repeat the > export command. It would be nice indeed. Though, it may be useful to put some additional limitations to this feature. For example, it would trigger only when on the same buffer as before, perhaps even within the same subtree. What do you think about it? > If others would find this useful, I'd make a patch. Be my guest. ;) Regards, -- Nicolas Goaziou
Re: [O] BUG copyright sign
Am 27.02.2013 09:30, schrieb Bastien: Andreas Röhler writes: When evaluating the source examples attached, it fails sending Traceback (most recent call last): File "", line 1, in UnicodeEncodeError: 'ascii' codec can't encode character u'\xa9' in position 0: ordinal not in range(128) This is a Python error, not an Org error. I guess you are using Python 2.x? The way Python handles encoding changed in Python 3.0. Forms work from all Python shells > python Python 2.7.3 (default, Apr 14 2012, 08:58:41) [GCC] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> print(u'\xA9') © >>> quit() > python3 Python 3.3.0 (default, Oct 01 2012, 09:13:30) [GCC] on linux Type "help", "copyright", "credits" or "license" for more information. >>> print(u'\xA9') © >>> print(u'\u00A9') © >>> AFAIS bug is caused by calling shell-command-on-region
Re: [O] Exporter question
Nicolas Goaziou writes: > Done. > > Node property is ALT_TITLE and function is > `org-export-get-alt-title'. Thanks! -- Bastien
[O] Inserting a comma as prefix of headlines (in Org code blocks)
Hello, Consider this Org block: #+begin_src org * Headline inside an Org block Text of that entry. #+end_src I don't remember exactly why (I think, sometimes, TAB'ing did not work properly to prefix the dangerous lines with a `,'), I had to do it manually: go and prefix every headline of the Org code block. #+begin_src org ,* Headline inside an Org block Text of that entry. #+end_src That worked for long, but not anymore since a couple of weeks (could be something like 2 months or so): currently, if you go in column 0 of the headline, and insert `,', you get asked: "Priority A-C, SPC to remove: " IMHO, such a question should not be asked, and the `,' should be inserted literally, as we're in the context of a code block. Best regards, Seb -- Sebastien Vauban
Re: [O] tangle multiple code blocks belonging to the same file
Hi Zech, Not To Miss writes: > I know C-u C-c C-v t tangles current code block only, even if there > are other code blocks that have the same tangle file name. Isn't it > counterintuitive? It makes more sense that this command tangles all > the code blocks that belongs to the same file, in my opinion. Any > other ideas? Maybe `C-u C-u C-c C-v t' could tangle blocks from the same target file, so that we don't need to change users' habits with `C-u C-c C-v t'. But for now IIURC it is not possible to collect blocks for the same target file. I think it would be a very nice addition. Eric, would that be difficult to implement? Or maybe I miss it in the code and we just need a keybinding for this? Thanks for the suggestion, -- Bastien
Re: [O] BUG copyright sign
Hi Andreas, Andreas Röhler writes: > Forms work from all Python shells You need to test the form in a regular shell, not a Python shell. See `org-babel-sh-command'. > AFAIS bug is caused by calling shell-command-on-region See above, and edebug-defun `org-babel-shell-command-on-region' to see what's wrong here. -- Bastien
[O] Shortcuts for setting or changing the warning period "-3d" in DEADLINE timestamps?
I often use individual warning periods for defining how many days before the DEADLINE the task will show up in my agenda like DEADLINE: <2013-02-27 Wed -3d> However, it seems not to be possible to enter this warning period directly when defining a date with the calendar e. g. by C-C C-D. Is there a syntax to enter warnings here directly? If not, could it be defined, please? :-) IMHO it would also be helpful to have a shortcut to directly modify the warning period of an item with a timestamp in the agenda. (like it is possible with Shift+Left/Right Arrow to modify the date day by day). Kind regards Martin
Re: [O] logdone enhancement
Hi Bastien, Bastien wrote: > Arun Persaud writes: > >> * project >> ** TODO headline :repeat: >>a longer description of what the todo item is about >>SCHEDULED: <2013-06-18 Tue +1m> > > The SCHEDULED line should be right after the headline, see the manual. > It can sometimes work when it is on another line, but this is > accidental, you should put the line right after the headline. Now that this "syntax order" is enforced, will we get commit 6b04bef back in Org 8? That'd be great... Best regards, Seb PS- See discussion on http://lists.gnu.org/archive/html/emacs-orgmode/2011-08/msg01248.html and https://lists.gnu.org/archive/html/emacs-orgmode/2011-09/msg00219.html -- Sebastien Vauban
Re: [O] [PATCH] ob-core: do not ask for confirmation if cached value is current
Bastien altern.org> writes: > thanks for the patch. I applied it but renamed cache? and > cache-current? to cache-p and cache-current-p. Thanks. I have no preference either way regarding the names, I was just following the example of cache?, which I copied from the original code. There's another "cache?" in ob-lob, IIRC. Regards, Achim.
Re: [O] BUG copyright sign
Am 27.02.2013 10:12, schrieb Bastien: Hi Andreas, Andreas Röhler writes: Forms work from all Python shells You need to test the form in a regular shell, not a Python shell. Hi Bastien, do you mean this: > python -c "print(u'\xA9')" © > python -c "print(u'\u00A9')" © > python3 -c "print(u'\xA9')" © > python3 -c "print(u'\u00A9')" © > See `org-babel-sh-command'. AFAIS bug is caused by calling shell-command-on-region See above, and edebug-defun `org-babel-shell-command-on-region' to see what's wrong here. Well, that was a long-time bug in python-mode, so I'm not surprised to find it here. BTW org-babel solution looks quite interesting. Just porting existing fix might not be the best. Need to investigate it further. Cheers, Andreas
Re: [O] [PATCH] ob-core: do not ask for confirmation if cached value is current
Achim Gratz writes: > There's another "cache?" in ob-lob, IIRC. Fixed, thanks. -- Bastien
Re: [O] Bug: Lisp error: (wrong-type-argument listp t) at startup [7.9.3f (release_7.9.3f-10-g2b13d0 @ /home/horn/Repos/el/org-mode/lisp/)]
Bastien writes: Hi Basien, >> since I've updated my org git clone today, I get the following error >> on emacs startup. > > Fixed, thanks. Confirmed, thanks. Bye, Tassilo
Re: [O] new version of org-mew.el
Bastien altern.org> writes: > I applied this patch: > http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=7604fe1 Some functions / variables from mew should be pre-declared or mew needs to be required. Regards, Achim.
Re: [O] Shortcuts for setting or changing the warning period "-3d" in DEADLINE timestamps?
Hi Martin, Martin Beck writes: > However, it seems not to be possible to enter this warning period directly > when > defining a date with the calendar e. g. by C-C C-D. > Is there a syntax to enter warnings here directly? Nope. > If not, could it be defined, please? :-) Patch welcome :) But... > IMHO it would also be helpful to have a shortcut to directly modify the > warning > period of an item with a timestamp in the agenda. (like it is possible with > Shift+Left/Right Arrow to modify the date day by day). C-c C-d RET C-u C-u C-c C-d s- s- s- RET will do it, so I don't think a specific syntax is needed here. HTH, -- Bastien
[O] Bad indentation with visual-line-mode
Hallöchen! For reasons I cannot understand, longlines-mode was dropped in bzr emacs. Thus, I have to use visual-line-mode with org-mode in order to achieve similar behaviour. This has two drawbacks: - There is no way to set the line width besides setting Emacs margins, which is visually less appealing than before. (Minor problem.) - Indentation in lists is essentially broken. I illustrate this by indenting this list as it now appears in my org-mode file. One can activate org-indent-mode but this is not the same as longlines-mode. Besides, I don't like the big indentations it creates for deeply nested content. Has anybody an idea how to solve my second point? Thank you! Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com
Re: [O] new version of org-mew.el
Achim Gratz writes: > Bastien altern.org> writes: >> I applied this patch: >> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=7604fe1 > > Some functions / variables from mew should be pre-declared Can you fix this? > or mew needs to be required. Mhh.. no, let's not require org-mew.el. IMHO org-mew.el should not be distributed in core but in contrib, as it is not useful for Emacs users that are not using Mew, and those using Mew can install contrib/. Same for wanderlust. So for now let's add the need declarations. Thanks! -- Bastien
Re: [O] 5f095f5 is the first bad commit (for my use case)
"Sebastien Vauban"
writes:
> You've directly put me on the right track: some (untested) code I added just
> before leaving on vacation...
>
> ;; highlight LaTeX and related syntax
> (setq org-highlight-latex-and-related
> '('latex
> 'script
> 'entities))
>
> This is obviously wrong (shame on me!), but has the interesting effect of
> causing an infloop on opening Org files...
I fixed the infloop. Thank you.
Regards,
--
Nicolas Goaziou
Re: [O] Inserting a comma as prefix of headlines (in Org code blocks)
Hi Sébastien, "Sebastien Vauban" writes: > IMHO, such a question should not be asked, and the `,' should be inserted > literally, as we're in the context of a code block. Fixed in master, thanks. -- Bastien
Re: [O] logdone enhancement
Hi Sébastien, "Sebastien Vauban" writes: > Now that this "syntax order" is enforced, will we get commit 6b04bef back in > Org 8? That'd be great... Why not. Can you heavily test commit 6b04bef and see if anything goes wrong? -- Bastien
Re: [O] How to make the new exporter open PDF using evince?
On Tue, Feb 26, 2013 at 10:40 AM, Martin Marier wrote: > Hi James, > > Here is a third vote for mailcap. I have (only) this in my .mailcap > file: > > application/pdf; okular '%s'; test=test -n "$DISPLAY" Just tried it. Mailcap for the win! > PS Cool to see a (notorious) sc user on this list as well. Ha! Well, let's not talk about my TODOs underneath "* SC stuff" that are still in TODO state... hjh
Re: [O] logdone enhancement
Bastien, Bastien wrote: > Hi Sébastien, > > "Sebastien Vauban" > writes: > >> Now that this "syntax order" is enforced, will we get commit 6b04bef back in >> Org 8? That'd be great... > > Why not. Can you heavily test commit 6b04bef and see if > anything goes wrong? I can try, though it already had been heavily tested back in that time. But first, For me, the question comes down to: do we agree that John (in this case) won't be allowed anymore to write such an entry? --8<---cut here---start->8--- *** NOTE Assets:Receivable:CEG #+begin_src sh :results value :exports results ledger reg --inject=Expected '^income:ceg' ledger reg --sort date -b 2007 receivable:CEG #+end_src :PROPERTIES: :ID: 8BEF6C42-8B23-495B-9421-3810B58907A1 :VISIBILITY: folded :CREATED: [2010-06-18 Fri 07:37] :END: --8<---cut here---end--->8--- Best regards, Seb -- Sebastien Vauban
Re: [O] [PATCH] ob-core: do not ask for confirmation if cached value is current
Bastien altern.org> writes: > thanks for the patch. I applied it but renamed cache? and > cache-current? to cache-p and cache-current-p. That patch needs amending. You let-bind cache-current, but then try to use cache-current-p. Regards, Achim.
Re: [O] 5f095f5 is the first bad commit (for my use case)
Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> You've directly put me on the right track: some (untested) code I added
>> just before leaving on vacation...
>>
>> ;; highlight LaTeX and related syntax
>> (setq org-highlight-latex-and-related
>> '('latex
>> 'script
>> 'entities))
>>
>> This is obviously wrong (shame on me!), but has the interesting effect of
>> causing an infloop on opening Org files...
>
> I fixed the infloop. Thank you.
Thanks!
Do you know if there was a way out -- other than killing Emacs -- in such a
case where `C-g' is not working?
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [patch] ox-koma-letter
On Tue, Feb 26, 2013 at 10:14:28PM +0100, Rasmus wrote:
[...]
> > Wouldn't it be better to use Markus Kohm's concept of letter class
> > options to set all the static stuff?
>
> Potentially. What do you mean by "letter class options"? Are you
> referring to customized LCO files or do you refer to e.g. customized
> org-latex-classes?
I mean customized LCO files. For my former company I had made a letter
class for business letters based on scrlttr2.cls with two LCO files.
the first LCO file *company.lco* contained the general information about
the company (address, bank account, etc.). A second LCO file
*my_name.lco* contained the personal information of (e-mail address,
name, phone extension). With *my_name.lco* calling *company.lco* the
document class command for my letter finally was:
\documentclass[my_name]{our_company_letter_class}
With suitable setting of org-latex-classes not even the LCO feature
would be needed in ox-koma-letter. However I would leave it there for
more flexibility.
[...]
> Even when using a dedicated LCO files and or org-latex-classes it
> might be appropriate to overwrite variables.
Yes, I can imagine such cases. My problem with the current
implementation was, that for instance, the phone number was preset in
org-latex-classes. That urged me to customize this variable although
everything was already well defined in *my_name.lco*. So, please take
care to preset such variables with nil, where nil shall have the meaning
of 'ignore this variable'.
> In any case I don't have a strong opinion on this issue and your
> approach also makes sense.
Maybe we should write a user guide *before* further implementation steps.
> >> 2. Added AFTER_CLOSING and AFTER_LETTER keywords for arbitrary code
> >> after \closing{.} and \end{letter}, respectively.
> >> [...]
> >> b. Would it be better to have a dedicated, say, PS and ENCL rather
> >> than the generic AFTER_CLOSING?
> > I would opt for dedicated variables.
>
> Fine by be.. At the very least these should come in the order that
> they are specified in the document, I guess. E.g. I should be able to
> place ENCL before PS in the output, if I so desire.
Mmmh ... never thought about this aspect. I simply dictated the order
of CC, ENCL and PS in my implementation. Thus your current
AFTER_CLOSING is the best solution, if you want to provide full
flexibility.
> For arbitrary code I find AFTER_CLOSING and AFTER_LETTER nice.
> E.g. for pdfpages inclusions.
Agreed.
Best regards
--
Michael Strey
www.strey.biz
Re: [O] Shortcuts for setting or changing the warning period
Bastien altern.org> writes: > > IMHO it would also be helpful to have a shortcut > > to directly modify the warning > > period of an item with a timestamp in the agenda. > > (like it is possible with > > Shift+Left/Right Arrow to modify the date day by day). > > C-c C-d RET C-u C-u C-c C-d s- s- s- RET will do > it, so I don't think a specific syntax is needed here. Salut Bastien, thanks a lot for your help! I tried what you proposed, but that only removes the deadline for me: C-c C-d RET creates the deadline today. C-u C-u C-c C-d removes it and opens a capture window, as I have the corresponding option activated which prompts for a note when changing a deadline. Kind regards Martin
Re: [O] Exporter interface question
On 27.2.2013, at 09:52, Nicolas Goaziou wrote: > Hello, > > Carsten Dominik writes: > >> I much appreciate that `C-u C-c C-e' repeats the >> previous export action, that is extremely useful. >> >> I often only export a subtree of a document, and I >> was wondering if others would also find this proposal >> useful: >> >> When exporting a subtree, lets drop a mark at the >> headline and then go to this mark when C-c C-e is >> called with a prefix arguments. This would allow >> to keep the cursor somewhere deep in the subtree while >> working on it, and still be able to quickly repeat the >> export command. > > It would be nice indeed. > > Though, it may be useful to put some additional limitations to this > feature. For example, it would trigger only when on the same buffer as > before, perhaps even within the same subtree. Yes, this is possible. I'll look into it. - Carsten > > What do you think about it? > >> If others would find this useful, I'd make a patch. > > Be my guest. ;) > > > Regards, > > -- > Nicolas Goaziou
Re: [O] [patch] ox-koma-letter
Michael,
> I mean customized LCO files. For my former company I had made a
> letter class for business letters based on scrlttr2.cls with two LCO
> files. the first LCO file *company.lco* contained the general
> information about the company (address, bank account, etc.). A
> second LCO file *my_name.lco* contained the personal information of
> (e-mail address, name, phone extension). With *my_name.lco* calling
> *company.lco* the document class command for my letter finally was:
>
> \documentclass[my_name]{our_company_letter_class}
>
> With suitable setting of org-latex-classes not even the LCO feature
> would be needed in ox-koma-letter. However I would leave it there for
> more flexibility.
That's cool. Personally, I like this approach. But while lco files
are still readable they are not very nice. But not that terrible
either.
In fact to use the scrlttr2 support in Org I had to adjust a LCO files
because it's currently loaded after LATEX_HEADER arguments (so all
customization was overwritten). I didn't like that.
> Yes, I can imagine such cases. My problem with the current
> implementation was, that for instance, the phone number was preset in
> org-latex-classes. That urged me to customize this variable although
> everything was already well defined in *my_name.lco*. So, please take
> care to preset such variables with nil, where nil shall have the
> meaning
> of 'ignore this variable'.
I agree. This is anything but flexible, and I didn't even consider
it. I also noted that there's a lot of silly defaults. So probably
we should set everything to nil and do a "nil check" before inserting
stuff into the TeX file. This would also make for a clearer output
file, which is in itself something we should aim for.
> Maybe we should write a user guide *before* further implementation
> steps.
I agree. A "question zero" is whether we eventually want to have an
org-letter which could, in principle, output to something different
than scrlttr2.
Other things:
- Cleaning defaults
- Only insert KOMAVARs when non-nil.
- Which variables to include. E.g. Michael's list vs. every
komavar.
- consider the order of KOMAVARs, e.g. do we really want
LATEX_HEADER before LCO-like stuff? Do we want a KOMA_HEADER
(or LETTER_HEADER) which comes after LCO?
What to you think?
> Mmmh ... never thought about this aspect. I simply dictated the order
> of CC, ENCL and PS in my implementation. Thus your current
> AFTER_CLOSING is the best solution, if you want to provide full
> flexibility.
Or having the order of ENCL, PS, CC and "AFTER_CLOSING" in the TeX
file be governed by the order in the Org file. I guess this should be
feasible, although I currently do not know how to code. I think it's
desireable, though.
–Rasmus
--
When in doubt, do it!
Re: [O] Shortcuts for setting or changing the warning period
Salut Martin, Martin Beck writes: > thanks a lot for your help! > I tried what you proposed, > but that only removes the deadline for me: > C-c C-d RET creates the deadline today. > C-u C-u C-c C-d removes it and opens a capture window, > as I have the corresponding option activated which prompts > for a note when changing a deadline. I forgot to mention C-u C-u C-s C-d is only for the braves, those who live in the development (aka "master") branch of the repo. But you forgot to mention the version of Emacs, so we're even :) Best, -- Bastien
Re: [O] Exporter interface question
On Wed, Feb 27, 2013 at 01:00:30PM +0100, Carsten Dominik wrote: > > On 27.2.2013, at 09:52, Nicolas Goaziou wrote: > > > Carsten Dominik writes: > > > >> When exporting a subtree, lets drop a mark at the > >> headline and then go to this mark when C-c C-e is > >> called with a prefix arguments. This would allow > >> to keep the cursor somewhere deep in the subtree while > >> working on it, and still be able to quickly repeat the > >> export command. > > > > It would be nice indeed. > > > > Though, it may be useful to put some additional limitations to this > > feature. For example, it would trigger only when on the same buffer as > > before, perhaps even within the same subtree. > > Yes, this is possible. I'll look into it. I love the idea, including Nicolas' proposed restrictions. Until now I was defining keyboard macros for this. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] Bad indentation with visual-line-mode
Hi Torsten, Torsten Bronger writes: > - There is no way to set the line width besides setting Emacs > margins, which is visually less appealing than before. (Minor > problem.) Please report this to Emacs developers. > - Indentation in lists is essentially broken. I illustrate this by > indenting this list as it now appears in my org-mode file. One can > activate org-indent-mode but this is not the same as > longlines-mode. Besides, I don't like the big indentations it > creates for deeply nested content. `org-indent-mode' is fine for me here, it fixes the wrong _visual_ indentation which results from using `visual-line-mode'. > Besides, I don't like the big indentations it > creates for deeply nested content. Mhh.. what big indentations? (setq org-list-indent-offset 0) HTH, -- Bastien
Re: [O] [PATCH] ob-core: do not ask for confirmation if cached value is current
Achim Gratz writes: > Bastien altern.org> writes: > >> thanks for the patch. I applied it but renamed cache? and >> cache-current? to cache-p and cache-current-p. > > That patch needs amending. You let-bind cache-current, but then try to use > cache-current-p. Er... fixed, thanks for double-checking! -- Bastien
Re: [O] [org-contacts] need help for making gnus/message-mode integration optional
Simon Campese writes: > Hello, Hi Simon, > I have one quick feature request for org-contacts.el that should be > pretty easy and quick to implement: Could someone please introduce > customizable variables to optionally disable the gnus/message mode > integration? I've added a custom boolean, `org-contacts-enable-completion', that you can set to nil to disable the `message-mode' integration. Thanks for reporting this. > I don't know a lot of elisp, so instead of copy-pasting my way to a > half-baked solution that would maybe not be accepted upstream, I thought > that asking the experts here is more appropriate. > > My reason for this request: > For email address completion in message mode, I use a program that scans > through my whole email database (I use notmuch to manage emails and have > all my mails stored locally). This program is stored in > 'notmuch-address-command' and the integration has so far been done by > 'notmuch-address'. However, the recent version of org-contacts breaks > this behaviour, i.e. I only get the emails from my org-contacts file > when I try to complete recipients. As I don't want to add all the people > I correspond with electronically to my org-contacts file, this is a huge > annoyance. Could you try the attached patch and set the variable `org-contacts-complete-exclusive' to nil and see if it still happens. With this patch org-contacts should fail silently to complete and let other functions do the completion, so it should complete with both org-contacts and notmuch. Regards, From 9eef3177dc401b49a902fcbcbdf86dc1d63865d8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gr=C3=A9goire=20Jadi?= Date: Wed, 27 Feb 2013 13:31:12 +0100 Subject: [PATCH] org-contacts.el: Add a custom variable to let others functions complete in `message-mode' * contrib/lisp/org-contacts.el (org-contacts-complete-exclusive): a custom boolean variable to let others functions complete in `message-mode'. (org-contacts-complete-group, org-contacts-complete-name): Use `org-contacts-complete-exclusive'. --- contrib/lisp/org-contacts.el | 16 ++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index 8674533..8189da2 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -138,6 +138,12 @@ This overrides `org-email-link-description-format' if set." :group 'org-contacts :type 'boolean) +(defcustom org-contacts-complete-exclusive t + "Determine whether `org-contacts-message-complete-function' +should be the only function to complete or not." + :group 'org-contacts + :type 'boolean) + ;; Decalre external functions and variables (declare-function wl-summary-message-number "ext:wl-summary" ()) (declare-function wl-address-header-extract-address "ext:wl-address") @@ -421,7 +427,10 @@ A group FOO is composed of contacts with the tag FOO." ", "))) ;; We haven't found the correct group (completion-table-case-fold completion-list - (not org-contacts-completion-ignore-case + (not org-contacts-completion-ignore-case))) + :exclusive (if org-contacts-complete-exclusive + 'yes + 'no)) (defun org-contacts-complete-name (start end string) "Complete text at START with a user name and email." @@ -445,7 +454,10 @@ A group FOO is composed of contacts with the tag FOO." (org-contacts-make-collection-prefix (org-contacts-all-completions-prefix string - (remove-duplicates completion-list :test #'equalp))) + (remove-duplicates completion-list :test #'equalp))) + :exclusive (if org-contacts-complete-exclusive + 'yes + 'no) (defun org-contacts-message-complete-function (&optional start) "Function used in `completion-at-point-functions' in `message-mode'." -- 1.7.10.4 -- Daimrod/Greg pgpJPNCKaneHS.pgp Description: PGP signature
Re: [O] Add agenda entries into diary to export weelky calendar
Hi Sakurai san, I gave calfw a new try yesterday. It works well now and I really like it! I tried to do, as you suggested, a export via htmlfontify-buffer. It seems like it has problems with the cell alignment for those cells which contain an appointment. Please see the attached picture (I can send you the html file in a private mail if you are interested to see the html code). Could be the trouble of a non-monospace font, As far as I know Japanese fonts are monospace? The generic htmlfontify-buffer might be a bit to simple. E.g. as you can see in the image, I use a dark colour scheme in emacs. This is also used in the export, making it difficult to print. How about a real export function in calfw? Similar to what the calendar/diary offers. I could help to work on a LaTeX template using graphical elements e.g. by using TikZ [1]. There are SVG-based generators and solutions written in python as well. However, I have no idea how move the data of calfw into a template or into such a script. My elisp knowledge is almost non existing. All the best Torsten [1] http://www.texample.net/tikz/examples/feature/calendar-library/ On 26 February 2013 01:56, SAKURAI Masashi wrote: > Hi, > > > Alternatives: > > I read about calfw and org2hpda. However, I did not found a way to > generate a printable version of > > calfw (and I had trouble to set it up). For org2hpda I still struggle > with the installation and it > > seems to be broken at the moment. Not sure. > > I'm an author of calfw. I would help you about calfw. > > After displaying your calfw buffer, you can get a HTML buffer > with M-x htmlfontify-buffer. > > > Regards, > -- > SAKURAI, Masashi (family, given) > m.saku...@kiwanami.net > <>
Re: [O] Including linked emails during export (was Re: Integration of notmuch email references in notes in org-mode)
Hello,
Rainer M Krug writes:
> On 18/02/13 22:41, Suvayu Ali wrote:
>> Hi,
>>
>> On Mon, Feb 18, 2013 at 04:33:45PM +0100, Rainer M Krug wrote:
>>> On 18/02/13 16:12, Suvayu Ali wrote:
On Mon, Feb 18, 2013 at 02:49:32PM +0100, Rainer M Krug wrote:
>
> - From time to time, I have to include email references in notes in org.
> There is
> obviously org-notmuch.el, but I am not to happy with it as, when
> exporting the notes, the
> link is shown but neither clickable nor the resulting email is shown in
> the exported
> document (both understandable).
>
This has also been an irritation of mine. I think I will take your second
idea (include
the email on export) and see if I can come-up with a patch for
org-notmuch. Since I'm
still a newbie elisp programmer, this might take a while. :-p
>>>
>>> If there is a solution in sight, I am happy to wait a bit - email in
>>> export, possibly in a
>>> block so that it is set apart from the rest of the document, would be
>>> brilliant. Possibly
>>> having an option which can be set to have links exported as links or
>>> expanded on export,
>>> would be really nice.
>>
>> The option to open the link is out of the question since different people
>> read their emails
>> differently. There is no way for a library to get everything right,
>> specially since the link
>> won't be in Emacs. It is in the exported file (e.g. html, pdf, txt).
>
> If I understand the link system correctly, one would need to create a notmuch
> protocoll so that
> linux can react to clicking the link. But you are right, this is outside org.
>
>
>>
>> Now to include the email during the export at first I thought it should be
>> possible to write a
>> filter, but then I realised I need to insert an email quote block after
>> whatever parent
>> greater-element holds the link and then redirect the link to this new block.
>> A filter allows
>> you a way to modify an element, but nothing more. So I think the correct
>> approach here would
>> be to write a derived backend. This complicates things quite significantly
>> since now you need
>> to support each backend separately. I wonder if there is any easier
>> (generic) way to do the
>> above for all present and future backends.
>
> How is the export of links to pictures handled - as far as I remember, if the
> image is in a LaTeX
> suitable format, the image is included in the LaTeX file, and the same for
> html. But you are right
> - I guess this is handled in the backend. I don't think that would be a
> suitable approach as it
> would include to much maintenance.
>
> But what about defining notmuch as a new language for babel, so that one
> could do the following:
>
> #+begin_src notmuch :exports raw
> search id:x
> #+end_src
>
> Would not be much different then
>
> #+begin_src sh :exports raw
> notmuch search id:x
> #+end_src
>
> but possibly open more possibilities for customizations?
> x
> Or inline it could be src_notmuch{search id:x}
>
> The general advantage would be that one can use the existing infrastructure
> for code blocks and
>
> Cheers,
>
> Rainer
>
>>
>> I have CC'd Nicolas, lets see what he has to say.
FWIW, I think the approach suggested by Rainer is good, i.e. writing
a new "language" for Babel, with specific headers. Such blocks would
then be expanded into appropriate Org syntax the exporter can
understand.
Regards,
--
Nicolas Goaziou
Re: [O] [Bug] Export Coding System
Hello, Achim Gratz writes: > Achim Gratz writes: >> I've just had a chance to test this on the system where the problem >> originally >> showed up (Cygwin with the current 24.3 pre-release). On this system, the >> buffer-file-coding-system is not copied and the (wrong) default takes over >> again. I'm puzzled, I can't see how this happens... > > Also tested it with NT-Emacs on the same system and it also doesn't copy > all variables to the export buffer. I can't find anything wrong with > the macro, however, if I run the code there directly it works. Can you reproduce the problem in both synchronous and asynchronous export? Regards, -- Nicolas Goaziou
Re: [O] [patch] ox-koma-letter
Hi, Rasmus wrote: >> Maybe we should write a user guide *before* further implementation >> steps. > > I agree. A "question zero" is whether we eventually want to have an > org-letter which could, in principle, output to something different > than scrlttr2. That could be "isodoc" for which I have a bit of experience with. I'd enjoy to try and plug it in the current "org-letter" implementation. Best regards, Seb -- Sebastien Vauban
Re: [O] Including linked emails during export (was Re: Integration of notmuch email references in notes in org-mode)
Hey Nicolas,
On Wed, Feb 27, 2013 at 02:35:04PM +0100, Nicolas Goaziou wrote:
> Hello,
>
> Rainer M Krug writes:
> >
> > But what about defining notmuch as a new language for babel, so that
> > one could do the following:
> >
> > #+begin_src notmuch :exports raw
> > search id:x
> > #+end_src
> >
> > Would not be much different then
> >
> > #+begin_src sh :exports raw
> > notmuch search id:x
> > #+end_src
> >
> > but possibly open more possibilities for customizations?
> > x
> > Or inline it could be src_notmuch{search id:x}
> >
> > The general advantage would be that one can use the existing
> > infrastructure for code blocks and
>
> FWIW, I think the approach suggested by Rainer is good, i.e. writing
> a new "language" for Babel, with specific headers. Such blocks would
> then be expanded into appropriate Org syntax the exporter can
> understand.
Thanks for your feedback. I haven't had any time to look at this yet.
I'll keep this in mind.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
[O] org-caldav can't find org-prepare-agenda-buffers
As of today, org-cadav-syn fails with --8<---cut here---start->8--- org-export-icalendar: Symbol's function definition is void: org-prepare-agenda-buffers --8<---cut here---end--->8--- Actually, I can't find this function but org-agenda-prepare-buffers exist. Are there two different functions or is there a confusion somewhere ?
Re: [O] org-caldav can't find org-prepare-agenda-buffers
Hi Julien, Julien Cubizolles writes: > As of today, org-cadav-syn fails with > > org-export-icalendar: Symbol's function definition is void: > org-prepare-agenda-buffers > > Actually, I can't find this function but org-agenda-prepare-buffers > exist. Are there two different functions or is there a confusion > somewhere ? The function has been renamed a while ago. `org-agenda-prepare-buffers' is the correct name. -- Bastien
[O] [bug] Inline tasks are exported, even with noexport tag
Hello,
The following ECM fails on 2 fronts:
- the `noexport' tag on the inline task is not respected;
- the exported contents (because of the previous item) is not compilable in
LaTeX (maybe the default in `org-latex-inlinetask' is not generic enough for
handling such a content, or there are restrictions on the contents of inline
tasks which I did not respect?)
Best regards,
Seb
--8<---cut here---start->8---
#+TITLE: ECM Noexport not respected, and failure to export
#+AUTHOR:Seb Vauban
#+Time-stamp: <2013-02-27 Wed 15:07>
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:t ^:{}
* Private headline :noexport:
You don't see this. Good!
* Public headline
Normal body text...
*** This error report should be private :noexport:
When pushing Submit, I got the error:
#+begin_example
[ServletException in:/WEB-INF/sharedfiles/pdef/split/action_n235.jsp] No
getter method available for property submitinfo.xor_n249_n250 for bean under
name ViewCaseForm'
#+end_example
Maybe due to UTF-8 in the file =C:\WebClient\src\SubmitInfo.java=.
See as well
[[file:WebClient/src/tools/pdef/makefile][file:WebClient/src/tools/pdef/makefile]].
*** END
Follow-up to normal body text...
--8<---cut here---end--->8---
--
Sebastien Vauban
[O] bug: "org-export-preprocess-string: Wrong number of arguments" when doing "org-export-as-html"
Hi!
Org-mode 7.9.3f (692f053d8 Wed Feb 27 14:49:46 2013 +0100)
#+BEGIN_SRC elisp
(org-export-as-html 3 nil nil "htmlized-output" nil nil)
#+END_SRC
results in:
org-export-preprocess-string: Wrong number of arguments:
#[(&optional sort-only) ""
[org-inlinetask-min-level limit-level org-odd-levels-only nstars
org-outline-regexp count boundp 2 "\\*" format ...] 7
("/home/vk/.emacs.d/contrib/org-mode/lisp/org-footnote.elc" .
16171)], 2
A couple of weeks ago, it worked flawlessly with a single
difference: in between, the first optional parameter HIDDEN was
added. So I added "nil" as well.
Am I doing something wrong or is this a bug?
--
Karl Voit
Re: [O] Exporter interface question
On 27.2.2013, at 09:52, Nicolas Goaziou wrote: > Hello, > > Carsten Dominik writes: > >> I much appreciate that `C-u C-c C-e' repeats the >> previous export action, that is extremely useful. >> >> I often only export a subtree of a document, and I >> was wondering if others would also find this proposal >> useful: >> >> When exporting a subtree, lets drop a mark at the >> headline and then go to this mark when C-c C-e is >> called with a prefix arguments. This would allow >> to keep the cursor somewhere deep in the subtree while >> working on it, and still be able to quickly repeat the >> export command. > > It would be nice indeed. > > Though, it may be useful to put some additional limitations to this > feature. For example, it would trigger only when on the same buffer as > before, perhaps even within the same subtree. > > What do you think about it? > >> If others would find this useful, I'd make a patch. > > Be my guest. ;) OK, I see that this is a bit less trivial then I thought, requires that I study the ui interface a bit more. If you want to rush ahead and implement it let me know - otherwise this will be a few days before I find the time. - Carsten
Re: [O] Exporter interface question
Carsten Dominik writes: > OK, I see that this is a bit less trivial then I thought, requires > that I study the ui interface a bit more. I think the only pieces of the UI involved are `org-export-dispatch' function and `org-export-dispatch-last-action' variable. > If you want to rush ahead and implement it let me know - otherwise > this will be a few days before I find the time. There's no hurry. It can wait a few days. Thank you for looking into it. Regards, -- Nicolas Goaziou
Re: [O] Bad indentation with visual-line-mode
Hallöchen! Bastien writes: > Torsten Bronger writes: > >> - There is no way to set the line width besides setting Emacs >> margins, which is visually less appealing than before. (Minor >> problem.) > > Please report this to Emacs developers. In http://lists.gnu.org/archive/html/emacs-devel/2010-05/msg00824.html Stefan Monnier says that he sees no need to add a set-wrap-width option. >> - Indentation in lists is essentially broken. I illustrate this >> by indenting this list as it now appears in my org-mode file. >> One can activate org-indent-mode but this is not the same as >> longlines-mode. Besides, I don't like the big indentations it >> creates for deeply nested content. > > `org-indent-mode' is fine for me here, it fixes the wrong _visual_ > indentation which results from using `visual-line-mode'. Yes, it fixes it for me, too. But my point is that I don't want to have indentation of the subtrees, only of the list items. This basically means that org-indent-mode isn't the solution I am looking for. Besides, setting org-indent-indentation-per-level to "0" triggers this error on startup: Warning (initialization): An error occurred while loading `/home/bronger/.emacs': Args out of range: [nil * ** *** * ** *** * ** *** * ** *** * ** *** nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil], -1 Should I report a bug? And, shouldn't visual-line-mode's behaviour that it doesn't respect the indentation of org-mode be considerd a bug, too? Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com
[O] bug with timestamp fontification (bisected to b6b509b)
This is bisected to b6b509b (which 467f7ff claims to fix, and indeed does partially) Reproduce by doing: emacs -q -L /home/youngfrog/sources/org-mode/lisp/ -f org-mode --eval '(insert "<2012-02-27 Wed.>")' => timestamp is not fontified. or instead emacs -q -L /home/youngfrog/sources/org-mode/lisp/ -f org-mode --eval '(insert "Whatever\n<2012-02-27 Wed.>")' => timestamp is fontified but fontification is lost if you hit RET I tried to patch but didn't succeed. The newline (or beginning of buffer in first case, but that's probably unimportant ?) seems to be the problem. Any idea on that ? -- N.
Re: [O] bug with timestamp fontification (bisected to b6b509b)
On Wed, Feb 27, 2013 at 04:54:54PM +0100, Nicolas Richard wrote: > > Reproduce by doing: > emacs -q -L /home/youngfrog/sources/org-mode/lisp/ -f org-mode --eval > '(insert "<2012-02-27 Wed.>")' ^ Are you sure your timestamp has the correct syntax? As far as I know there should be no periods at the end of the day name. BTW, how do you enter timestamps? You can use C-c C-x . and C-c C-x ! for active and inactive timestamps. This way you can avoid sysntax errors conveniently. Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] org-mode not working properly after update
Hi, After another update of emacs today, org-mode is working fine now it seems. Thanks - *Sanjib Sikder * > > >
Re: [O] bug with timestamp fontification (bisected to b6b509b)
Hi Nicolas, "Nicolas Richard" writes: > This is bisected to b6b509b (which 467f7ff claims to fix, and indeed > does partially) I think I *completely* fixed this now... thanks for the heads up and the easy recipe! -- Bastien
Re: [O] bug with timestamp fontification (bisected to b6b509b)
Suvayu Ali writes: > On Wed, Feb 27, 2013 at 04:54:54PM +0100, Nicolas Richard wrote: >> emacs -q -L /home/youngfrog/sources/org-mode/lisp/ -f org-mode --eval >> '(insert "<2012-02-27 Wed.>")' > > Are you sure your timestamp has the correct syntax? As far as I know > there should be no periods at the end of the day name. Sometimes there is a period, sometimes not. When and when not : I never figured that out (never really tried to, either). > BTW, how do you enter timestamps? You can use C-c C-x . and C-c C-x ! That's what I use (usually). [except that there is no C-x] -- N.
Re: [O] [patch] ox-koma-letter
"Sebastien Vauban" writes: > Hi, > > Rasmus wrote: >>> Maybe we should write a user guide *before* further implementation >>> steps. >> >> I agree. A "question zero" is whether we eventually want to have an >> org-letter which could, in principle, output to something different >> than scrlttr2. > > That could be "isodoc" for which I have a bit of experience > with. I'd enjoy to try and plug it in the current "org-letter" > implementation. True. And it even produces beautiful documents, as far as I remember. There's even the standard LaTeX letter class. Say we define a variable ORG_LETTER_X. Then we'd need a table of corresponding values in export type Y. Probably this would be easiest to do in terms of the export function. –Rasmus -- Don't panic!!!
[O] org-agenda-write taking very long (probably because of babel)
Hi! Org-mode 7.9.3f (692f053d8 Wed Feb 27 14:49:46 2013 +0100) I am using these two lines to export an agenda to an iCal file: (org-agenda-list nil nil 60) (org-agenda-write "~/share/all/org-mode/org-export.ics") Since my Org-mode update from today (from 5d467d6f8affc0afe34922e885ac6e2492ddd091 Fri Feb 15 15:28:35 2013 +0100) it takes very long to export the ics file. I guess this relates to ... org-babel-exp processing... [25 times] ... which also pops up some babel result graphics which did not happen before. Was there a change in the default settings or is this a bug? Thanks! -- Karl Voit
Re: [O] bug with timestamp fontification (bisected to b6b509b)
Bastien writes: > I think I *completely* fixed this now... thanks for the heads up > and the easy recipe! Thanks ; indeed dropping the change to the regexp seems the easiest (and may avoid problems with code relying on that regexp out of the core). May I suggest that you fix the commit just once more ? Part of the previous fix was to increase "group number" everywhere, and that has to be reverted. Here is a patch if you prefer : >From 53152a802afe85e856d571867a2c8a36457cf0cd Mon Sep 17 00:00:00 2001 From: Nicolas Richard Date: Wed, 27 Feb 2013 17:55:42 +0100 Subject: [PATCH] Fix b6b509b one more time. --- lisp/org.el | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index b88b49a..7cf7832 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -5830,15 +5830,15 @@ by a #." (if (and (re-search-forward org-tsr-regexp-both limit t) (not (equal (char-before (match-beginning 0)) 91))) (progn - (org-remove-flyspell-overlays-in (match-beginning 1) (match-end 1)) - (add-text-properties (match-beginning 1) (match-end 1) + (org-remove-flyspell-overlays-in (match-beginning 0) (match-end 0)) + (add-text-properties (match-beginning 0) (match-end 0) (list 'mouse-face 'highlight 'keymap org-mouse-map)) - (org-rear-nonsticky-at (match-end 1)) + (org-rear-nonsticky-at (match-end 0)) (when org-display-custom-times - (if (match-end 4) - (org-display-custom-time (match-beginning 4) (match-end 4))) - (org-display-custom-time (match-beginning 2) (match-end 2))) + (if (match-end 3) + (org-display-custom-time (match-beginning 3) (match-end 3))) + (org-display-custom-time (match-beginning 1) (match-end 1))) t))) (defvar org-target-link-regexp nil -- 1.8.1.4
Re: [O] org-agenda-write taking very long (probably because of babel)
* Karl Voit wrote: > Hi! > > Org-mode 7.9.3f (692f053d8 Wed Feb 27 14:49:46 2013 +0100) > > I am using these two lines to export an agenda to an iCal file: > (org-agenda-list nil nil 60) > (org-agenda-write "~/share/all/org-mode/org-export.ics") > > Since my Org-mode update from today (from > 5d467d6f8affc0afe34922e885ac6e2492ddd091 Fri Feb 15 15:28:35 2013 > +0100) it takes very long to export the ics file. > > I guess this relates to ... > > org-babel-exp processing... [25 times] > > ... which also pops up some babel result graphics which did not > happen before. What I just found out: there were open buffers "2012-01-17-R" (an R session I used in an agenda file) and "*gnuplot*", both with running(!) sessions. > Was there a change in the default settings or is this a bug? > Thanks! -- Karl Voit
Re: [O] bug with timestamp fontification (bisected to b6b509b)
"Nicolas Richard" writes: > May I suggest that you fix the commit just once more ? Part of the > previous fix was to increase "group number" everywhere, and that has to > be reverted. Here is a patch if you prefer : Applied... thanks! *Sigh*... I think I need to get unplugged for a while :) -- Bastien
Re: [O] undo-tree and Org visibility
Samuel, Samuel Wales writes: > When I went back and forth with undo-tree, Org did not show the same > visibility that it did during each stage, so I added this defadvice. > What it does is make everything visible. My suggestion here is to use M-x show-all RET (or Org cycling) before playing around with `undo-tree-undo' or `undo-tree-visualize'. You will then have a clear view of what is un-done, without the need to worry about the visibility state. -- Bastien
Re: [O] org-agenda-write taking very long (probably because of babel)
Hi Karl, Karl Voit writes: > Was there a change in the default settings or is this a bug? Maybe this change: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=091bf02 Achim? -- Bastien
[O] [babel] Commenting out src blocks for tangling
Hello, I finally bit the bullet and converted by rather convoluted and long emacs startup code to an org file with emacs-lisp code blocks. I then tangle these into the actual code which is loaded by emacs at startup. So far, so good, and it does make it easier for me to navigate around my customisations. However, it has highlighted a feature which is missing (I think) but which would be great. I tangle all the code blocks to the same file. It would be great if I could have the =org-babel-tangle= command skip sections that are COMMENTed out (i.e. headline with COMMENT, as produced by =org-toggle-comment=). Alternatively, a :nobabel: or :notangle: tag to mark subtrees that should be excluded would be fine. If I have missed a way of doing this, please do let me know (politely ;-). If not, any suggestions on how to achieve this would be great. Thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3f-1285-g6cc600
Re: [O] undo-tree and Org visibility
Hi Bastien, On 2/27/13, Bastien wrote: > My suggestion here is to use M-x show-all RET (or Org cycling) > before playing around with `undo-tree-undo' or `undo-tree-visualize'. > > You will then have a clear view of what is un-done, > without the need to worry about the visibility state. Correct me if I'm wrong, but M-x show-all is equivalent to my defadvice (even worse because it shows more). Cycling will work initially, but that will change as soon as some changes in body text forces revealing that entry. Finally, this requires careful consideration of when to do undo and redo, and preparation beforehand, while I'd prefer those to be natural, quick operations that do not require setting visibility manually first. The "clear view" is only a clear view if you have all of the headlines showing. They will not show unless you have a very tall screen or very small fonts or a very small amount of body text. If you do not show the following headlines because the body text is too long, then you cannot easily tell that the operation was a move. Not saying anybody is interested, but I wanted to make the problem clear. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.
Re: [O] Exporter question
Aaron Ecay writes: > 2013ko otsailak 26an, Bastien-ek idatzi zuen: >> (Er.. org-toc.el should be trashed, it's 99% obsolete.) > > It is? I like its functionality and don’t know of any replacement... You could try speedbar instead which might give you most (some? definitely no column views in speedbar) of the functionality? Depends on what you used, of course. Speedbar understands org structure (headline based trees). There's always org-goto (C-c C-j, which I think means the command should have been org-jump but there you are...) as well. -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3f-1285-g6cc600
Re: [O] [babel] Commenting out src blocks for tangling
You should be able to set the “tangle” property of the headline to “no” to achieve this effect: see the following section of the manual: (org) Header arguments in Org mode properties It isn’t as easy to manipulate as a tag, perhaps. -- Aaron Ecay
Re: [O] [babel] Commenting out src blocks for tangling
Aaron Ecay writes: > You should be able to set the “tangle” property of the headline to “no” > to achieve this effect: see the following section of the manual: > (org) Header arguments in Org mode properties > > It isn’t as easy to manipulate as a tag, perhaps. Thanks. This does work and is relatively straightforward. However, it provides no visual indication of excluded sections from my customisation file which is rather unfortunate. That's why I would prefer to be able to COMMENT or tag excluded sub-trees. I guess I can use column view to see what is excluded... In any case, I can manage what I want for the moment. Thanks again, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3f-1285-g6cc600
Re: [O] Add agenda entries into diary to export weelky calendar
Torsten Wagner writes: [...] > I read about calfw and org2hpda. However, I did not found a way to generate > a printable version of calfw (and I had trouble to set it up). For org2hpda > I still struggle with the installation and it seems to be broken at the > moment. Not sure. You could print the calendar produced by calfw by C-u M-x ps-print-buffer-with-faces RET from the *cfw-calendar* buffer. This command (because of the C-u) will prompt for a file to place the postscript into. You can print without faces (i.e. no colour) with ps-print-buffer. You can then convert PS to PDF if so desired. You may wish to set ps-print-landscape to t. HTH, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3f-1285-g6cc600
Re: [O] [PATCH] ox-latex: provide width and height options for images
Rasmus writes: > For tikz figures resizing should be done via the scale argument to > preserve the right font sizes. If people want to resize a tikz figure > they should do so in their tikz code. No, that doesn't work for many tikz pictures; in particular it doesn't work for tikz files produced by gnuplot. There are reams of threads on stackoverflow on this topic… Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] logdone enhancement
Hi >> * project >> ** TODO headline :repeat: >>a longer description of what the todo item is about >>SCHEDULED: <2013-06-18 Tue +1m> > > The SCHEDULED line should be right after the headline, see the manual. > It can sometimes work when it is on another line, but this is > accidental, you should put the line right after the headline. I just tried * project ** TODO headline :repeat: SCHEDULED: <2013-06-18 Tue +1m> a longer description of what the todo item is about but this will still add the state-changed-line between the SCHEDULED line and the longer description (it will also add the property drawer there, if it doesn't exist). If you track some daily changes this can move the longer description away from the top quite fast, which is what I would like to avoid. Arun
Re: [O] seeing ??? in Ccaa rather than file name
Bastien writes: >> I see the same thing. Categories that would normally set to the file >> name are displayed as "???". Presumably because >> `org-refresh-category-properties' is called inside >> `with-silent-modifications', which let-binds `buffer-file-name'. > > Thanks for digging this further, I've fixed this now. Great, so much better! Thanks, Dave
Re: [O] org-agenda-write taking very long (probably because of babel)
Bastien writes: >> Was there a change in the default settings or is this a bug? > > Maybe this change: > http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=091bf02 I cannot see how. If the cache is current, the new code does _less_ work than it would have before the change. If the cache was stale to begin with, the files would have been re-made with the old code anyhow. Does this happen each time and if yes, what source blocks are involved? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Inserting a comma as prefix of headlines (in Org code blocks)
Hello, "Sebastien Vauban" writes: > Consider this Org block: > > #+begin_src org > * Headline inside an Org block > > Text of that entry. > #+end_src Technically, this is not an Org block for any serious function in Org. Headlines have precedence over block markers. > I don't remember exactly why (I think, sometimes, TAB'ing did not work > properly to prefix the dangerous lines with a `,'), I had to do it manually: > go and prefix every headline of the Org code block. > #+begin_src org > ,* Headline inside an Org block > > Text of that entry. > #+end_src > > That worked for long, but not anymore since a couple of weeks (could be > something like 2 months or so): currently, if you go in column 0 of the > headline, and insert `,', you get asked: > > "Priority A-C, SPC to remove: " > > IMHO, such a question should not be asked, and the `,' should be inserted > literally, as we're in the context of a code block. We're not, that's why comma escaping exists in the first place. I understand this may be counter-intuitive in your simple example, but it's quite logical. I think a proper solution would be to remove "," from speed keys and put priority command elsewhere. Thus, you can always insert "," manually at the beginning of the line. Meanwhile, there is "C-q ,".n What about "#" for priorities? Regards, -- Nicolas Goaziou
Re: [O] Inserting a comma as prefix of headlines (in Org code blocks)
Hi Nicolas, Nicolas Goaziou writes: > What about "#" for priorities? "#" is already taken, for comments. I think "," is good for priorities, and that preventing speed commands in the several blocks is safe and non-intrusive, that's what my patch did. Let me know if you (strongly) think otherwise! -- Bastien
Re: [O] logdone enhancement
Hi Sébastien, "Sebastien Vauban" writes: > But first, For me, the question comes down to: do we agree that John (in this > case) won't be allowed anymore to write such an entry? > > *** NOTE Assets:Receivable:CEG > #+begin_src sh :results value :exports results > ledger reg --inject=Expected '^income:ceg' > ledger reg --sort date -b 2007 receivable:CEG > #+end_src > :PROPERTIES: > :ID: 8BEF6C42-8B23-495B-9421-3810B58907A1 > :VISIBILITY: folded > :CREATED: [2010-06-18 Fri 07:37] > :END: No. The rule is about the SCHEDULED line, not about the :PROPERTIES: drawer. So John is allowed to write such an entry. `org-fixup-indentation' is just a way to _improve_ the indentation, so it should do its best in order to align SCHEDULED cookies (and friends) *and* drawers. If it can't align some drawers, it should just ignore them. And be happy with what it did. Thanks for testing, -- Bastien
[O] Org-Mode Reference Card "bug"
Just a remark to the Org-Mode Reference Card (http://orgmode.org/orgcard.pdf). There is a little bug in the spreadsheet description. wrong:sum from 2nd to 3rd hline |:=vsum(@II..@III)| correct:sum from 2nd to 3rd hline |:=vsum(@II..III)| The second at symbol must be deleted for correct working. Regards,-frank
[O] Tips for using orgmode + ledger to record events?
Hi all (posted to orgmode and ledger-cli list), I'm looking for ideas/tips on how to best record events using orgmode and ledger. By events I mean things like buying/paying a certain item (groceries, online payment, dining out), going to a certain place (haircut appointment, going to the gym), etc. Many of the events have its respective ledger journal because they involve buying/selling. But some other events do not involve money/ledger. I want to avoid duplication (recording both in .org file as well as ledger journal). How do you guys do it? Regards, Harum
Re: [O] Inserting a comma as prefix of headlines (in Org code blocks)
Hello,
Bastien writes:
> "#" is already taken, for comments.
Ok then another binding. I still think freeing "," key is the best thing
to do. More on this below.
> I think "," is good for priorities, and that preventing speed commands
> in the several blocks is safe and non-intrusive, that's what my patch
> did. Let me know if you (strongly) think otherwise!
Well, yes, I strongly think otherwise.
Your patch is relying on `org-in-block-p', which is completely broken in
this situation.
The fact is that any strictly positive number of "*" at column
0 followed by a space define a headline, whatever the context is. In
other words, headlines have precedence over every other construct in Org
syntax.
It's not about the parser. Every low level Org command (and most of the
high level too) assume, and have always assumed, this. For example, try
to cycle visibility in the following example (or move forward
heading...):
--8<---cut here---start->8---
* H1
** H11
#+begin_example
** H12
#+end_example
--8<---cut here---end--->8---
So, we have to make this point clear once and for all. Otherwise, we
should as well re-implement all functions working on headlines, because
if we accept that (org-in-block-p '("example")) returns a non-nil value
in the previous example, they become all wrong.
Therefore, "** H12" is a headline, and it is to be expected that speed
commands are triggered when point is on column 0. So my suggested
solution for the problem at hand is to simply avoid using "," in speed
keys, since "," is also used to protect headlines in blocks.
Let me stress this again:
1. "stars + space" at column 0 define a headline. No exception. Most
of Org code (reasonably) assumes this, so we should not let users
think otherwise.
2. Do not rely on `org-in-block-p'. Please use `org-element-at-point'
or `org-element-context' instead. These are not broken, and they
are fast enough for any interactive use (but let's not use them for
fontification yet).
Regards,
--
Nicolas Goaziou
Re: [O] [PATCH] Add a different prefix for past deadlines in the agenda view
Hi Sébastien, Bastien writes: >> Here's a patch to allow for a different prefix for deadline entries which are >> in the past: for example, "3 d ago" instead of "In -3 d"... > > Please make sure the change is backward compatible so that users don't > have to change the value of their `org-agenda-deadline-leaders' > (i.e. simply fall back on (nth 1 ...) when (nth 2 ...) returns nil. I finally added this, with a slightly different patch: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=c8c991e Thanks for the suggestion, -- Bastien
Re: [O] [bug] Inline tasks are exported, even with noexport tag
Hello, "Sebastien Vauban" writes: > The following ECM fails on 2 fronts: > > - the `noexport' tag on the inline task is not respected; Should it? Inlinetasks are not headlines, even though they use a somewhat similar syntax. :noexport: tag applies to trees. Inlinetasks do not define a tree. More generally, `org-export-with-tasks', `org-export-select-tags' and `org-export-exclude-tags' only apply on headlines. On the other hand, `org-export-with-inlinetasks' allows you to ignore inlinetasks completely during export. For conditional export, you may also want to look at drawers, which can be included/excluded by their name. > - the exported contents (because of the previous item) is not compilable in > LaTeX (maybe the default in `org-latex-inlinetask' is not generic enough for > handling such a content, or there are restrictions on the contents of inline > tasks which I did not respect?) >From the Org POV, you can put anything in an inlinetask excepted another inlinetask and a headline. `latex' backend puts contents within \fbox and a \minipage environments. It's possible that verbatim is not allowed within one of them, I didn't check. It's quite difficult to come up with something visually different and yet general enough. You can also use `org-latex-format-inlinetask-function'. Regards, -- Nicolas Goaziou
Re: [O] [HTML] subtree export reverted back to absolute H level behavior
Also true with region export.
Re: [O] [babel] Commenting out src blocks for tangling
Eric S Fraga writes: > Hello, > > I finally bit the bullet and converted by rather convoluted and long > emacs startup code to an org file with emacs-lisp code blocks. I then > tangle these into the actual code which is loaded by emacs at > startup. So far, so good, and it does make it easier for me to navigate > around my customisations. > > However, it has highlighted a feature which is missing (I think) but > which would be great. I tangle all the code blocks to the same > file. It would be great if I could have the =org-babel-tangle= command > skip sections that are COMMENTed out (i.e. headline with COMMENT, as > produced by =org-toggle-comment=). > > Alternatively, a :nobabel: or :notangle: tag to mark subtrees that > should be excluded would be fine. > > If I have missed a way of doing this, please do let me know (politely > ;-). If not, any suggestions on how to achieve this would be great. G'day Eric, If I understand your problem correctly, doesn't the property :tangle: do what you want? Cheers, Alan > > Thanks, > eric -- Alan L Tyree http://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
Re: [O] org-caldav can't find org-prepare-agenda-buffers
Bastien writes: > Hi Julien, > > Julien Cubizolles writes: > >> As of today, org-cadav-syn fails with >> >> org-export-icalendar: Symbol's function definition is void: >> org-prepare-agenda-buffers >> >> Actually, I can't find this function but org-agenda-prepare-buffers >> exist. Are there two different functions or is there a confusion >> somewhere ? > > The function has been renamed a while ago. > > `org-agenda-prepare-buffers' is the correct name. org-caldav does not call this function. It however requires org-icalendar, and that was renamed to ox-icalendar in org git. So I guess it pulls org-icalendar from the Org that is included with Emacs, which calls the obsoleted function. I don't follow org-development very closely. I realize there's a new exporter, but renaming the exporters in this way is asking for trouble. In this case, we've actually been lucky that an error like the above is thrown; much more subtle things can happen when new and old Org functions interact. -David
Re: [O] org-agenda-write taking very long (probably because of babel)
Achim Gratz writes: > I cannot see how. In fact I cannot even see how creating the agenda would run any src block at all… Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] Org-Mode Reference Card "bug"
Frank Mueller wrote: > Just a remark to the Org-Mode Reference Card (http://orgmode.org/orgcard.pdf). > > There is a little bug in the spreadsheet description. > > wrong: > sum from 2nd to 3rd hline |:=vsum(@II..@III)| > > correct: > sum from 2nd to 3rd hline |:=vsum(@II..III)| > > The second at symbol must be deleted for correct working. > Why do you think so? Nick
Re: [O] logdone enhancement
Arun Persaud wrote: > Hi > > >> * project > >> ** TODO headline:repeat: > >>a longer description of what the todo item is about > >>SCHEDULED: <2013-06-18 Tue +1m> > > > > The SCHEDULED line should be right after the headline, see the manual. > > It can sometimes work when it is on another line, but this is > > accidental, you should put the line right after the headline. > > I just tried > > * project > ** TODO headline :repeat: >SCHEDULED: <2013-06-18 Tue +1m> >a longer description of what the todo item is about > > but this will still add the state-changed-line between the SCHEDULED > line and the longer description (it will also add the property drawer > there, if it doesn't exist). If you track some daily changes this can > move the longer description away from the top quite fast, which is what > I would like to avoid. > Isn't that what the LOGBOOK drawer is for? You put the mess in there, so it's available when you open it, but you don't have to look at it most of the time. Nick
Re: [O] [babel] Commenting out src blocks for tangling
Alan L Tyree writes: [...] > G'day Eric, > > If I understand your problem correctly, doesn't the property :tangle: do > what you want? Yes, thanks; Aaron Ecay has also pointed out to me. It works and does exactly what I said I needed. And you have both been very polite :-) -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3f-1285-g6cc600
Re: [O] 5f095f5 is the first bad commit (for my use case)
2013ko otsailak 27an, Sebastien Vauban-ek idatzi zuen: > > Do you know if there was a way out -- other than killing Emacs -- in such a > case where `C-g' is not working? If you are on Linux (or OS X, I suppose), you can sometimes break an infloop by sending emacs the SIGUSR2 signal (in the shell, “kill -USR2 `pidof emacs`”). This also generates a backtrace in the lisp debugger, which is useful for debugging. See C-h v debug-on-event . -- Aaron Ecay
Re: [O] [HTML] subtree export reverted back to absolute H level behavior
Hello, Samuel Wales writes: > The old exporter had a bug where exporting a subtree would start H > levels at the level in the file. > > Thus, the top level being exported could be H8 if it were indented to > that level. Or H38 if it were indented to that level. > > IMO better behavior is relative. > > === > > The new exporter seemed to fix this, but it seems to have gone back to > the old behavior in a recent commit on git master. > > It is excellent to make the new emulate the old as much as possible; > this reduces bugs and impact on people. But does anybody rely on > absolute levels for subtree export? My guess would be no, but I could > be wrong. > > === > > Recent commit caused this change in output: > > -An intriguing and fun question > +An intriguing and fun question > > Hope I've not misunderstood something here. I can't run the > dispatcher directly because I get other issues. It would help to see your test file. For example, in the following Org buffer, * Level 1 ** Level 2 *** Level 3 Level 4 * Level 5 ** Level 6 exporting subtree with point on "Level 4" will result as Level 5 and Level 6, which is correct. I think your file is more like the following: * Something ** An intriguing and fun question ** An intriguing and fun question I.e. you skipped levels in your file. Then, numbering indeed skips parts. So to put it differently, level is relative to the lowest level among exported headline (it will always be 1), thereafter, it is absolute. Regards, -- Nicolas Goaziou
Re: [O] [HTML] region export exports footnotes title
Hello, Samuel Wales writes: > Footnotes > > Footnotes is not the correct title. I don't understand. Could you elaborate? > Also, I'd like to not have a title for subtree and region export, in > case it interferes with the title in the Blogger template. Do you mean that title shouldn't appear when exporting to body only? I don't mind changing it. But where to put it? In the preamble? I'm not sure it's a good location for it. You can also use a filter (`org-export-filter-final-output-functions') and remove the line matching "...". Regards, -- Nicolas Goaziou
Re: [O] new version of org-mew.el
Bastien writes: >> Some functions / variables from mew should be pre-declared > > Can you fix this? I don't have mew installed, so no I can't. >> or mew needs to be required. > > Mhh.. no, let's not require org-mew.el. Actually, looking at this, it wouldn't work before mew was loaded. > IMHO org-mew.el should not be distributed in core but in contrib, > as it is not useful for Emacs users that are not using Mew, and > those using Mew can install contrib/. Same for wanderlust. Yes, both libraries are not in Emacs. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] logdone enhancement
Hi > Isn't that what the LOGBOOK drawer is for? You put the mess in there, so > it's available when you open it, but you don't have to look at it most of > the time. nice! I didn't know about this one. This will solve my problem, although I still would prefer that drawers, etc are added at the very end of the entry and not before my additional description. But with LOGBOOK, I will only have them separated by 3 lines (scheduled, logbook and properties) which is not too bad. Thanks for the tip! Arun
Re: [O] 5f095f5 is the first bad commit (for my use case)
> Do you know if there was a way out -- other than killing Emacs -- in such a > case where `C-g' is not working? None that I can think of. Regards, -- Nicolas Goaziou
Re: [O] [HTML] subtree export reverted back to absolute H level behavior
On 2/27/13, Nicolas Goaziou wrote: > It would help to see your test file. For example, in the following Org > buffer, > > * Level 1 > ** Level 2 > *** Level 3 > Level 4 > * Level 5 > ** Level 6 Did you try it with org-odd-levels-only set to t? That's a standard part of Org. > I think your file is more like the following: > > * Something > ** An intriguing and fun question > ** An intriguing and fun question Not that I am aware of. === Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.
Re: [O] edit-src on read-only files
Hi Bastien, Bastien writes: > Hi Andreas, > > Andreas Leha writes: > >> On a related note: I'd also love to see the changes in the >> source code buffers be autosaved in the org file. I've lost some big >> edits already due to power loss on my (old) laptop. > > There is now `org-edit-src-auto-save-idle-delay' which you can > set to >0 so that the edit src buffer will be saved after N secs > of idle time. > > Thanks for suggesting this, thanks for taking this up! But I am not sure, whether I like the current implementation too much. Instead of saving the org-file itself, I'd prefer the org-file to be auto-saved. More importantly, the current implementation prevents me from discarding the edit with the new C-c C-k (org-edit-src-abort). I am not sure how to overcome those limitations (especially the second one), though. So I fear, I won't be able to provide a patch implementing my preferred behaviour. Regards, Andreas
Re: [O] [HTML] region export exports footnotes title
On 2/27/13, Nicolas Goaziou wrote: > Samuel Wales writes: > >> Footnotes >> >> Footnotes is not the correct title. > > I don't understand. Could you elaborate? It literally exported that as the title. The document source did not have that headline anywhere. It might or might not be related to the inline footnote fix. >> Also, I'd like to not have a title for subtree and region export, in >> case it interferes with the title in the Blogger template. > > Do you mean that title shouldn't appear when exporting to body only? Yes. > I don't mind changing it. But where to put it? In the preamble? I'm not > sure it's a good location for it. The title shouldn't appear anywhere, because the object is to export HTML for Blogger. It did not appear in the old exporter. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.
Re: [O] [HTML] subtree export reverted back to absolute H level behavior
Samuel Wales writes: > On 2/27/13, Nicolas Goaziou wrote: >> It would help to see your test file. For example, in the following Org >> buffer, >> >> * Level 1 >> ** Level 2 >> *** Level 3 >> Level 4 >> * Level 5 >> ** Level 6 > > Did you try it with org-odd-levels-only set to t? That's a standard > part of Org. The equivalent file with `org-odd-levels-only' set to t also gives correct results. >> I think your file is more like the following: >> >> * Something >> ** An intriguing and fun question >> ** An intriguing and fun question > > Not that I am aware of. Then my next guess is: Colonel Mustard with the chandler in the kitchen. Did I win? Or you can provide a file demonstrating the problem... Regards, -- Nicolas Goaziou
