[O] Org interpreting multiple ^{*} instances as bold in LaTeX beamer export
Here's a minimal example:
#+begin_src org
#+startup: beamer
#+latex_class: beamer
#+options: tex:t
* A headline
a word^{*} followed by another^{*}
- bullet item^{*}
- bullet item^{*}
- bullet item
- bullet item
#+end_src
I just wanted an asterisk to put a little footnote for two items in a
longer list and noticed that it shifted the whole slide up. Same for
regular LaTeX document export. Seems like it only happens if the two
bullets are consecutive. In other words, this works fine:
#+begin_src org
a word^{*} followed by another and let's see how far apart they need
to be before this
isn't triggered anymore by org interpreting LaTeX math as bold markup
and inserting
textbf commands in the export^{*}. Ah, yes. That does it.
- bullet item^{*}
- bullet item
- bullet item^{*}
#+end_src
I also tried explicitly forcing math mode, but with varied success:
#+begin_src org
appears to work:
a word\(^{*}\) followed by another\(^{*}\)
still doesn't work (asterisks are there, but org doesn't put it in as
an =\item=, taking the - bullet markup literally
- bullet item\(^{*}\)
- bullet item\(^{*}\)
- bullet item
- bullet item
#+end_src
This is on the old exporter (not sure if org has actually moved to
this or not yet... but either way, I've still just been doing things
the old way as I haven't really dug into the new one yet).
Best regards,
John
[O] [BUG] (error Lisp nesting exceeds `max-lisp-eval-depth')
Hello, Since the last pull I made, I can't expand anymore BBDB aliases in Gnus... because of Org! --8---cut here---start-8--- Debugger entered--Lisp error: (error Lisp nesting exceeds `max-lisp-eval-depth') yas--all-parents(text-mode) (lambda (mode) (yas--all-parents mode))(text-mode) mapcar((lambda (mode) (yas--all-parents mode)) (text-mode message-mode)) cl-mapcar((lambda (mode) (yas--all-parents mode)) (text-mode message-mode)) apply(cl-mapcar (lambda (mode) (yas--all-parents mode)) (text-mode message-mode) nil) mapcan((lambda (mode) (yas--all-parents mode)) (text-mode message-mode)) (append modes-to-activate (mapcan (function (lambda (mode) (yas--all-parents mode))) modes-to-activate)) (remove-duplicates (append modes-to-activate (mapcan (function (lambda (mode) (yas--all-parents mode))) modes-to-activate))) (let ((modes-to-activate (list major-mode)) (mode major-mode)) (while (setq mode (get mode (quote derived-mode-parent))) (setq modes-to-activate (cons mode modes-to-activate))) (progn (let ((--dolist-tail-- (yas-extra-modes)) mode) (while --dolist-tail-- (setq mode (car --dolist-tail--)) (setq modes-to-activate (cons mode modes-to-activate)) (setq --dolist-tail-- (cdr --dolist-tail--) (remove-duplicates (append modes-to-activate (mapcan (function (lambda (mode) (yas--all-parents mode))) modes-to-activate yas--modes-to-activate() (mapcar (function (lambda (mode-name) (gethash mode-name yas--tables))) (yas--modes-to-activate)) (remove nil (mapcar (function (lambda (mode-name) (gethash mode-name yas--tables))) (yas--modes-to-activate))) yas--get-snippet-tables() (mapcan (function (lambda (table) (yas--fetch table (buffer-substring-no-properties start end (yas--get-snippet-tables)) (setq templates (mapcan (function (lambda (table) (yas--fetch table (buffer-substring-no-properties start end (yas--get-snippet-tables))) (while (and (not done) syntaxes) (setq syntax (car syntaxes)) (setq syntaxes (cdr syntaxes)) (save-excursion (skip-syntax-backward syntax) (setq start (point))) (setq templates (mapcan (function (lambda (table) (yas--fetch table (buffer-substring-no-properties start end (yas--get-snippet-tables))) (if templates (setq done t) (setq start end))) (let ((start (point)) (end (point)) (syntaxes yas-key-syntaxes) syntax done templates) (while (and (not done) syntaxes) (setq syntax (car syntaxes)) (setq syntaxes (cdr syntaxes)) (save-excursion (skip-syntax-backward syntax) (setq start (point))) (setq templates (mapcan (function (lambda (table) (yas--fetch table (buffer-substring-no-properties start end (yas--get-snippet-tables))) (if templates (setq done t) (setq start end))) (list templates start end)) yas--current-key() (if field (save-restriction (narrow-to-region (yas--field-start field) (yas--field-end field)) (yas--current-key)) (yas--current-key)) (setq templates-and-pos (if field (save-restriction (narrow-to-region (yas--field-start field) (yas--field-end field)) (yas--current-key)) (yas--current-key))) (if (and yas-expand-only-for-last-commands (not (member last-command yas-expand-only-for-last-commands))) nil (setq templates-and-pos (if field (save-restriction (narrow-to-region (yas--field-start field) (yas--field-end field)) (yas--current-key)) (yas--current-key (let (templates-and-pos) (if (and yas-expand-only-for-last-commands (not (member last-command yas-expand-only-for-last-commands))) nil (setq templates-and-pos (if field (save-restriction (narrow-to-region (yas--field-start field) (yas--field-end field)) (yas--current-key)) (yas--current-key (if (and templates-and-pos (first templates-and-pos)) (yas--expand-or-prompt-for-template (first templates-and-pos) (second templates-and-pos) (car (cdr (cdr templates-and-pos (yas--fallback (quote trigger-key yas-expand() call-interactively(yas-expand) (if (keymapp binding) (set-temporary-overlay-map binding) (call-interactively (or binding (quote orgstruct-error (let ((binding (let ((orgstruct-mode)) (key-binding (if (keymapp binding) (set-temporary-overlay-map binding) (call-interactively (or binding (quote orgstruct-error) (if (let* ((org-heading-regexp (concat ^ orgstruct-heading-prefix-regexp \\(\\*+\\)\\(?: +\\(.*?\\)\\)?[ ]*$)) (org-outline-regexp (concat orgstruct-heading-prefix-regexp \\*+ )) (org-outline-regexp-bol (concat ^ org-outline-regexp)) (outline-regexp org-outline-regexp) (outline-heading-end-regexp \n) (outline-level (quote outline-level)) (outline-heading-alist)) (when (org-context-p (quote headline) (quote item) nil) (org-run-like-in-org-mode (quote org-cycle)) t)) nil (let ((binding (let ((orgstruct-mode)) (key-binding (if (keymapp binding) (set-temporary-overlay-map binding) (call-interactively (or binding (quote orgstruct-error)) (unless (let* ((org-heading-regexp (concat ^ orgstruct-heading-prefix-regexp
[O] org 8.0 and new exporter ETA?
Dear org-people, First of all, my thanks to everyone who contributes to this project! My (digital) life orbits around org-mode now. I am very happy with my current emacs/org-mode set up, but (being a permanent tinkerer) I am planning to do some relatively important changes, in particular in relationship with exporting to LaTex. I would like to do this after org 8.0 is out with the new exporter. Do we have a rough idea of when it will be officially out? It is a matter of weeks, or months? Many thanks for the answer, Julian -- Julian Mariano Burgos, PhD Hafrannsóknastofnunin/Marine Research Institute Skúlagata 4, 121 Reykjavík, Iceland Sími/Telephone : +354-5752037 Bréfsími/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is
[O] time stamps in table of contents
Hi,
this is a question for CSS experts.
I am trying to get rid of time stamps in HTML export. So I am using a CSS file
which contains among other things:
#table-of-contents {
font-size: 100%;
position: fixed;
display: block;
left: 10px;
top: 164px;
width: 300px;
bottom: 2px;
line-height: 1.0em;
overflow: auto;
border-style:none;
}
#table-of-contents timestamp {
display:none;
}
One of the lines in the table of contents looks like this:
lia href=#sec-2-1span class=timestamp-wrapperspan
class=timestamplt;2013-01-11 Frgt;/span/span Carsten: Wiskunde als de
taal van de Natuur/a/li
So I had been hoping this would get rid of the timestamp in the table of
context. It does not. Does anyone know why?
Cheers!
- Carsten
Re: [O] time stamps in table of contents
Hello Carsten,
Carsten Dominik wrote:
this is a question for CSS experts.
I am trying to get rid of time stamps in HTML export. So I am using a CSS
file which contains among other things:
#table-of-contents {
font-size: 100%;
position: fixed;
display: block;
left: 10px;
top: 164px;
width: 300px;
bottom: 2px;
line-height: 1.0em;
overflow: auto;
border-style:none;
}
#table-of-contents timestamp {
display:none;
}
One of the lines in the table of contents looks like this:
lia href=#sec-2-1span class=timestamp-wrapperspan
class=timestamplt;2013-01-11 Frgt;/span/span Carsten: Wiskunde als
de taal van de Natuur/a/li
So I had been hoping this would get rid of the timestamp in the table of
context. It does not. Does anyone know why?
You don't use the `' selector for direct child, so that shouldn't be the
problem (the fact that timestamp is not a direct child, but a grandchild).
Don't you forget the `.' in front of timestamp, for the class spec?
Best regards,
Seb
--
Sebastien Vauban
Re: [O] Macro expansion in new exporter
Hello again,
Like many others, I'm adapting my workflow to the new exporter. Like
Carsten (but apparently few others), I've been using macros extensively.
Though I've spent several days digging through the mailing list and
code, I still don't have the answers I need, but hopefully I can ask
intelligent questions.
Nicolas Goaziou n.goaz...@gmail.com writes:
On that topic, the main difference with the previous exporter is that
macros are now required to be in a context that can be parsed. Thus, for
example, the following is not a macro:
~{{{title}}}~
What is meant by a context that can be parsed?
In my work, it has been very useful to use macros for snippets of
text. Then, instead of changing the text everywhere when I want a
change, I would just change the macro. So...
For instance, I used to be able to do this:
#+MACRO: status Draft
#+HTML: p class=status{{{status}}}/p
And on export to HTML, I would get what you would expect:
p class=statusDraft/p
With the new exporter, the macro is left unexpanded in the output:
p class=status{{{status}}}/p
Of course, I could also put the {{{status}}} in any ordinary text and
have it there as well.
In extensive experiments, I have not found any combination of input that
would produce the old output using macros.
The old behavior had an elegant, one-line solution. Perhaps the
functionality could be duplicated with babel, but surely not as simply
and directly as with the old macro system.
Is there a way to replicate the old behavior in the new export engine?
Also, in your response to Carsten's question about macros, you suggested
this:
#+MACRO: thumbright @@html:img src=./Content/$2/thumb.jpg
style=float:right;width:$1;margin:0px 20px 0px 20px;
alt=./Content/$2/thumb.jpg /@@
The @@ syntax looks new to me. Can you tell me what the function of
the @@ is? Is this documented somewhere?
Best regards,
Terry
--
T.F. Torrey
[O] BIND org-html-style-include-*
Hello, In my files, this used to work to suppress the default styles and javascript: #+BIND: org-export-html-style-include-default nil #+BIND: org-export-html-style-include-scripts nil Now, I have these: #+BIND: org-html-style-include-default nil #+BIND: org-html-style-include-scripts nil But they seem to be silently ignored, though if I setq the values ahead of time, the output is suppressed. Can these still be set using BIND? If so, what am I doing wrong? Also, the value of org-html-mathjax-template seems to be output now by default, and I don't remember seeing it before. Is this an intended change? If so, how can it be suppressed? (If not ... ???) Emacs: GNU Emacs 24.3.50.1 (i686-pc-linux-gnu, GTK+ Version 3.6.0) of 2012-12-24 on menkib, modified by Debian Package: Org-mode version 7.9.3e (7.9.3e-970-g728c0e @ /home/tftorrey/.emacs.d/elisp/org/lisp/) Best regards, Terry -- T.F. Torrey
Re: [O] org 8.0 and new exporter ETA?
Dear Julian, Julian Burgos jul...@hafro.is writes: First of all, my thanks to everyone who contributes to this project! My (digital) life orbits around org-mode now. :) I am very happy with my current emacs/org-mode set up, but (being a permanent tinkerer) I am planning to do some relatively important changes, in particular in relationship with exporting to LaTex. I would like to do this after org 8.0 is out with the new exporter. Do we have a rough idea of when it will be officially out? It is a matter of weeks, or months? Many thanks for the answer, If we get enough testing against current HEAD of the master branch in our git repository, I'd say it's a matter of weeks. In any case, I don't want to delay the release beyond end of March, as I won't have enough time to dedicate to Org past this date. HTH, -- Bastien
Re: [O] Still Wishing for Snooze
Hi Michael, Michael Brand michael.ch.br...@gmail.com writes: SCHEDULED: 2013-02-07 jeu. -2d The item will not be shown today, but in three days. For this case I would use: SCHEDULED: 2013-02-09 Sat AFAIU this would not work for what Andrew wants. He wants the scheduled item to be invisible on the 2013-02-07 but to appear on the 2013-02-07 as it is was scheduled on 2013-02-09. My change does this. It seems I don’t get the point because when a TODO with repeater SCHEDULED: 2013-02-01 Fri +1w -3d is set to DONE the delay remains and this way also here I would not use a delay but: SCHEDULED: 2013-02-04 Mon +1w The usefulness of a SCHEDULED delay I see together with a TODO and repeater to implement an _exception_ (to simplify: exception just for the first date, before the repetitions). For example SCHEDULED: 2013-02-01 Fri +1w -3d would mean: Usually start working on the entry earliest on the first day of the month except [2013-02-01 Fri] when work can not start before [2013-02-04 Mon]. It would start to show in the agenda on [2013-02-04 Mon], [2013-03-01 Fri], [2013-04-01 Mon], [2013-05-01 Wed], [2013-06-01 Sat] etc. On let’s say [2013-02-05 Tue] it would be set to DONE and would change to: SCHEDULED: 2013-03-01 Fri +1w Note the automatically removed delay. Point well taken -- this is now what adding --2d does: use a temporary delay that will not be taken into account for dates later than the next repeater, and that will be deleted when a repeating task is marked as done. Thanks for suggesting this. I think it still makes sense to keep the default behavior: -1d in a scheduled items means inconditionnally add a delay of one day, even when there is a repeater -- because perhaps what users want is a global delay for the repeated task. If that's not the case, --2d is just fine too. Thanks for your feedback on this! -- Bastien
Re: [O] Bug: org-insert-heading-respect-content inserts at the wrong level if target heading is invisible [7.9.2 (release_7.9.2-883-g6fb36e.dirty @ /home/dlm/share/org-mode.git/lisp/)]
Hi James, James Harkins jamshar...@gmail.com writes: One concern: When you tested with C-u C-RET, was the point on a hidden headline? Yes. The problem only occurs if the current heading is folded up underneath a parent heading. AFAIK cursor movement in org-mode ensures that the point is never on invisible text, which is why I wrote a short lisp function to demonstrate. It seems to me the issue reproduces only when calling org-insert-heading non-interactively, then, so I wanted to check if your test reproduces the problem without the patch. Looking forward reading your feedback on this! -- Bastien
Re: [O] time stamps in table of contents
Carsten Dominik carsten.dominik at gmail.com writes:
#table-of-contents timestamp {
display:none;
}
You want a class selector (.) there, not an ID selector (#). Also you
should probably mark this !important so it doesn't get overriden later.
Regards,
Achim.
[O] Bug: [MINOR BUG] Agenda files are always loaded in showeverything mode [7.9.3e (7.9.3e-956-g3943be.dirty @ /home/vdyadov/Work/Tools/emacs/org-mode/lisp/)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. Hi! There is a minor issue with last org-mode from git repo. Agenda files are loaded in showeverything mode (including expanded drawers and so on),regardless value of org-startup-folded (which is set to 'content ) and #+STARTUP: file field. BTW: find-file-noselect which is used to load agenda files list, after loading emacs and org-mode works fine with org-files. Emacs : GNU Emacs 24.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.18.9) of 2012-12-25 on canopus-pc.elvees.com Package: Org-mode version 7.9.3e (7.9.3e-956-g3943be.dirty @ /home/vdyadov/Work/Tools/emacs/org-mode/lisp/)
Re: [O] time stamps in table of contents
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
Don't you forget the `.' in front of timestamp, for the class
spec?
Yes
#table-of-contents .timestamp {
display:none;
}
works correctly.
--
Bastien
Re: [O] Bug: [MINOR BUG] Agenda files are always loaded in showeverything mode [7.9.3e (7.9.3e-956-g3943be.dirty @ /home/vdyadov/Work/Tools/emacs/org-mode/lisp/)]
Hi Дядов Васил (do I get your name right?) vdya...@canopus-pc.elvees.com (Дядов Васил Стоянов) writes: There is a minor issue with last org-mode from git repo. Agenda files are loaded in showeverything mode (including expanded drawers and so on),regardless value of org-startup-folded (which is set to 'content ) and #+STARTUP: file field. This is intentional as it speeds up the agenda generation a lot for people who have many agenda files. Use (setq org-agenda-inhibit-startup nil) to avoid this. Thanks, -- Bastien
[O] double-width characters in tables
This problem has been flagged up before: http://orgmode.org/worg/org-issues.html#mid-87pqt04qg1-2Efsf-40gmail-2Ecom It's causing me headaches at the moment, so I'm trying to see if I can find a solution. The proximate cause of issues with double-width characters in table fields (they also mess with justification) is that the contents of the fields are propertized with a length based on `length', and not `string-width'. So you get this: #(《蛙》 0 3 (fontified t line-prefix #( 0 4 (face org-indent)) wrap-prefix #( 0 4 (face org-indent)) face org-table)) 3 is the number of characters in the string, but it takes up 6 columns of screen width. That messes up justification. I can't for the life of me figure out where that number is getting added to the string! I tried changing `length' to `string-width' in all manner of org functions, such as `org-add-props', but could never get that number changed during the fontification of the org tables. I wouldn't be surprised if this is something outside of org, or if fixing it would lead to more troubles, but does anyone have any ideas about this? Fixable, or not? Thanks! Eric
Re: [O] org 8.0 and new exporter ETA?
Thanks Bastien. Keep up the good work! On 02/12/2013 10:30 AM, Bastien wrote: Dear Julian, Julian Burgos jul...@hafro.is writes: First of all, my thanks to everyone who contributes to this project! My (digital) life orbits around org-mode now. :) I am very happy with my current emacs/org-mode set up, but (being a permanent tinkerer) I am planning to do some relatively important changes, in particular in relationship with exporting to LaTex. I would like to do this after org 8.0 is out with the new exporter. Do we have a rough idea of when it will be officially out? It is a matter of weeks, or months? Many thanks for the answer, If we get enough testing against current HEAD of the master branch in our git repository, I'd say it's a matter of weeks. In any case, I don't want to delay the release beyond end of March, as I won't have enough time to dedicate to Org past this date. HTH, -- Julian Mariano Burgos, PhD Hafrannsóknastofnunin/Marine Research Institute Skúlagata 4, 121 Reykjavík, Iceland Sími/Telephone : +354-5752037 Bréfsími/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is
Re: [O] double-width characters in tables
File a bug report - M-x report-emacs-bug RET - against Orgmode. I am sure something useful will come out of it, eventually. It is good to get eyes and mouths of emacs-devel-ers involved, for whatever it is worth. Believe me it is good, for the discussion and suggestions it will open up. Eric Abrahamsen e...@ericabrahamsen.net writes: This problem has been flagged up before: http://orgmode.org/worg/org-issues.html#mid-87pqt04qg1-2Efsf-40gmail-2Ecom It's causing me headaches at the moment, so I'm trying to see if I can find a solution. The proximate cause of issues with double-width characters in table fields (they also mess with justification) is that the contents of the fields are propertized with a length based on `length', and not `string-width'. So you get this: #(《蛙》 0 3 (fontified t line-prefix #( 0 4 (face org-indent)) wrap-prefix #( 0 4 (face org-indent)) face org-table)) 3 is the number of characters in the string, but it takes up 6 columns of screen width. That messes up justification. I can't for the life of me figure out where that number is getting added to the string! I tried changing `length' to `string-width' in all manner of org functions, such as `org-add-props', but could never get that number changed during the fontification of the org tables. I wouldn't be surprised if this is something outside of org, or if fixing it would lead to more troubles, but does anyone have any ideas about this? Fixable, or not? Thanks! Eric --
Re: [O] double-width characters in tables
Hi Eric, Eric Abrahamsen e...@ericabrahamsen.net writes: This problem has been flagged up before: http://orgmode.org/worg/org-issues.html#mid-87pqt04qg1-2Efsf-40gmail-2Ecom It's causing me headaches at the moment, so I'm trying to see if I can find a solution. The problem for me here is that even if (string-width 《蛙》) returns 6, it is not visually equivalent to 6 characters. Is it for you? If not, let's report this to Emacs... PS: Btw (org-string-width 《蛙》) returns the correct value. -- Bastien
Re: [O] double-width characters in tables
Jambunathan K kjambunat...@gmail.com writes: File a bug report - M-x report-emacs-bug RET - against Orgmode. If users believe this is a bug in Org-mode, they should send the bug report to the Orgmode list. If they believe this is a bug in Emacs, they should discuss it to emacs-devel. Please help me in letting people know about this policy. -- Bastien
Re: [O] time stamps in table of contents
On 12 feb. 2013, at 11:35, Achim Gratz strom...@nexgo.de wrote:
Carsten Dominik carsten.dominik at gmail.com writes:
#table-of-contents timestamp {
display:none;
}
You want a class selector (.) there, not an ID selector (#). Also you
should probably mark this !important so it doesn't get overriden later.
I am dumber than you think, how exactly would I do this? Add an exclamation
mark? Where?
Thanks
- Carsten
Re: [O] time stamps in table of contents
Carsten Dominik carsten.domi...@gmail.com writes:
I am dumber than you think, how exactly would I do this? Add an
exclamation mark? Where?
This should do:
#table-of-contents .timestamp {
display:none !important;
}
--
Bastien
Re: [O] time stamps in table of contents
OK, thank you!
- Carsten
On 12 feb. 2013, at 12:41, Bastien b...@altern.org wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
I am dumber than you think, how exactly would I do this? Add an
exclamation mark? Where?
This should do:
#table-of-contents .timestamp {
display:none !important;
}
--
Bastien
--
Do unto others as you'd have them do unto you. But first ask them if it is
alright -- Julia Sweeney
[O] Critic markup
Hello, I just read about this nice extension to markdown syntax this morning: http://macdrifter.com/2013/02/everyones-a-critic-the-critic-markup-language-proposal.html I really like how it's minimal yet seems to fairly well address a problem in collaborative text editing. Is there something similar in orgmode? Thanks, Alan
[O] [new exporter] workaround/replacement for org-export-as-html-batch
Dear all,
I rely on
emacs --batch \
--eval (add-to-list 'load-path \${HOME}/GIT/org-mode/lisp/\)\
--load ${HOME}/GIT/org-mode/lisp/org.el \
--visit file.org \
--funcall org-export-as-html-batch
somewhere in my HTML generating workflow.
I see org-export-as-html-batch in the FIXME section in the source.
Is there any easy workaround for the moment? Or a guess when it will leave that
section?
Naively loading the old stuff by adding a
---eval (add-to-list 'load-path
\${HOME}/GIT/org-mode/contrib/oldexp/\)\
line to the call above did not work either.
I then get:
---
Exporting...
Symbol's value as variable is void: org-export-with-sub-superscripts
---
What worked was de-automating that step and export manually, so it's not an
emergency.
Obviously my google-fu wasn't up to the task, too.
All that with orgmode from today.
Thanks for any help
Detlef
Re: [O] Still Wishing for Snooze
Hi Bastien On Tue, Feb 12, 2013 at 11:21 AM, Bastien b...@altern.org wrote: Point well taken -- this is now what adding --2d does: use a temporary delay that will not be taken into account for dates later than the next repeater, and that will be deleted when a repeating task is marked as done. Thanks for suggesting this. This * TODO 1a SCHEDULED: 2013-01-10 Thu +1m --2d * TODO 2a SCHEDULED: 2013-02-10 Sun +1m --2d * TODO 1b SCHEDULED: 2013-01-11 Fri +1m --2d * TODO 2b SCHEDULED: 2013-02-11 Mon +1m --2d * TODO 1c SCHEDULED: 2013-01-12 Sat +1m --2d * TODO 2c SCHEDULED: 2013-02-12 Tue +1m --2d in the agenda of today ([2013-02-12 Tue]) shows 1a 2a 1b 2b but I would expect 1a 2a 1b 1c. And there is a critical bug: Setting 2a to DONE repeats all entries below too. Michael
Re: [O] OT, but not really: todays XKCD
Dear Jambunathan, If I say Yagnesh has made zero contributions to Tamil Poetry does it amount to attacking you. Think about it. Sorry to say, that is very bad comparison. Seems you are trying to nullify Bastien's efforts. Though I don't want to quantify, here is one data point, I wonder how much contribution(s) sum up zero+ for you. But personally for me a contributor doesn't need to add code commits. I start counting from a mere up-voter on a thread , I consider anybody a contributor who has at least upvoted pro fsf/org thread. Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు. YYR
Re: [O] Still Wishing for Snooze
On Tue, Feb 12, 2013 at 1:29 PM, Michael Brand michael.ch.br...@gmail.com wrote: And there is a critical bug: Setting 2a to DONE repeats all entries below too. Reducing to a MCE shows me that triggering the repetitions requires #+STARTUP: nologrepeat Michael
Re: [O] OT, but not really: todays XKCD
Yagnesh Raghava Yakkala h...@yagnesh.org writes: Dear Jambunathan, If I say Yagnesh has made zero contributions to Tamil Poetry does it amount to attacking you. Think about it. Sorry to say, that is very bad comparison. Seems you are trying to nullify Bastien's efforts. You are blaming me for what I didn't say. How bad can it be. Re-read the mail I sent. Now contest my statement: Bastien has minimal contribution to new export framework or exporters. Hint: There is a (subtle) difference between: I am not eating Oranges and I am fasting. I will give you one more attempt. Try again. See whether you can convince me. Though I don't want to quantify, here is one data point, I wonder how much contribution(s) sum up zero+ for you. But personally for me a contributor doesn't need to add code commits. I start counting from a mere up-voter on a thread , I consider anybody a contributor who has at least upvoted pro fsf/org thread. Thanks., --
Re: [O] OT, but not really: todays XKCD
Yagnesh Raghava Yakkala h...@yagnesh.org writes: Though I don't want to quantify, here is one data point, Graphs are wonderful and colorful. The key thing is it's irrelevant. How about creating a graph that shows commit to the org-element.el and org-e-* files. Then we are talking. --
Re: [O] [ANN] outorg.el -- reverse Org-Babel
François Pinard pin...@iro.umontreal.ca writes: Thorsten Jolitz tjol...@gmail.com writes: [about the nearly coincident publication of *outorg* and *poporg*] What a bad luck ... ;( Oh, I'm not much into authorship wars, you know, as long as the need gets covered. Free time being a scarce resource (for me at least!), I prefer when we can all make the best use of it. Keep happy! Thanks, I really did miss your anouncement, and it was not the feedback I was looking for to hear that another (after looking at your code: better and more refined) version of the idea already exists. A bit discouraging, I must admit. So I consider 'outorg' now as a private project for my private use. Keep going with 'poporg' and make it part of emacs/org-mode - and look at 'outorg' as a proof that there is definitely a need out there that should get covered. -- cheers, Thorsten
Re: [O] OT, but not really: todays XKCD
Bastien b...@altern.org writes: It's important for two reasons: to keep a nice atmosphere on the list, so that people feel comfortable asking stupid questions; and to let other developers focus on their work (while you try to help newbies with their problems). It would have been difficult for you to focus on the ODT exporter or to Nicolas to focus on the new export engine if I didn't put enough energy to maintain the whole beast. Last line is comical. It reminds me of name Dilbert, for reason I cannot fathom. The worth of managers is over-estimated, particularly when the estimation is done by managers themselves. --
[O] [Warnings] HTML produced by new exporter
Hello, I exported a simple file: --8---cut here---start-8--- #+TITLE: Example of Tasks #+AUTHOR:Sebastien Vauban #+Time-stamp: 2013-02-12 Tue 16:04 #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en * Marketing ** STRT Hire PR firm :phone: --8---cut here---end---8--- and ran `tidy' on it. It reported 2 warnings: --8---cut here---start-8--- 63:59: Warning: nested emphasis span 81:126: Warning: nested emphasis span --8---cut here---end---8--- They come from the tag, once in the TOC, once in the headline: --8---cut here---start-8--- lia href=#sec-1-11.1. Hire PR firmnbsp;nbsp;nbsp;span class=tagspan class=phonephone/span/span/a ... h3 id=sec-1-1span class=section-number-31.1/span span class=todo STRTSTRT/span Hire PR firmnbsp;nbsp;nbsp;span class=tagspan class=phonephone/span/span/h3 --8---cut here---end---8--- Best regards, Seb -- Sebastien Vauban
Re: [O] format of the ID property in the new HTML exporter
Jambunathan K kjambunat...@gmail.com writes: There is ID and then there is CUSTOM_ID. IIUC/IIRC, ID is a uuid and CUSTOM_ID can be whatever. Any reason why you cannot use CUSTOM_IDs here? Yes. Why do you need the assert? It only seems to be there to make my life more difficult. -- Florian Beck
[O] src blocks in texinfo export
Hello, I discovered a problem when exporting source blocks containing braces to texinfo using `ox-texinfo'. The texinfo exporter wraps source blocks into a `example' environment, which takes care of source block indentation but doesn't allow any braces to occur in the contained text, since braces have a special meaning in TeX. After reading the `texinfo' manual, it became clear that literal examples should be exported also in a `verbatim' environment. A patch making this change to the exporter is attached. Dario diff --git a/lisp/ox-texinfo.el b/lisp/ox-texinfo.el index 8bc3520..211bf01 100644 --- a/lisp/ox-texinfo.el +++ b/lisp/ox-texinfo.el @@ -1409,7 +1409,7 @@ contextual information. (org-export-format-code-default src-block info))) ;; Case 2. Other blocks (t - (format @example\n%s@end example + (format @example\n@verbatim\n%s@end verbatim\n@end example (org-export-format-code-default src-block info)) ;;; Statistics Cookie
Re: [O] double-width characters in tables
Bastien b...@altern.org writes: Hi Eric, Eric Abrahamsen e...@ericabrahamsen.net writes: This problem has been flagged up before: http://orgmode.org/worg/org-issues.html#mid-87pqt04qg1-2Efsf-40gmail-2Ecom It's causing me headaches at the moment, so I'm trying to see if I can find a solution. The problem for me here is that even if (string-width 《蛙》) returns 6, it is not visually equivalent to 6 characters. Is it for you? If not, let's report this to Emacs... PS: Btw (org-string-width 《蛙》) returns the correct value. Yes, org-string-width eventually calls string-width, so that behaves correctly as far as it goes, but unfortunately that's not where the value in the text properties comes from... 《蛙》 123456 Doesn't that line up for you? Those bracket characters come with their own whitespace, maybe this is clearer: 正能量 123456 One Chinese character should definitely take up two screen columns. I'd love to file a bug report but I honestly don't know where this comes from. If it's not org-add-props or relatives, what emacs function is responsible? Thanks for the swift responses! Eric
Re: [O] OT, but not really: todays XKCD
On 12 feb. 2013, at 15:04, Jambunathan K kjambunat...@gmail.com wrote: Yagnesh Raghava Yakkala h...@yagnesh.org writes: Though I don't want to quantify, here is one data point, Graphs are wonderful and colorful. The key thing is it's irrelevant. How about creating a graph that shows commit to the org-element.el and org-e-* files. Then we are talking. You are really starting to make me angry. No one in this thread has claimed that Bastien to a major part of the commits or code lines of the parser. This is a fuzz you are generating all by yourself. - Carsten
[O] SETUPFILE and variants
Hello, With the new exporter, I still couldn't find how to use a setup file. Neither with: - the old `#+SETUPFILE:' directive - the new one (?): `#+SETUP_FILE:' - the soon to be unique one (?): `#+INCLUDE:' Am I missing something? Best regards, Seb ECM file: --8---cut here---start-8--- #+TITLE: Example of Tasks #+AUTHOR:Sebastien Vauban #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+INCLUDE: ~/src/org-style/bigblow.setup * Marketing ** STRT Hire PR firm --8---cut here---end---8--- -- Sebastien Vauban
Re: [O] double-width characters in tables
Eric Abrahamsen e...@ericabrahamsen.net wrote: 《蛙》 123456 Doesn't that line up for you? Those bracket characters come with their own whitespace, maybe this is clearer: 正能量 123456 I use a fixed-width font in my emacs and those two do not line up for me (the Chinese chars reach to about the middle of the 5). One Chinese character should definitely take up two screen columns. It does not seem to, in my case. Nick PS. In case it matters, I have this in my .emacs: (set-default-font -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso8859-1)
Re: [O] Still Wishing for Snooze
Hi Michael, Michael Brand michael.ch.br...@gmail.com writes: And there is a critical bug: Setting 2a to DONE repeats all entries below too. I fixed this one. I'm looking in the other issue right now. Thanks! -- Bastien
Re: [O] Bug in org-src.el?
Bastien b...@altern.org writes: Hi Bastien, Yes, I've seen this error too sometimes and it was not easy to fix when I tried to. Can you share the minimal code block to reproduce? ,-- | * org-src.el bug MWE | | #+begin_src picolisp :results output html | (+ 3 5) | #+end_src | | #+results: | #+BEGIN_HTML | #+END_HTML `-- ,-- | executing Picolisp code block... | executing Picolisp source code block | Wrote /tmp/babel-81734R/input-817F22 | org-escape-code-in-region: Invalid search bound (wrong side of point) `-- I discovered this with a much more complicated code block, but with some (not really successfull) debugging I found out that the problem is simply an empty result string, i.e. this happens when 'results' is ''. So its easy to reproduce with any expression that doesn't produce output. -- cheers, Thorsten
Re: [O] OT, but not really: todays XKCD
You are really starting to make me angry. I let go of my commit access sometime ago. Now, I am leaving this forum. Peace. --
Re: [O] src blocks in texinfo export
Hello Dario, On 12 February 2013 10:36, Dario Hamidi dario.ham...@gmail.com wrote: Hello, I discovered a problem when exporting source blocks containing braces to texinfo using `ox-texinfo'. The texinfo exporter wraps source blocks into a `example' environment, which takes care of source block indentation but doesn't allow any braces to occur in the contained text, since braces have a special meaning in TeX. After reading the `texinfo' manual, it became clear that literal examples should be exported also in a `verbatim' environment. A patch making this change to the exporter is attached. Using your patch as is would wrap the source blocks in both example and verbatim blocks. If going with verbatim it would be better to remove all references to @example/@end example. I had chosen to go with @example rather than @verbatim because it does state that lisp blocks should be wrapped in @lisp which is synonymous to @example. It should be possible to escape any braces or @ before inserting them into the example block to ensure there is no expansion. The only differences in using @verbatim over escaping any characters in @example are the following: - Tabs are treated as tabs and not as single spaces - The code block is not indented. Regards, Jon Dario
Re: [O] Still Wishing for Snooze
Hi Michael, Michael Brand michael.ch.br...@gmail.com writes: This * TODO 1a SCHEDULED: 2013-01-10 Thu +1m --2d * TODO 2a SCHEDULED: 2013-02-10 Sun +1m --2d * TODO 1b SCHEDULED: 2013-01-11 Fri +1m --2d * TODO 2b SCHEDULED: 2013-02-11 Mon +1m --2d * TODO 1c SCHEDULED: 2013-01-12 Sat +1m --2d * TODO 2c SCHEDULED: 2013-02-12 Tue +1m --2d in the agenda of today ([2013-02-12 Tue]) shows 1a 2a 1b 2b but I would expect 1a 2a 1b 1c. This should be fixed now. Thanks for the clear example and the testing. -- Bastien
Re: [O] Bug in org-insert-heading-after-current?
Bastien b...@altern.org writes: Hi Bastien, , | * Definitions | :PROPERTIES: | :exports: both | :results: replace | * | [2013-01-28 Mo 17:48] | :END: ` while the new heading should be below the :END: I cannot reproduce this with the current HEAD of the git repository and a bare emacs -Q. It did happen, but now - without updating Org-mode - I cannot reproduce it anymore. So, sorry for the noise. -- cheers, Thorsten
Re: [O] Bug in org-src.el?
Hi Thorsten, Thorsten Jolitz tjol...@gmail.com writes: I discovered this with a much more complicated code block, but with some (not really successfull) debugging I found out that the problem is simply an empty result string, i.e. this happens when 'results' is ''. So its easy to reproduce with any expression that doesn't produce output. Indeed! Fixed in master. Thanks for pushing following up on this one, it has been nagging me several times. Best, -- Bastien
Re: [O] Calling 'org-babel-mark-block' with 'M-x cmd' and 'M-: (cmd)'
Bastien b...@altern.org writes: Hi Bastien, Can you reproduce it with a recent Emacs? My Emacs is fairly recent: , | GNU Emacs 24.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4) | of 2013-01-20 on eric | | Org-mode version 7.9.3e (7.9.3e-921-g4d5c79 @ /home/tj/gitclone/org-mode/lisp/) ` Also, M-h is bound to `org-mark-element', which will mark a block (the whole block, not just its content). You might find it useful too! Thats very useful, indeed. But the same thing happens when calling 'org-babel-mark-block' or 'org-mark-element' with 'M-: (cmd)': cursor jumps to beginning of the block/element, nothing is highlighted (transient mark mode), and doing 'M-w' does not put anything into the kill-ring. With 'M-x cmd', highlighting and copying works. Thats not really a problem for me - just a bit strange. -- cheers, Thorsten
Re: [O] OT, but not really: todays XKCD
El Tue, 12 Feb 2013 19:28:24 +0530 Jambunathan K va escriure: I will give you one more attempt. Try again. See whether you can convince me. Wow, you like discussing! You would enjoy a debate association. I did it and I enjoyed very much, it's discussing only for its own sake. I suggest you a challenging exercise: correct facts /without/ causing a negative response from the list. It may be difficult but it's useful. In this way we will be able to focus discussions on more useful and relevant topics.
Re: [O] [BUG] (error Lisp nesting exceeds `max-lisp-eval-depth')
Hi Sébastien, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: Since the last pull I made, I can't expand anymore BBDB aliases in Gnus... because of Org! Do you have the same error when you don't load yasnippets? It looks like this is a bad interaction between yasnippets and orgstruct++-mode, not a bug only in orgstruct++-mode. Thanks, -- Bastien
Re: [O] time stamps in table of contents
Yes, thank you everyone for replying, this indeed works.
- Carsten
On 12 feb. 2013, at 10:59, Bastien b...@altern.org wrote:
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
Don't you forget the `.' in front of timestamp, for the class
spec?
Yes
#table-of-contents .timestamp {
display:none;
}
works correctly.
--
Bastien
--
Happiness is a false goal. You cannot pursue an emotion. Happiness is a
byproduct of having a purpose in life -- Julia Sweeney
[O] Align argument in #+attr_latex for tabular env. is whitespace sensitive
Was not getting the results I expected from #+attr_latex, so I created
a simplified table to test:
#+begin_src org
Centered (will be sent to LaTeX as =\begin{tabular}{cc}=:
#+attr_latex: align=cc
| test | test |
| test of longer | test |
Left aligned (will be sent to LaTeX as =\begin{tabular}{ll}=:
#+attr_latex: align = cc
| test | test |
| test of longer | test |
#+end_src
If there's reason for this, I can change my habits. I guess from
various tidy programming habits, I'm just in the practice of
separating equal signs with surrounding white space for easier
readability. For what it's worth, these two behave identically:
#+attr_latex: width=5cm
#+attr_latex: width = 5cm
I'm not sure why the tabular align argument is behaving differently.
Thanks for any feedback,
john
Re: [O] [BUG] (error Lisp nesting exceeds `max-lisp-eval-depth')
HI Bastien, Bastien wrote: Sebastien Vauban writes: Since the last pull I made, I can't expand anymore BBDB aliases in Gnus... because of Org! Do you have the same error when you don't load yasnippets? It looks like this is a bad interaction between yasnippets and orgstruct++-mode, not a bug only in orgstruct++-mode. After testing: nope, it does not occur when YASnippet is not loaded. Best regards, Seb -- Sebastien Vauban
Re: [O] Macro expansion in new exporter
Hello,
tftor...@tftorrey.com (T.F. Torrey) writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
On that topic, the main difference with the previous exporter is that
macros are now required to be in a context that can be parsed. Thus, for
example, the following is not a macro:
~{{{title}}}~
What is meant by a context that can be parsed?
Anywhere but in verbatim areas like:
- example blocks
- src blocks, inline src-blocks
- fixed-width area
- keywords (excepted CAPTION, DATE, TITLE, AUTHOR, EMAIL and MACRO).
- verbatim and code emphasis.
- block boundaries
In my work, it has been very useful to use macros for snippets of
text. Then, instead of changing the text everywhere when I want a
change, I would just change the macro. So...
For instance, I used to be able to do this:
#+MACRO: status Draft
#+HTML: p class=status{{{status}}}/p
And on export to HTML, I would get what you would expect:
p class=statusDraft/p
With the new exporter, the macro is left unexpanded in the output:
p class=status{{{status}}}/p
Because the macro is in a keyword that means: do not parse this
contents, it is for the html back-end only.
Of course, I could also put the {{{status}}} in any ordinary text and
have it there as well.
In extensive experiments, I have not found any combination of input that
would produce the old output using macros.
It's possible, macros are not exactly the same. Some of their old
functionalities are meant to be reached through Babel now. It may sounds
bad, but it allows a better control on macro expansion.
The old behavior had an elegant, one-line solution. Perhaps the
functionality could be duplicated with babel, but surely not as simply
and directly as with the old macro system.
Is there a way to replicate the old behavior in the new export engine?
I didn't check thoroughly, but I would say this kind of feature requires
some Babel code.
Also, in your response to Carsten's question about macros, you suggested
this:
#+MACRO: thumbright @@html:img src=./Content/$2/thumb.jpg
style=float:right;width:$1;margin:0px 20px 0px 20px;
alt=./Content/$2/thumb.jpg /@@
The @@ syntax looks new to me. Can you tell me what the function of
the @@ is? Is this documented somewhere?
It is called an export-snippet. @@html:...@@ syntax is to #+begin_html
blocks what =...= is to #+begin_example blocks. It replaces old @...
syntax, which was HTML only. Now you can have @@latex:...@@ or
@@beamer:...@@ syntax.
Regards,
--
Nicolas Goaziou
Re: [O] OT, but not really: todays XKCD
On 2/12/13, Jambunathan K kjambunat...@gmail.com wrote: I let go of my commit access sometime ago. Now, I am leaving this forum. Peace. Yes, I think we will have peace. I feel more comfortable on this list now than I have in a very long time. Thank you. 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] Still Wishing for Snooze
Hi Bastien On Tue, Feb 12, 2013 at 5:33 PM, Bastien b...@altern.org wrote: This should be fixed now. Thanks for the clear example and the testing. Thank you for fixing the bugs and mainly for the --2d delay for repeated SCHEDULED. To summarize my point of view of this thread: Originally I wanted to use such a delay primarily for repeated DEADLINE. But as I had to realize, to me such a delay seems not simple enough to use with warning periods other than -0d. Maybe I will adapt my usage of SCHEDULED a bit so that I can use repeated SCHEDULED with the new --2d delay, instead of my current not delayable repeated DEADLINE with -0d. Michael
Re: [O] [ANN] outorg.el -- reverse Org-Babel
Thorsten Jolitz tjol...@gmail.com writes: François Pinard pin...@iro.umontreal.ca writes: Keep happy! A bit discouraging, I must admit. Don't be! We need all the courage we can get! Keep going with 'poporg' and make it part of emacs/org-mode - and look at 'outorg' as a proof that there is definitely a need out there that should get covered. poporg has many flaws, and is surely not up to the quality of Org. Nevertheless, I much use it even if imperfect, while knowing it should be improved in many ways. If we could make something better out of two imperfections, it could be worth trying. If only I had more time! Sigh! François
Re: [O] [ANN] outorg.el -- reverse Org-Babel
This looks great. One suggestion: what about optionally allowing you to keep your Org notes in Org? That would allow all Org features. You'd do it by putting a specially-formatted Org ID in the comment, and then you have a key that bounces back and forth. ;;; $[id 123451243512345] Then in Org you have that ID as a property. That way you can choose whether to have your documentation in the source file using Org syntax or in Org. 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] OT, but not really: todays XKCD
Jambunathan K kjambunat...@gmail.com writes: Bastien b...@altern.org writes: [...] to keep a nice atmosphere on the list, [...] put enough energy to maintain the whole beast. the estimation is done by managers themselves. I find Bastien to be a very good maintainer. I maintained a good deal of software in my computer life, some being much more visible than Org. Yet, Bastien shows me how I could have been a much better maintainer, and in many ways. He demonstrates a good balance between being able to listen and communicate, and yet being firm enough to take decisions. And these decisions are such that Org continues to stay rather consistent while being opened to a lot of diversity, which to me is a little miracle in itself. How he can succeed in finding enough time for all the timely supports he gives us, is a wonderful mystery to me. Jambunathan, I prefer to think, right or wrong, that your account has been pirated, and that someone else is impersonating you. The truth is that I admired your work and involvement around the ODT exporter, and with the Org community. Some people wrote to me about you, sharing the high praise they have towards the quality of your code. So, I prefer to blindly stick with my admiration, and forget all the rest. :-) Peace! François
Re: [O] [BUG] (error Lisp nesting exceeds `max-lisp-eval-depth')
Hi Sébastien, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: After testing: nope, it does not occur when YASnippet is not loaded. Now that John H. gave me some directions on using yasnippet, I'm ready to test further and to hunt your bug. Would you mind sharing the minimal yas/org config I need to reproduce the problem? Let me insist on minimal :) Thanks, -- Bastien
Re: [O] double-width characters in tables
Eric Abrahamsen writes: Yes, org-string-width eventually calls string-width, so that behaves correctly as far as it goes, but unfortunately that's not where the value in the text properties comes from... 《蛙》 123456 Doesn't that line up for you? Those bracket characters come with their own whitespace, maybe this is clearer: 正能量 123456 One Chinese character should definitely take up two screen columns. That's a function of the font that is ultimately used and their run-length. Since you are unlikely to use a font that has _all_ those glyphs, eventually the ones that are missing in your specified font will be replaced with the glyph corresponding to the same codepoint in a different font if it exists or possibly a composition of multiple glyphs (if not you'll get a placeholder). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] new exporter fails to output footnotes?
On 2/11/13, Nicolas Goaziou n.goaz...@gmail.com wrote: It should be fixed in master. Could you confirm it? Thank you. Confirmed that footnotes are included in HTML now. They are missing from plain text export. In HTML, how do you control the hlevel of the footnotes header? Also, there is a formatting issue with footnotes. Here they are in w3m: === ^ They became popular in the silence=death era. 1 This image by Jock Cooper is licensed under a Creative ^ Commons Attribution-Noncommercial 3.0 United States 2 License. ^ I didn't look up the types of self-similarity in 3 fractals. This image is protected by a True Scottish copyright: ^ Creative Commons, Attribution — Noncommercial — 4 Share-alike 2.5 UK: Scotland. ^ Creative Commons Attribution-Share Alike 3.0 Unported 5 ^ Cur CUD brih sure I ween. 6 === A slightly different formatting issue occurs in Firefox by default, but copy and paste might not depict it. === Thanks. 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] [BUG] (error Lisp nesting exceeds `max-lisp-eval-depth')
Bastien, Bastien wrote: Sebastien Vauban writes: After testing: nope, it does not occur when YASnippet is not loaded. Now that John H. gave me some directions on using yasnippet, I'm ready to test further and to hunt your bug. Would you mind sharing the minimal yas/org config I need to reproduce the problem? Let me insist on minimal :) Okaayyy, understood! ;-) #+begin_src emacs-lisp (add-to-list 'load-path ~/Public/Repositories/yasnippet) ;; Yet Another Snippet extension for Emacs (require 'yasnippet) ;; root directories that store the snippets (setq yas/root-directory nil) (let ((my-snippets ~/src/yasnippet/snippets) (local-snippets ~/Public/Repositories/yasnippet/snippets)) (when (file-directory-p local-snippets) (add-to-list 'yas/root-directory local-snippets)) ;; the first element is always the user-created snippets directory (when (file-directory-p my-snippets) (add-to-list 'yas/root-directory my-snippets))) ;; enable the YASnippet menu and tab-trigger expansion in *all* ;; buffers (yas/global-mode 1) ;; text that will be used in menu to represent the trigger (setq yas/trigger-symbol tab) ;; allow YASnippet to do its thing in Org files (when (fboundp 'yas/expand) (defun yas/org-very-safe-expand () (let ((yas/fallback-behavior 'return-nil)) (yas/expand))) (add-hook 'org-mode-hook (lambda () (set (make-local-variable 'yas/trigger-key) (kbd tab)) ;; needed? (add-to-list 'org-tab-first-hook 'yas/org-very-safe-expand) (define-key yas/keymap (kbd tab) 'yas/next-field ;; needed? #+end_src Best regards, Seb -- Sebastien Vauban
Re: [O] how to indent plain lists in ASCII
I think I got this to work now. Thanks. I had had code to work around something else.
Re: [O] orgstruct-mode with custom headline prefix
Christopher Schmidt writes: This is in master now. The commit is a3f6570. This introduces the following failures in compilation with Emacs 24.2 and has a high chance of not working at all in some setups: --8---cut here---start-8--- Compiling /home/gratz/lisp/org-mode/lisp/org.el... In org-heading-components: org.el:7436:16:Warning: reference to free variable `orgstruct-mode' In org-run-like-in-org-mode: org.el:8841:20:Warning: function `cl-progv-before' from cl package called at runtime In end of data: org.el:23217:1:Warning: the function `cl-progv-after' is not known to be defined. --8---cut here---end---8--- …and no, I have no idea how that single progv macro manages to expand to use these two functions. Emacs 24.3.93 seems to have that fixed, but complains about this instead: In org-heading-components: org.el:7436:16:Warning: reference to free variable `orgstruct-mode' In end of data: org.el:23217:1:Warning: the following functions might not be defined at runtime: easy-menu-add, format-spec Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] How to get === on a line by itself to be a special string
On 2/10/13, Nicolas Goaziou n.goaz...@gmail.com wrote: (defun my-rule-markup (paragraph backend info) (when (and (org-export-derived-backend-p backend 'html) (string-match p\ncode=/code\n/p\n* paragraph)) hr width=\10%\ style=\width:10%;color:#000;background-color:#000;height:1px;border:none\/\n\n)) (add-to-list 'org-export-filter-paragraph-functions 'my-rule-markup) I think this restores the behavior. Thank you. 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] Running a sudo in a #+begin_src sh fails to get tty and askpass
#+begin_src sh :dir /sudo:: apt-get update #+end_src Thanks! Emilio
Re: [O] OT, but not really: todays XKCD
On Tue, Feb 12, 2013 at 10:10 AM, Jambunathan K kjambunat...@gmail.com wrote: Bastien b...@altern.org writes: It's important for two reasons: to keep a nice atmosphere on the list, so that people feel comfortable asking stupid questions; and to let other developers focus on their work (while you try to help newbies with their problems). It would have been difficult for you to focus on the ODT exporter or to Nicolas to focus on the new export engine if I didn't put enough energy to maintain the whole beast. Last line is comical. It reminds me of name Dilbert, for reason I cannot fathom. The worth of managers is over-estimated, particularly when the estimation is done by managers themselves. I dislike this kind of negativity, so I've added you to my spam filter. Bye bye. -Ista
Re: [O] Align argument in #+attr_latex for tabular env. is whitespace sensitive
Hello,
John Hendy jw.he...@gmail.com writes:
Was not getting the results I expected from #+attr_latex, so I created
a simplified table to test:
#+begin_src org
Centered (will be sent to LaTeX as =\begin{tabular}{cc}=:
#+attr_latex: align=cc
| test | test |
| test of longer | test |
Left aligned (will be sent to LaTeX as =\begin{tabular}{ll}=:
#+attr_latex: align = cc
| test | test |
| test of longer | test |
#+end_src
If there's reason for this, I can change my habits. I guess from
various tidy programming habits, I'm just in the practice of
separating equal signs with surrounding white space for easier
readability. For what it's worth, these two behave identically:
#+attr_latex: width=5cm
#+attr_latex: width = 5cm
I'm not sure why the tabular align argument is behaving differently.
This syntax is wrong anyway. It should be:
#+attr_latex: :width 5cm
or
#+attr_latex: :width 5cm
The same goes for :align. Also, for simple alignment strings, you can
provide align cookies within the table.
Regards,
--
Nicolas Goaziou
Re: [O] BIND org-html-style-include-*
Hello, tftor...@tftorrey.com (T.F. Torrey) writes: In my files, this used to work to suppress the default styles and javascript: #+BIND: org-export-html-style-include-default nil #+BIND: org-export-html-style-include-scripts nil Now, I have these: #+BIND: org-html-style-include-default nil #+BIND: org-html-style-include-scripts nil But they seem to be silently ignored, though if I setq the values ahead of time, the output is suppressed. Can these still be set using BIND? If so, what am I doing wrong? What is the value of `org-export-allow-bind-keywords'? Also, the value of org-html-mathjax-template seems to be output now by default, and I don't remember seeing it before. Is this an intended change? If so, how can it be suppressed? (If not ... ???) I cannot answer you for now, because I don't know enough of the HTML back-end. Regards, -- Nicolas Goaziou
Re: [O] [new exporter] workaround/replacement for org-export-as-html-batch
Hello,
Detlef Steuer detlef.ste...@gmx.de writes:
I rely on
emacs --batch \
--eval (add-to-list 'load-path \${HOME}/GIT/org-mode/lisp/\)\
--load ${HOME}/GIT/org-mode/lisp/org.el \
--visit file.org \
--funcall org-export-as-html-batch
somewhere in my HTML generating workflow.
You may want to set-up a publishing project instead.
Does `org-html-export-to-html' works as a replacement for
`org-export-as-html-batch'?
I see org-export-as-html-batch in the FIXME section in the source.
The FIXME section ought to be fixed anyway.
Is there any easy workaround for the moment? Or a guess when it will leave
that section?
Naively loading the old stuff by adding a
---eval (add-to-list 'load-path
\${HOME}/GIT/org-mode/contrib/oldexp/\)\
line to the call above did not work either.
I then get:
---
Exporting...
Symbol's value as variable is void: org-export-with-sub-superscripts
---
The old export framework is not usable anymore from master branch.
Regards,
--
Nicolas Goaziou
Re: [O] Align argument in #+attr_latex for tabular env. is whitespace sensitive
On Tue, Feb 12, 2013 at 1:22 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
John Hendy jw.he...@gmail.com writes:
Was not getting the results I expected from #+attr_latex, so I created
a simplified table to test:
#+begin_src org
Centered (will be sent to LaTeX as =\begin{tabular}{cc}=:
#+attr_latex: align=cc
| test | test |
| test of longer | test |
Left aligned (will be sent to LaTeX as =\begin{tabular}{ll}=:
#+attr_latex: align = cc
| test | test |
| test of longer | test |
#+end_src
If there's reason for this, I can change my habits. I guess from
various tidy programming habits, I'm just in the practice of
separating equal signs with surrounding white space for easier
readability. For what it's worth, these two behave identically:
#+attr_latex: width=5cm
#+attr_latex: width = 5cm
I'm not sure why the tabular align argument is behaving differently.
This syntax is wrong anyway. It should be:
#+attr_latex: :width 5cm
or
#+attr_latex: :width 5cm
The same goes for :align. Also, for simple alignment strings, you can
provide align cookies within the table.
Ah. Very good to know. Is this documented? This is the syntax I use
for babel blocks, but I've never seen it for #+attr_latex. The manual
also doesn't show any =:option value= methods, at least in my
initial peruse:
- http://orgmode.org/manual/Tables-in-LaTeX-export.html
- http://orgmode.org/manual/Images-in-LaTeX-export.html#Images-in-LaTeX-export
It's all in `option=value` format.
Is your syntax (including the comment about cookies, as I haven't seen
that in the org manual either) relevant for the old exporter, or only
the new one? As I said, this is using the old exporter and I haven't
migrated over yet...
Thanks for the prompt response!
John
Regards,
--
Nicolas Goaziou
Re: [O] Invalid read syntax (#) in org-element parse tree
Thorsten Jolitz tjol...@gmail.com writes: I'm not sure about what you want to do with the parse tree. The usual function to work with it is `org-element-map'. You may want to have a look at its docstring, as it contains examples. I want to write an 'unusual' backend that does not need anything else from the exporting framework but the parse-tree as a list. Then you don't want the exporting framework at all, only org-element.el. Anyway I'm confused. The parse-tree _is_ a list. To convince yourself, evaluate the following in any Org buffer: (listp (org-element-parse-buffer)) So all I need would be a workaround for this read-error issue, i.e. a tip how to get a version of the parse tree that can be used as list in a Lisp program. Have you tried (setq print-circle t) ? I could not find any explanation for the '#1' and '#2' syntax I encountered, so I don't really know what its all about. It is explained in the info link I gave you. Regards, -- Nicolas Goaziou
Re: [O] Align argument in #+attr_latex for tabular env. is whitespace sensitive
John Hendy jw.he...@gmail.com writes:
On Tue, Feb 12, 2013 at 1:22 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
John Hendy jw.he...@gmail.com writes:
Was not getting the results I expected from #+attr_latex, so I created
a simplified table to test:
#+begin_src org
Centered (will be sent to LaTeX as =\begin{tabular}{cc}=:
#+attr_latex: align=cc
| test | test |
| test of longer | test |
Left aligned (will be sent to LaTeX as =\begin{tabular}{ll}=:
#+attr_latex: align = cc
| test | test |
| test of longer | test |
#+end_src
If there's reason for this, I can change my habits. I guess from
various tidy programming habits, I'm just in the practice of
separating equal signs with surrounding white space for easier
readability. For what it's worth, these two behave identically:
#+attr_latex: width=5cm
#+attr_latex: width = 5cm
I'm not sure why the tabular align argument is behaving differently.
This syntax is wrong anyway. It should be:
#+attr_latex: :width 5cm
or
#+attr_latex: :width 5cm
The same goes for :align. Also, for simple alignment strings, you can
provide align cookies within the table.
Ah. Very good to know. Is this documented?
It was only announced on this ML.
This is the syntax I use for babel blocks, but I've never seen it for
#+attr_latex. The manual also doesn't show any =:option value=
methods, at least in my initial peruse:
- http://orgmode.org/manual/Tables-in-LaTeX-export.html
- http://orgmode.org/manual/Images-in-LaTeX-export.html#Images-in-LaTeX-export
It's all in `option=value` format.
Is your syntax (including the comment about cookies, as I haven't seen
that in the org manual either) relevant for the old exporter, or only
the new one? As I said, this is using the old exporter and I haven't
migrated over yet...
The Babel-like syntax is only relevant for the new exporter.
The old exporter had some support for align cookies in table (depending
on the back-end).
Regards,
--
Nicolas Goaziou
Re: [O] Exporter question
Hello, Dominik, Carsten c.domi...@uva.nl writes: In a file with some time stamps in headlines, is it still possible to get rid of them only for the Table of Contents, but to leave them in the headlines themselves? Good question. You can probably use filters, but it isn't a trivial task, depending on the back-end. How did you do it in the previous exporter? Regards, -- Nicolas Goaziou
Re: [O] Align argument in #+attr_latex for tabular env. is whitespace sensitive
On Tue, Feb 12, 2013 at 1:44 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
John Hendy jw.he...@gmail.com writes:
On Tue, Feb 12, 2013 at 1:22 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
John Hendy jw.he...@gmail.com writes:
Was not getting the results I expected from #+attr_latex, so I created
a simplified table to test:
#+begin_src org
Centered (will be sent to LaTeX as =\begin{tabular}{cc}=:
#+attr_latex: align=cc
| test | test |
| test of longer | test |
Left aligned (will be sent to LaTeX as =\begin{tabular}{ll}=:
#+attr_latex: align = cc
| test | test |
| test of longer | test |
#+end_src
If there's reason for this, I can change my habits. I guess from
various tidy programming habits, I'm just in the practice of
separating equal signs with surrounding white space for easier
readability. For what it's worth, these two behave identically:
#+attr_latex: width=5cm
#+attr_latex: width = 5cm
I'm not sure why the tabular align argument is behaving differently.
This syntax is wrong anyway. It should be:
#+attr_latex: :width 5cm
or
#+attr_latex: :width 5cm
The same goes for :align. Also, for simple alignment strings, you can
provide align cookies within the table.
Ah. Very good to know. Is this documented?
It was only announced on this ML.
This is the syntax I use for babel blocks, but I've never seen it for
#+attr_latex. The manual also doesn't show any =:option value=
methods, at least in my initial peruse:
- http://orgmode.org/manual/Tables-in-LaTeX-export.html
-
http://orgmode.org/manual/Images-in-LaTeX-export.html#Images-in-LaTeX-export
It's all in `option=value` format.
Is your syntax (including the comment about cookies, as I haven't seen
that in the org manual either) relevant for the old exporter, or only
the new one? As I said, this is using the old exporter and I haven't
migrated over yet...
The Babel-like syntax is only relevant for the new exporter.
The old exporter had some support for align cookies in table (depending
on the back-end).
Good to know. I guess this gives me reason to switch over!
John
Regards,
--
Nicolas Goaziou
Re: [O] [ANN] outorg.el -- reverse Org-Babel
Thorsten Jolitz writes: 'outorg' is based on the idea that it would be nice to be able to 1. structure your source-code files like Org-mode files and use all the structure editing and navigation commands available. Does it mean it can superseed orgstruct-mode, or should one use both? In any case, I find this and poporg great ideas! Alan
Re: [O] Exporter question
On 12.2.2013, at 20:46, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Dominik, Carsten c.domi...@uva.nl writes: In a file with some time stamps in headlines, is it still possible to get rid of them only for the Table of Contents, but to leave them in the headlines themselves? Good question. You can probably use filters, but it isn't a trivial task, depending on the back-end. I have now succeeded using CSS, but this is for HTML only, of course. How did you do it in the previous exporter? There used to be a variable org-export-remove-timestamps-from-toc, and a function org-export-cleanup-toc-line which provided this functionality. It is actually somewhat useful functionality. It there a filter that is applied only to toc lines? Regards - Carsten
Re: [O] Macro expansion in new exporter
Hello Nicolas, Thank you for your thoughtful clarification about macros in the new exporter. Probably in the long run I will find happiness using babel for what I want to do. In the meantime, however, I have a few more questions: 1. You wrote before that macros were scaled back because what they did could be done by babel. Is that really a good reason for removing functionality? Everything that Org does could be done in other tools, and yet ... we have Org. 2. You wrote to Carsten that macros could no longer contain newlines. That seems like an arbitrary limitation. Is it? 3. Is there really a reason why macro expansion is limited to a few keywords rather than all? Who would that trip up? Ditto for verbatim and code emphasis. 4. Given that macro values are easy to find in the source document, and unexpanded macros are easy to find in the output document, couldn't I just add a filter to the exporter to find and expand any unexpanded macros (and lingering newline indicators)? Is there an easy method for adding such a filter? 5. Actually, why do macros need to be an exporter problem at all? Couldn't the macro functionality be put into a separate package that used hooks and filters to connect itself into the export routine and the various back-ends (if even necessary)? Then macros could be made to do interesting things without burdening the export engine (and its maintainer) at all. Thanks again for your amazing work. Best regards, Terry -- T.F. Torrey
Re: [O] Problem with org-html-format-latex
Hi, (let ((cache-relpath ) (cache-dir ) bfn) Mhh... okay. Now should be good. Yep, thanks! Thanks for your patience. No thanks needed, nor patience either for that matter, you and the other devs are the ones who should be thanked ... /v -- Bastien
Re: [O] orgstruct-mode with custom headline prefix
Achim Gratz strom...@nexgo.de writes: This introduces the following failures in compilation with Emacs 24.2 and has a high chance of not working at all in some setups: --8---cut here---start-8--- Compiling /home/gratz/lisp/org-mode/lisp/org.el... In org-heading-components: org.el:7436:16:Warning: reference to free variable `orgstruct-mode' In org-run-like-in-org-mode: org.el:8841:20:Warning: function `cl-progv-before' from cl package called at runtime In end of data: org.el:23217:1:Warning: the function `cl-progv-after' is not known to be defined. --8---cut here---end---8--- Great. …and no, I have no idea how that single progv macro manages to expand to use these two functions. These internal functions should have been autoloaded. progv is pretty obscure and I guess noone has noticed that bug in cl-macs until now. Emacs 24.3.93 seems to have that fixed, So does 24.2.x. I will push a fix ASAP. but complains about this instead: In org-heading-components: org.el:7436:16:Warning: reference to free variable `orgstruct-mode' This one is bogus, the variable is defined later on. I will silence that warning. Christopher
Re: [O] Invalid read syntax (#) in org-element parse tree
Nicolas Goaziou n.goaz...@gmail.com writes: I want to write an 'unusual' backend that does not need anything else from the exporting framework but the parse-tree as a list. Then you don't want the exporting framework at all, only org-element.el. yes, only the parser. Anyway I'm confused. The parse-tree _is_ a list. To convince yourself, evaluate the following in any Org buffer: (listp (org-element-parse-buffer)) So all I need would be a workaround for this read-error issue, i.e. a tip how to get a version of the parse tree that can be used as list in a Lisp program. Have you tried (setq print-circle t) ? I could not find any explanation for the '#1' and '#2' syntax I encountered, so I don't really know what its all about. It is explained in the info link I gave you. I read this link, it says: , | To represent shared or circular structures within a complex of Lisp | objects, you can use the reader constructs ‘#n=’ and ‘#n#’. ` what is not quite the same like ,--- | :parent #1 `--- but with your other hints, I now understand the problem. I wanted to see how the parse tree looks like, so I printed it out (I did not know about the existance of 'print-circle' then, but it was set to nil). Then I tried to experiment with the printed representation, but the #1 syntax gave me an error. When I set 'print-circle' to t, the printed result looks like described in the info page, with elements like [...] :parent #66# #67=(headline [...] -- cheers, Thorsten
Re: [O] Invalid read syntax (#) in org-element parse tree
Thorsten Jolitz tjol...@gmail.com writes: [continuation, prior message sent unfinished by accident] but with your other hints, I now understand the problem. I wanted to see how the parse tree looks like, so I printed it out (I did not know about the existance of 'print-circle' then, but it was set to nil). Then I tried to experiment with the printed representation, but the #1 syntax gave me an error. When I set 'print-circle' to t, the printed result looks like described in the info page, with elements like [...] :parent #66# #67=(headline [...] So it was all about the difference between printed representation and the actual list object, and the special syntax when 'print-circle' is nil that I could not find in the manual. Thanks for the tips, I have to read more about circular lists in Emacs Lisp, ,first time I see them in action. -- cheers, Thorsten
Re: [O] orgstruct-mode with custom headline prefix
Hi Christopher, Christopher Schmidt christop...@ch.ristopher.com writes: These internal functions should have been autoloaded. progv is pretty obscure and I guess noone has noticed that bug in cl-macs until now. The attached patch gets rid of progv by using org-let. As a side-effect, it fixes a but that was introduced with your change: M-x turn-on-orgstruct RET in message-mode and try to move around list items for example... it will choke at org-auto-fill-function not being defined. The bug is not limited to this example of course. Let me know if it breaks something I may have overlooked. Emacs 24.3.93 seems to have that fixed, So does 24.2.x. I will push a fix ASAP. but complains about this instead: In org-heading-components: org.el:7436:16:Warning: reference to free variable `orgstruct-mode' This one is bogus, the variable is defined later on. I will silence that warning. Thanks in advance for this! diff --git a/lisp/org.el b/lisp/org.el index 5892489..b251cbe 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -8781,7 +8781,7 @@ Possible values in the list of contexts are `table', `headline', and `item'. (setq x (if (symbolp x) (list x) - (list (car x) (cdr x + (list (car x) (list 'quote (cdr x) (if (and (not (get (car x) 'org-state)) (string-match ^\\(org-\\|orgtbl-\\|outline-\\|comment-\\|paragraph-\\|auto-fill\\|normal-auto-fill\\|fill-paragraph\\|indent-\\) @@ -8810,15 +8810,8 @@ call CMD. (org-load-modules-maybe) (unless org-local-vars (setq org-local-vars (org-get-local-variables))) - (let (symbols values) -(dolist (var org-local-vars) - (when (or (not (boundp (car var))) - (eq (symbol-value (car var)) - (default-value (car var -(push (car var) symbols) -(push (cadr var) values))) -(progv symbols values - (call-interactively cmd + (org-let org-local-vars +(call-interactively cmd))) Archiving -- Bastien
Re: [O] Calling 'org-babel-mark-block' with 'M-x cmd' and 'M-: (cmd)'
Hi Thorsten, Thorsten Jolitz tjol...@gmail.com writes: Thats not really a problem for me - just a bit strange. So maybe this is by design. Similarily M-: (org-mark-element) RET does not highlight the region, while M-x org-mark-element RET does. Perhaps you can ask on emacs-devel for confirming this (or maybe someone who knows better will chime in this thread!) -- Bastien
Re: [O] [ANN] outorg.el -- reverse Org-Babel
Hi François and Thorsten, When great minds meet... ;) It's sometimes good to have two different implementations, ideas can flow from one to another. If you think one library is mature and useful enough for the contrib/ directory, please feel free to submit it! Note that both your libraries (supporting some Org syntax in comments) are a perfect match for Christopher recent chance in master, which allows a more powerful orgstruct-mode in those files -- with folding etc. If you didn't, have a look: C-h v orgstruct-heading-prefix-regexp RET is a starting point. Thanks! -- Bastien
Re: [O] Exporter question
Carsten Dominik carsten.domi...@gmail.com writes: There used to be a variable org-export-remove-timestamps-from-toc, and a function org-export-cleanup-toc-line which provided this functionality. It is actually somewhat useful functionality. It there a filter that is applied only to toc lines? Not a dedicated filter. But you can use `final-filter', which is applied to the whole output. Anyway, I add this feature on my TODO list. Regards, -- Nicolas Goaziou
Re: [O] src blocks in texinfo export
Hello Jonathan,
Using your patch as is would wrap the source blocks in both example and
verbatim blocks. If going with verbatim it would be better to remove all
references to @example/@end example.
I don't understand where the problem lies with having a `@verbatim'
within a `@example'. Could you maybe explain to me why this is
problematic?
Using both environments seems to achieve the goal of having an idented
source block in the resulting info file without having to further
process the source block before export.
Consider exporting
#+BEGIN_SRC sh
function fails
{
echo this causes an error with makeinfo
}
#+END_SRC
with only the verbatim environment:
File: test.info, Node: Top, Up: (dir)
Manual
**
function fails
{
echo this causes an error with makeinfo
}
and with verbatim in example:
File: test.info, Node: Top, Up: (dir)
Manual
**
function fails
{
echo this causes an error with makeinfo
}
It should be possible to escape any braces or @ before inserting them into
the
example block to ensure there is no expansion.
While it certainly is possible, it would also mean to properly escape
*all* characters with a special meaning to TeX. I suppose that making
text containing such characters visible in a document without having to
escape them is what the verbatim environment is for.
The only differences in using @verbatim over escaping any characters in
@example are the following:
- Tabs are treated as tabs and not as single spaces
- The code block is not indented.
Preserving whitespace seems like a good idea when displaying python
source code or makefiles.
Dario
Re: [O] Still Wishing for Snooze
I just got this installed today and it appears to be *exactly* what I wanted. Many thanks for this implementation. Your cheesecake is in the mail. :) :AMN: On 02/07/2013 01:44 AM, Bastien wrote: Hi Andrew, Andrew M. Nuxoll nux...@up.edu writes: If you do that, I may have to send you a cheesecake. Time for a cheesecake! You can now use a delay cookie like this: SCHEDULED: 2013-02-07 jeu. -2d The item will not be shown today, but in three days. See the new options `org-scheduled-delay-days' and `org-agenda-skip-scheduled-delay-if-deadline' which are quite symmetric to `org-deadline-warning-days' and `org-agenda-skip-deadline-prewarning-if-scheduled'. Thanks for this idea, and thanks to Michael for the implementation example -- I implemented it a bit differently, but I think it makes sense (1) to use -2d to tell the scheduled item is postponed, and (2) to use the same - for prewarning and delays. -- Andrew M. Nuxoll Phone: 503-943-7688 Asst Professor of Computer Science Fax: 503-943-7316 University of Portland - MSC #145Email: nux...@up.edu 5000 N. Willamette Blvd Web: http://faculty.up.edu/nuxoll Portland, OR 97203-5798 Office: Shiley Hall Rm 217
Re: [O] suggestion: M-m should move point to first word on line
Bastien b...@altern.org writes: [...] I'm not sure I'm in favor of this change, though, I expect it to cause other problems and the benefit looks small for now. Do you see other reasons than M-m where stars as whitespace chars are useful? What about *markup*? I have no issues with the current behaviour (i.e. the behaviour without your patch). I only tried out the patch to see what would happen! ;-) I never use M-m, relying on C-a (well, org variant actually) to do what I want. thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org 7.9.3e-988-g1f8c8d
Re: [O] OT, but not really: todays XKCD
Jambunathan K kjambunat...@gmail.com writes: [...] Pray explain why Carsten appears in the followup post and you yourself don't figure in it. Jambunathan, I cannot speak for Carsten. In my case, if I send an email to the list, I would expect following responses to go to that list as well; I don't need to get the emails directly addressed to me as I subscribe to the list. I realise that this is possibly non-intuitive based on normal practice for non-mailing list emails but, for a list, I think this is the best default as it makes it easy to respond to a list as opposed to the individual. I tell gnus I am subscribed to this list and it takes care of setting the headers for me. I have only customised the following two variables: #+begin_src emacs-lisp (setq message-subscribed-address-functions '(gnus-find-subscribed-addresses) message-subscribed-addresses '(d...@gnus.org emacs-orgmode@gnu.org) ) #+end_src If there is a consensus on the list that I am going against some form of etiquette for this list, I am happy to change my settings. I have no interest in annoying people! eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org 7.9.3e-988-g1f8c8d
[O] Modifying the exporter (was: org-latex-classes with functions, incomplete doc)
Nicolas Goaziou n.goaz...@gmail.com writes:
Anyway, we're back to step one: if you want to handle headlines
differently (i.e. by adding your own properties), you need to fork
`latex' back-end, as explained before. If you encounter problems, you
can post back here.
Ok, I took some time to extract a minimal example. It works fine, but
on a very low level (see below).
Again, the goal is to add an optional argument to sectioning command.
The best way I could come up with is this (I omit the
`fb/org-export-pdf' function):
#+BEGIN_SRC emacs-lisp
(defun fb/org-export-modify-headline (headline string)
(if (string-match
(rx
string-start \\
(group-n 1 (0+ sub))
(group-n 2 (or part chapter section paragraph))
(group-n 3 (zero-or-one \*))
{ (group-n 4 (minimal-match (0+ (not (any }) })
string)
(let* ((level (match-string 1 string))
(type (match-string 2 string))
(stars (match-string 3 string))
(title (match-string 4 string))
(toc-title (org-element-property :toc-title headline))
(new-hl
(format \\%s%s%s%s{%s}
(or level )
type
(or stars )
(if toc-title (format [%s] toc-title) )
title)))
(replace-match new-hl t t string 0))
string))
(defun fb/org-latex-headline (headline contents info)
(fb/org-export-modify-headline
headline
(org-export-with-backend 'latex headline contents info)))
(org-export-define-derived-backend fb/org-export-pdf latex
:translate-alist ((headline . fb/org-latex-headline))
:options-alist ((:toc-title TOC_TITLE nil nil t))
:menu-entry (?l 99 ((?d Export PDF file fb/org-export-pdf
#+END_SRC
As you can see, I pull apart the string and then put it back together.
(Relatively straightforward in this case, much more involved for, say,
links.)
In a perfect world, I would have access to these elements and the format
string, so I could either modify them before calling
`org-export-with-backend' or assemble the string myself.
--
Florian Beck
Re: [O] OT, but not really: todays XKCD
Am 12.02.2013 18:39, schrieb Samuel Wales: On 2/12/13, Jambunathan K kjambunat...@gmail.com wrote: I let go of my commit access sometime ago. Now, I am leaving this forum. Peace. Yes, I think we will have peace. I feel more comfortable on this list now than I have in a very long time. Thank you. Samuel +1 Thanks Bastien for your great work and your kind and patient way of helping me and many more of us using Org! Rainer
Re: [O] [ANN] outorg.el -- reverse Org-Babel
Bastien b...@altern.org writes: Hi Bastien, It's sometimes good to have two different implementations, ideas can flow from one to another. I agree ... besides that I did not have any intention to duplicate or compete, the Org-mode mailing list is just so busy that its hard to keep up. If you think one library is mature and useful enough for the contrib/ directory, please feel free to submit it! OK Note that both your libraries (supporting some Org syntax in comments) are a perfect match for Christopher recent chance in master, which allows a more powerful orgstruct-mode in those files -- with folding etc. If you didn't, have a look: I will try to refactor the whole thing so that it becomes independent from outline-minor-mode. C-h v orgstruct-heading-prefix-regexp RET I will have a look, thanks. -- cheers, Thorsten
Re: [O] OT, but not really: todays XKCD
Many thanks for maintaining a civil community +1 Bastien On Tue, Feb 12, 2013 at 6:39 PM, Rainer Stengele rainer.steng...@online.de wrote: Am 12.02.2013 18:39, schrieb Samuel Wales: On 2/12/13, Jambunathan K kjambunat...@gmail.com wrote: I let go of my commit access sometime ago. Now, I am leaving this forum. Peace. Yes, I think we will have peace. I feel more comfortable on this list now than I have in a very long time. Thank you. Samuel +1 Thanks Bastien for your great work and your kind and patient way of helping me and many more of us using Org! Rainer -- Evan Misshula Doctoral Student (Criminal Justice) CUNY John Jay Let us reform our schools, and we shall find little reform needed in our prisons. John Ruskin, Unto This Last, essay 2 (1862) English critic, essayist, reformer (1819 - 1900) Instruction does much, but encouragement does everything. Johann Wolfgang Von Goethe www.snrg-nyc.org
Re: [O] [ANN] outorg.el -- reverse Org-Babel
Samuel Wales samolog...@gmail.com writes: One suggestion: what about optionally allowing you to keep your Org notes in Org? That would allow all Org features. You'd do it by putting a specially-formatted Org ID in the comment, and then you have a key that bounces back and forth. ;;; $[id 123451243512345] Then in Org you have that ID as a property. That way you can choose whether to have your documentation in the source file using Org syntax or in Org. I'm not sure I fully understand this, but working with 'org-id' would definitely have been another option. Maybe even in combination with dynamic blocks? -- cheers, Thorsten
Re: [O] [ANN] outorg.el -- reverse Org-Babel
Alan Schmitt alan.schm...@polytechnique.org writes: 'outorg' is based on the idea that it would be nice to be able to 1. structure your source-code files like Org-mode files and use all the structure editing and navigation commands available. Does it mean it can superseed orgstruct-mode, or should one use both? 'outorg' is actually based on outline-minor-mode. Since all I wanted in the source-buffers was outline functionality (combined with full Org-mode functionality in the edit-buffers), I thought all I need is outline-minor-mode. But I will try to refactor the whole thing so that it becomes immaterial if orgstruct-mode or outline-minor-mode is used (I assume there are equivalents for 'outline-regexp' and 'outline-level' in orgstruct-mode). -- cheers, Thorsten
Re: [O] Critic markup
On 12/02/13 23:12, Alan Schmitt wrote: Hello, I just read about this nice extension to markdown syntax this morning: http://macdrifter.com/2013/02/everyones-a-critic-the-critic-markup-language-proposal.html I really like how it's minimal yet seems to fairly well address a problem in collaborative text editing. Is there something similar in orgmode? Thanks, Alan A much older suggestion for editing text which is particularly suitable for electronic text: http://www.mpi-nf.mpg.de~hitoshi/otherprojects/manued/index.shtml http://www.mpi-inf.mpg.de/~hitoshi/otherprojects/manued/FAQ.shtml And there is an emacs mode for it: manued.el Cheers, Alan -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
Re: [O] [ANN] outorg.el -- reverse Org-Babel
François Pinard pin...@iro.umontreal.ca writes: poporg has many flaws, and is surely not up to the quality of Org. Nevertheless, I much use it even if imperfect, while knowing it should be improved in many ways. same here on the outorg site, although I'm pretty sure its more alpha-stage. but since it is based on such a simple idea (- design outline-regexp and outline-level in a way that applying 'comment-region' and 'uncomment-region' to each line does the conversion job between Org and whatever programming-language syntax) I hope a few bug-fixes and improvements will move it closer towards version 1.0. If we could make something better out of two imperfections, it could be worth trying. If only I had more time! Sigh! after a quick look at your code I would say that outorg and poporg are very different beasts - the effort to merge them would probably be much higher than to bring them both (independently) to a stable usable state. I will do some major changes motivated by this threat, maybe afterwards it easier to see where the similarities and where the differences are. -- cheers, Thorsten
[O] new HTML export backend: footnote format [%s]?
Hello, I have just started using the new exporter in 7.9.3e (7.9.3e-999-ge5322) for HTML output. After applying these changes to our org files: #+style - #+html_style #+setupfile - #+include and path in our HTML output is almost back to normal. Nice work! So it seems we are already down to the more cosmetic stuff. This apparently does not have an effect any more: (setq org-export-html-footnote-format [%s]) - is there a new way to configure this format for the new export backends (we prefer [123] references to superscripted footnotes)? Many thanks in advance! Warm regards, Stefan -- Dr. Stefan Vollmar, Dipl.-Phys. Head of IT group Max-Planck-Institut für neurologische Forschung Gleuelerstr. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 Email: voll...@nf.mpg.de http://www.nf.mpg.de smime.p7s Description: S/MIME cryptographic signature
Re: [O] double-width characters in tables
Achim Gratz strom...@nexgo.de writes: Eric Abrahamsen writes: Yes, org-string-width eventually calls string-width, so that behaves correctly as far as it goes, but unfortunately that's not where the value in the text properties comes from... 《蛙》 123456 Doesn't that line up for you? Those bracket characters come with their own whitespace, maybe this is clearer: 正能量 123456 One Chinese character should definitely take up two screen columns. That's a function of the font that is ultimately used and their run-length. Since you are unlikely to use a font that has _all_ those glyphs, eventually the ones that are missing in your specified font will be replaced with the glyph corresponding to the same codepoint in a different font if it exists or possibly a composition of multiple glyphs (if not you'll get a placeholder). Thanks for all the responses here! Obviously the question is more complicated than I thought. Chinese fonts are fixed-width by default, so I assumed things would line up with a fixed-width latin font, though clearly I wasn't thinking hard enough about typefaces and their different widths/sizes. It's obvious from the screenshots that everyone's got a little something different going on. Takaaki's unicode WHITE CIRCLE is weird -- it's classified as CJK, but Chinese characters are usually named CJK IDEOGRAPH BLAH, and this isn't. It's displayed using a Chinese font on my machine, making it double-width, but sure enough `string-width' returns 1. I actually have the same problem with EM DASH here -- Inconsolata doesn't have that glyph, so a Chinese font is substituted, and I get a double-width character that reports its width as 1. Anyhoo... I still think the original problem is valid: strings in table fields should be measured with `string-width', not `length'. It might not be perfect, but surely it would be better than the present situation? On second thought I don't think it's a problem with text properties. (add-text-properties 0 6 '() 正能量) gives an Args out of range error, and it probably should, since all it cares about is the number of characters in the string. Solving the problem then might mean just using `org-string-width' directly in the code, in the places where string width is currently calculated from text property values. I'll poke at it, and see how badly I break it. Thanks again, Eric
[O] Tables in texinfo export
Aloha all, Is there a way to control column widths when exporting Org mode tables to texinfo? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
