Re: [O] [PATCH][ox-koma-letter]: sender, email and cleanup
Rasmus writes:
Viktor,
1. Viktor's latest patch.
2. The patch describe above that gets user name and email and works
on my system. . .
Your code works for me. From my point of view, the pros are that per
default `org-koma-letter-{author,sender}' pick up the values of
`user-full-name' and `user-mail-address' whenever they are changed.
That's very nice! The cons are that IHMO it's quite complicated for
setting something as simple as author and email and you mentioned a
possible crash which I did not test further. Could this be tested using
`functionp'? Still, I think we should stick with it for now.
functionp seems better, yes. I didn't know about it (doh!). Thanks!
While it is complicated I think it's OK given our desire to disable
author and still have a similar default to ox-latex.el. Also, it
allows for arbitrary functions which could potentially determine the
name based on the context of the letter (I don't know since it's
already initialized in the options-alist).
I'll let you and Alan decide.
I like this approach.
As a side note, I had quite a few problems working with your patches.
None of them applied against master, or against my latest patch as you
claimed.
Right. I was working off of branch and I guess one reasons is that it
was against the history of my previoues patches—of which not all was
applied to the master, it seems (?). I've now tried to rework the
entire thing against the current master and produces simplified
patches. I tested them with git am and they work on my system.
There are still things I don't understand such as why git wants to
re-add the authors in patch 4 but I've spend way to much time on
rebasing and understanding git already and my head hurts. It seems to
ignore it when using git am.
Before applying the patches my git log says
commit 847637f4bdacb861723438c1389f1a3bcdac48af
Merge: 43cc5be 206762b
Author: Nicolas Goaziou n.goaz...@gmail.com
Date: Sat May 25 22:03:48 2013 +0200
Merge branch 'maint'
Patches:
1. summarizes all changes in author. It uses my solution as mentioned above.
2. full support for after closing keywords. See commit message
3. signature to nil
4. change handling of subject and allow for setting subject in
OPTION-line.
I'm going to apply the patches. Thanks to both of you for the nice work!
Alan
Re: [O] Starting emacs followed directly by org-agenda search and visiting file removes color formatting
Hi Rainer, Rainer Stengele rainer.steng...@online.de writes: any chance to get that bug resolved? I did not upgrade org since the commit introducing it. Yes, it is on top of my list, I was away from computer for a while, but I'll tackle this ASAP. -- Bastien
Re: [O] GFDL
Hi Ben, Ben Finney ben+em...@benfinney.id.au writes: Do you have a reference from some FSF official for that restriction? See this discussion: http://lists.gnu.org/archive/html/emacs-devel/2012-12/msg00375.html Also, when RMS discovered that the Org manual was published by http://www.network-theory.co.uk he asked for details on the publication -- I said it was none of my business and redirected him to Brian Gough, who led this publication effort with Carsten. I don't know what is the output of the conversion he may have had with Brian. Maybe RMS wanted the FSF to publish the manual. HTH, -- Bastien
Re: [O] [PATCH][ox-koma-letter]: sender, email and cleanup
Hi Xavier,
1. summarizes all changes in author. It uses my solution as mentioned
above.
2. full support for after closing keywords. See commit message
3. signature to nil
4. change handling of subject and allow for setting subject in
OPTION-line.
I'm going to apply the patches. Thanks to both of you for the nice work!
I just update Org/git and install ox-koma-letter lisp file. I have a
strange behavior with EMAIL keyword since there will be always a
=\setkomavar{fromemail}= command in my LaTeX produced file even if
there is no #+EMAIL: keyword on top of my org file. This is slightly
different from what I get when I write or not #+AUTHOR: keyword : the
=\setkomavar{fromname}= naturally disappears if AUTHOR is not written.
Thanks for the quick report, and sorry about the inconvenience.
I'm kind of busy this week due to obligations which I must attend to.
Could you perhaps set the offending variable to nil for now? Either
org-koma-letter-email or the org-koma-letter-use-email or use
#+OPTIONS: email:nil.
I couldn't see what would be causing the offending behavior straight
away. Could you give me an example-file where the behavior fails?
Then I'd also be able to test that future changes don't break expected
behavior.
Also, if time permits please do look over the (hopefully) elaborate
changelogs and test that everything works as you expect it to.
I do not want to write every time my email in org file header since it
is already set in a lco file. But given this problem, the email is
always overloaded when exporting to latex/pdf.
If you always have an email in you lco file you should disable email
publishing.
Cheers,
Rasmus
--
⠠⠵
Re: [O] Status fix for Regression in fill-paragraph behavior?
Nicolas Goaziou wrote: Also, you have to admit that Org is a bit more complex than Text mode (or Fundamental mode), and may have different requirements. It sure is a great tool, with a lot of useful functionality. But the new paragraph fill breaks my old workflows, so I am trying to find a way around that (preferably the easiest ;-). Is there some way or setting to tell org that in a node or perhaps all nodes in a subtree it should apply the adaptive fill from fill.el to text paragraphs, so that the fill-prefix is automatically recognized like in fundamental and text mode? Or is there some function that I can call (and bind to some key combination) to apply the old paragraph fill to some text paragraph? So that plain text paragraphs and citations that don't use any org features can be filled in the old way. Again, what you call standard Adaptive Fill is not standard, since it depends on the major mode. The word standard was meant in the following sense: Adaptive Fill that automatically recognizes a fill-prefix is available and enabled by default in the basic text editing modes of Emacs like fundamental-mode and text-mode. I think external packages (filladapt.el?) might provide the functionality you're after, assuming you configure them to play nicely with Org. The org manual says Many users reported they had problems using both 'filladapt.el' and Org mode, so I'm not very enthusiastic about embarking on that route. Regards, Peter Wagemans
Re: [O] Status fix for Regression in fill-paragraph behavior?
Hello Peter, On Mon, May 27, 2013 at 01:03:41PM +0200, Wagemans, Peter wrote: Nicolas Goaziou wrote: Also, you have to admit that Org is a bit more complex than Text mode (or Fundamental mode), and may have different requirements. It sure is a great tool, with a lot of useful functionality. But the new paragraph fill breaks my old workflows, so I am trying to find a way around that (preferably the easiest ;-). Is there some way or setting to tell org that in a node or perhaps all nodes in a subtree it should apply the adaptive fill from fill.el to text paragraphs, so that the fill-prefix is automatically recognized like in fundamental and text mode? Or is there some function that I can call (and bind to some key combination) to apply the old paragraph fill to some text paragraph? So that plain text paragraphs and citations that don't use any org features can be filled in the old way. Untested idea: you could adapt org-fill-paragraph to suit your needs and call the custom fill function when you need it. Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] Indentation of code blocks within lists
Hello Nicolas, Nicolas Goaziou wrote: Sebastien Vauban writes: Indeed. I have as well `org-src-preserve-indentation' set to `t', for the same reason as pointed out: if I don't use it that way, then my code blocks which have different relative depths are exported (in HTML) on the same level, as if there was no indentation to respect. So, yes, it does work if you don't need to preserve indentation, you're well right. But, if not, the indentation is lost on export (and on source editing with C-c '). I have pushed a fix on maint (at least for the export part, the source editing one is another story). Could you confirm it behaves as expected? I confirm that the export is respecting the indentation up to the virtual margin (represented by the # character). Excellentissimo! Thank you ve-ry much... Best regards, Seb -- Sebastien Vauban
Re: [O] Indentation of code blocks within lists
Nicolas, Sebastien Vauban wrote: Nicolas Goaziou wrote: Sebastien Vauban writes: Indeed. I have as well `org-src-preserve-indentation' set to `t', for the same reason as pointed out: if I don't use it that way, then my code blocks which have different relative depths are exported (in HTML) on the same level, as if there was no indentation to respect. So, yes, it does work if you don't need to preserve indentation, you're well right. But, if not, the indentation is lost on export (and on source editing with C-c '). I have pushed a fix on maint (at least for the export part, the source editing one is another story). Could you confirm it behaves as expected? I confirm that the export is respecting the indentation up to the virtual margin (represented by the # character). Excellentissimo! I wanted to add that I tested your patch against my LP'ed .emacs file (~10K lines)... which was then some sort of baptism of fire for it... Best regards, Seb -- Sebastien Vauban
[O] Only first time stamp per event on agenda (containing multiple time stamps)
Hi! (My current Org-mode is git 86fab4ce354c3fc29a9a169add80a) When I have a heading like following, the event appears on my agenda on Monday and on Wednesday with their time frames (as expected by me): ,[ time stamps on different days ] | ** Event A | | - 2013-05-27 Mon 09:00-12:00 | - 2013-05-29 Wed 13:00-16:00 ` However, with the following event, I only get one time stamp onto my agenda (namely the first one of the very same day): ,[ time stamp on the same day ] | ** Event B | | - 2013-05-27 Mon 09:00-12:00 | - 2013-05-27 Mon 13:00-16:00 ` If this is not intended behavior, I beg to fix it ;-) I do have use-cases [1] where this kind of list is way better than each time-stamp as its own heading. If this is intended behavior, I am curious about the reason why. Thank you in any case :-) 1. e.g., for irregular occurring courses sharing the same heading title. -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: get Memacs from https://github.com/novoid/Memacs https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
[O] org-effectiveness
Hello, I would like propose org-effectiveness to contrib. Org effectiveness is a mode to measure the personal effectiveness using org todos. Regards.
Re: [O] [PATCH][ox-koma-letter]: sender, email and cleanup
Hi Xavier,
Xavier Garrido wrote:
Hi koma-letterers,
Patches:
1. summarizes all changes in author. It uses my solution as mentioned
above.
2. full support for after closing keywords. See commit message
3. signature to nil
4. change handling of subject and allow for setting subject in
OPTION-line.
I'm going to apply the patches. Thanks to both of you for the nice work!
I just update Org/git and install ox-koma-letter lisp file. I have a
strange behavior with EMAIL keyword since there will be always a
=\setkomavar{fromemail}= command in my LaTeX produced file even if
there is no #+EMAIL: keyword on top of my org file. This is slightly
different from what I get when I write or not #+AUTHOR: keyword : the
=\setkomavar{fromname}= naturally disappears if AUTHOR is not
written.
I do not want to write every time my email in org file header since
it is already set in a lco file. But given this problem, the email is
always overloaded when exporting to latex/pdf.
Please check the values of `org-koma-letter-email' and
`org-koma-letter-author'. They should be set to nil if you have these
settings defined in an LCO file and do not want to set them in the
generated TeX sources. I use such a setup and the latest master branch
is working for me.
Cheers,
Viktor
I had a look into ox-koma-letter script and even if I saw small
differences when dealing with AUTHOR and EMAIL keywords, I am not
able to solve solve this discrepancy.
Xavier
PS: except from this little problem, it works like a charm, so thanks a lot.
Re: [O] org-effectiveness
davi...@es.gnu.org (David Arroyo =?utf-8?Q?Men=C3=A9ndez?=) writes: Hello, I would like propose org-effectiveness to contrib. Org effectiveness is a mode to measure the personal effectiveness using org todos. Regards. I've wrote a tutorial: http://orgmode.org/worg/org-tutorials/org-effectiveness.html Regards.
Re: [O] org-effectiveness
Hello, David Arroyo Menéndez wrote: Hello, I would like propose org-effectiveness to contrib. Org effectiveness is a mode to measure the personal effectiveness using org todos. +1 It should use `org-time-clocksum-use-effort-durations'. I definitely like when my weekly clock report tells me that I've worked more than seven days the past week. Awesome! Cheers, Viktor Regards.
[O] change styling in code block HTML export?
When I export an org-mode file to HTML, my code blocks don't have curly quotes and don't convert --- to —. I know this is by design but I want to change it. I have (setq org-export-with-smart-quotes t) set in my .emacs, which works correctly in the rest of my exported document—but code blocks receive their own styling. Can I change the export styling of my code blocks so that they do observe curly quotes and em dashes? In fact, is there a way to disable the switch that makes code blocks into code blocks, so I can just style them manually using CSS to my liking on HTML export? Thanks!
Re: [O] LaTeX minted --shell-escape error after updating to 8.0.3
On Sat, May 25, 2013 at 11:44 PM, Nick Dokos ndo...@gmail.com wrote:
Senthil Kumar M senthil.deb...@gmail.com writes:
I updated org-mode to 8.0.3 (release_8.0.3-156-g847637). I got the
following error while using the LaTeX export, before the update all
was well and the PDF file was produced fine.
Process completed with errors: [LaTeX error] [package error]
*Org PDF LaTeX Output* shows:
...
...
Package ifplatform Warning:
shell escape is disabled, so I can only detect \ifwindows.
))
! Package minted Error: You must invoke LaTeX with the -shell-escape flag.
See the minted package documentation for explanation.
Type H return for immediate help.
...
l.21 \usemintedstyle
{autumn}
! Package minted Error: You must have `pygmentize' installed to use this
packag
e.
See the minted package documentation for explanation.
Type H return for immediate help.
...
...
I have not changed any settings in my .emacs file (i.e.: (setq
org-export-latex-listings 'minted) is unchanged) and I never faced any
problems related to the `--shell-escape' before the update. pygmentize
is present in /usr/bin/ and it too worked perfectly before the update.
Well, you must have done something before to get around this problem.
My guess would be that you have customized the old
org-latex-to-pdf-process variable. The problem is that in 8.x, the
variable has been renamed to org-latex-pdf-process, so you need to do
to the new variable what you did to the old. E.g. the default setting
of this variable is three pdflatex calls:
,
| (pdflatex -interaction nonstopmode -output-directory %o %f
| pdflatex -interaction nonstopmode -output-directory %o %f
| pdflatex -interaction nonstopmode -output-directory %o %f)
`
You'd need to add --shell-escape to each one.
--
Nick
Hi,
Nick, thank you. Setting the org-latex-pdf-process variable as you
suggested resolved the LaTeX error during the export step.
However, the minted syntax colour highlighting does not work as
expected, all python/bash/XML code appear in one colour (black).
I had included (setq org-export-latex-listings 'minted) in my .emacs
file and it worked fine before the upgrade to 8.0.3.
Is there any variable that had changed and need to be set for the
syntax highlighting to work properly?
Thank you,
Sincerely,
Senthil
-/
For I am Vader, Darth Vader, Lord Vader. I can kill you with a single
thought. Well, you'll still need a tray. No, I will not need a
tray. I do not need a tray to kill you. I can kill you without a tray,
with the power of the Force, which is strong within me. Even though I
could kill you with a tray if I so wished, for I would hack at your
neck with the thin bit until the blood flowed across the canteen
floor. No, the food is hot. You'll need a tray to put the food on.
Oh, I see, the food is hot. I'm sorry, I did not realize.
--- Eddie Izzard
Re: [O] LaTeX minted --shell-escape error after updating to 8.0.3
Senthil Kumar M senthil.deb...@gmail.com writes: Nick, thank you. Setting the org-latex-pdf-process variable as you suggested resolved the LaTeX error during the export step. However, the minted syntax colour highlighting does not work as expected, all python/bash/XML code appear in one colour (black). Just to make sure: you export to latex, open the resulting PDF file and there is no syntax highlighting? I had included (setq org-export-latex-listings 'minted) in my .emacs file and it worked fine before the upgrade to 8.0.3. Is there any variable that had changed and need to be set for the syntax highlighting to work properly? I don't think so. My guess is that your minted/pygments installation is broken, i.e. nothing to do with org. What happens if you leave org out of the equation altogether? I.e. take a simple tex file using minted and pass it through ``pdflatex --shell-escap''? -- Nick
Re: [O] Only first time stamp per event on agenda (containing multiple time stamps)
Karl Voit devn...@karl-voit.at writes: However, with the following event, I only get one time stamp onto my agenda (namely the first one of the very same day): ,[ time stamp on the same day ] | ** Event B | | - 2013-05-27 Mon 09:00-12:00 | - 2013-05-27 Mon 13:00-16:00 ` If this is not intended behavior, I beg to fix it ;-) What is the value of org-agenda-skip-additional-timestamps-same-entry? When this variable is set to nil (the default value), I find that all entries appear in the agenda: , | Day-agenda (W22): | Monday 27 May 2013 W22 |8:00.. | inbox: 9:00-12:00 Event B | 10:00.. | 12:00.. | inbox: 13:00-16:00 Event B | 14:00.. | 15:23.. You are here - - - - - - - - - - - - - - - - - - - - - | 16:00.. | 18:00.. | 20:00.. ` Best, Matt
Re: [O] org-effectiveness
Viktor Rosenfeld listuse...@gmail.com writes: Hello, David Arroyo Menéndez wrote: Hello, I would like propose org-effectiveness to contrib. Org effectiveness is a mode to measure the personal effectiveness using org todos. +1 :-) Just a tutorial: http://orgmode.org/worg/org-tutorials/org-effectiveness.html It should use `org-time-clocksum-use-effort-durations'. I definitely like when my weekly clock report tells me that I've worked more than seven days the past week. Awesome! Cheers, Viktor Regards.
Re: [O] LaTeX minted --shell-escape error after updating to 8.0.3
On Mon, May 27, 2013 at 04:17:07PM -0400, Nick Dokos wrote: Senthil Kumar M senthil.deb...@gmail.com writes: I had included (setq org-export-latex-listings 'minted) in my .emacs file and it worked fine before the upgrade to 8.0.3. Is there any variable that had changed and need to be set for the syntax highlighting to work properly? It should be org-latex-listings. See the Org 8.0 upgrade guide. http://orgmode.org/worg/org-8.0.html#sec-4 Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] [PATCH][ox-koma-letter]: sender, email and cleanup
Hi Viktor, Please check the values of `org-koma-letter-email' and `org-koma-letter-author'. They should be set to nil if you have these settings defined in an LCO file and do not want to set them in the generated TeX sources. I use such a setup and the latest master branch is working for me. Ok these are working. Thanks for your help, Cheers, Xavier
Re: [O] LaTeX minted --shell-escape error after updating to 8.0.3
On Mon, May 27, 2013 at 1:17 PM, Nick Dokos ndo...@gmail.com wrote: Senthil Kumar M senthil.deb...@gmail.com writes: Nick, thank you. Setting the org-latex-pdf-process variable as you suggested resolved the LaTeX error during the export step. However, the minted syntax colour highlighting does not work as expected, all python/bash/XML code appear in one colour (black). Just to make sure: you export to latex, open the resulting PDF file and there is no syntax highlighting? Yes. I had included (setq org-export-latex-listings 'minted) in my .emacs file and it worked fine before the upgrade to 8.0.3. Is there any variable that had changed and need to be set for the syntax highlighting to work properly? I don't think so. My guess is that your minted/pygments installation is broken, i.e. nothing to do with org. What happens if you leave org out of the equation altogether? I.e. take a simple tex file using minted and pass it through ``pdflatex --shell-escap''? -- Nick If I run pdflatex --shell-escape foo.tex on the terminal, it gives the same result (i.e. no colour highlighting). While writing this reply, I saw the email from Suvayu Ali, about changing org-export-latex-listings to org-latex-listings. That solved this issue! Thank you, Sincerely, Senthil
Re: [O] LaTeX minted --shell-escape error after updating to 8.0.3
Senthil Kumar M senthil.deb...@gmail.com writes: Is there any variable that had changed and need to be set for the syntax highlighting to work properly? I don't think so. My guess is that your minted/pygments installation is broken, i.e. nothing to do with org. What happens if you leave org out of the equation altogether? I.e. take a simple tex file using minted and pass it through ``pdflatex --shell-escap''? If I run pdflatex --shell-escape foo.tex on the terminal, it gives the same result (i.e. no colour highlighting). [Given Suvayu's answer, the following is irrelevant to this case. Nevertheless, these are basic things that one should do when something goes wrong, which is why I'm following up.]] Was foo.tex what org produced or did you create it by hand? If the former, did you look at foo.tex? Did it contain a minted environment? While writing this reply, I saw the email from Suvayu Ali, about changing org-export-latex-listings to org-latex-listings. That solved this issue! Yup, I saw it too and kicked myself! -- Nick
[O] [Feature Request] - Furigana - Yomigana - Ruby
Hi,
So this is my first try to post to the mailing list. I Love Orgmode, you
guys are the best!
I would like to use orgmode to capture japanese text to later export to
latex, html and epub.
For japanese symbols, sometimes the pronounciation is put in smaller
letters above the symbol to help the reader.
These are called ruby in general in typesetting (in japanese, they are
also called furigana/yomigana, which I put in the header so not
everybody thinks of the programming language..)
http://en.wikipedia.org/wiki/Furigana
In Latex, using CJK and ruby packages, This exports ok.
(A problem being that japanese text in headers doesn't. But i guess
that's another (and rather Latex, not orgmode-specific) topic.
Now, my feature request would be to make the html exporter interpret the
latex command
\ruby{symbol}{reading}
as:
ruby symbol rp(/rprtreading/rtrp)/rp \ruby
as suggested here, for parentheses on non-ruby supporting browsers:
http://xahlee.info/js/html5_ruby_tag.html
For the org-mode file (you might see some blank squares if you have no
japanese support):
Here a minimal working example for export:
###
#+LATEX_HEADER: \usepackage[CJK, overlap]{ruby}
#+LATEX_HEADER: \usepackage{CJK} \end{CJK}
#+LATEX \begin{CJK}{UTF8}{min}
\ruby{東}{ひがし}アジア means east asia in japanese
#+LATEX \end{CJK}
###
All the best, and keep on rocking my world in plain text! =)
[O] Bug in org-table-convert-region?
Hi List, using 'M-: (org-table-convert-region beg end 2) on this output (with beg/end being the points before and after the tabular data) ,--- | === Error on training data === | | Correctly Classified Instances 147 98 % | Incorrectly Classified Instances 32 % | Kappa statistic 0.97 | Mean absolute error 0.0233 | Root mean squared error 0.108 | Relative absolute error 5.2482 % | Root relative squared error 22.9089 % | Total Number of Instances 150 `--- I get what I want: | Correctly Classified Instances | 144 | 96 | % | | Incorrectly Classified Instances | 6 | 4 | % | | Kappa statistic | 0.94 || | | Mean absolute error | 0.035 || | | Root mean squared error |0.1586 || | | Relative absolute error | 7.8705 % || | | Root relative squared error | 33.6353 % || | | Total Number of Instances| 150 || | However, using 'C-u 2 M-x org-table-convert-region' on the marked region yields this: | Correctly | Classified | Instances | 144 | 96 | % | | Incorrectly | Classified | Instances | 6 | 4 | % | | Kappa | statistic | 0.94 | | | | | Mean| absolute | error | 0.035 | | | | Root| mean | squared | error | 0.1586 | | | Relative| absolute | error |7.8705 | % | | | Root| relative | squared | error | 33.6353 | % | | Total | Number | of| Instances | 150 | | From the comment-string: ,--- | (org-table-convert-region BEG0 END0 optional SEPARATOR) | | Convert region to a table.[...] | SEPARATOR specifies the field separator in the lines. It can have the | following values: | | '(4) Use the comma as a field separator | '(16)Use a TAB as field separator | integer When a number, use that many spaces as field separator | nil When nil, the command tries to be smart and figure out the `--- and from the elisp manual: ,--- | Here are the results of calling display-prefix with various raw prefix | arguments: | | C-u M-x display-prefix -| (4) | | C-u C-u M-x display-prefix -| (16) | | C-u 3 M-x display-prefix -| 3 `--- Looks like a bug in the argument handling? -- cheers, Thorsten
Re: [O] Org as a static site generator
Bastien b...@gnu.org writes: Oh, nice! I added a pointer in Worg: http://orgmode.org/worg/org-tools/index.html At the end of that page, there is: See the page Org Blogs and Wikis., with Org Blogs and Wikis clickable. However, the pointer resolves to file:///home/emacs/install/git/worg/org-blog-wiki.html. Some http://; was likely intended there? François
[O] Org-mode won't let me export via markdown
First, thanks to everyone who contributes to org-mode. I find it very useful. When I select export as markdown, I get an error: Quit [2 times] not: Wrong type argument: stringp, nil I've posted a backtrace in the debugger to here: http://pastebin.com/UAAund8M Emacs: 24.3.50.1 Org-mode: 8.0.3 I've edited my .emacs appropriately to load the md exporter backend. As a sidenote, it would be nice to put into the documentation that there needs to be some configuration to get markdown export to work. I was confused for a while why I didn't see the markdown options.
