Rasmus ras...@gmx.us writes:
Quick but unrelated question. I'm updating the Worg page and I
noticed that the customize-group for ox-koma-letter is
org-export-koma-letter. Given that other groups are org-latex and
org-html etc., should the group not be called org-koma-letter?
Yes,
Nicolas Goaziou n.goaz...@gmail.com writes:
No. Other groups are `org-export-latex', `org-export-html'...
Bastien b...@gnu.org writes:
Unless I miss something, other groups are
org-export-html
org-export-latex
etc.
so org-export-koma-letter seems right.
Right. That's a late night
Hello Rasmus,
I applied the first patch, with the following small changes.
This part would not apply:
--8---cut here---start-8---
@@ -252,7 +258,7 @@ This option can also be set with the OPTIONS keyword, e.g.:
:group 'org-export-koma-letter)
(defcustom
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello Rasmus,
I applied the first patch, with the following small changes.
Please ignore this email, there was something wrong in my setup (I was
in the maint branch ...). Sorry for the noise.
Alan
Rasmus ras...@gmx.us writes:
Alan Schmitt alan.schm...@polytechnique.org writes:
Rasmus: do you want to change these, or should I do it and apply the
patch? (The former would be simpler, I have to say.)
Attached. Sorry about the delay. They should fix Nicholas'
'concerns'.
Applied and
Hello,
Sorry for not replying earlier, I've been swamped by traveling and work.
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Rasmus ras...@gmx.us writes:
Would you give the attached patches a spin? I think they work nicely;
only the second patch is non-trivial. Basically, one can
Would you give the attached patches a spin? I think they work nicely;
only the second patch is non-trivial. Basically, one can ignore
subject and title differences as now by setting
org-koma-letter-prefer-subject to t and not use the SUBJECT keyword.
I have set the default of
Alan Schmitt alan.schm...@polytechnique.org writes:
Rasmus: do you want to change these, or should I do it and apply the
patch? (The former would be simpler, I have to say.)
Attached. Sorry about the delay. They should fix Nicholas'
'concerns'.
–Rasmus
--
Vote for proprietary math!
From
Quick but unrelated question. I'm updating the Worg page and I
noticed that the customize-group for ox-koma-letter is
org-export-koma-letter. Given that other groups are org-latex and
org-html etc., should the group not be called org-koma-letter?
–Rasmus
PS: Sorry for not starting a new
Hello,
Rasmus ras...@gmx.us writes:
Given that other groups are org-latex and
org-html etc., should the group not be called org-koma-letter?
No. Other groups are `org-export-latex', `org-export-html'...
Regards,
--
Nicolas Goaziou
Hi Rasmus,
Rasmus ras...@gmx.us writes:
Quick but unrelated question. I'm updating the Worg page and I
noticed that the customize-group for ox-koma-letter is
org-export-koma-letter. Given that other groups are org-latex and
org-html etc., should the group not be called org-koma-letter?
Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Rasmus ras...@gmx.us writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
I finally had the time to fix these old patches. Sorry about the
wait.
You should update Org first. I modified large parts of ox-koma-letter.el
recently so your
Hello,
Rasmus ras...@gmx.us writes:
Would you give the attached patches a spin? I think they work nicely;
only the second patch is non-trivial. Basically, one can ignore
subject and title differences as now by setting
org-koma-letter-prefer-subject to t and not use the SUBJECT keyword.
I
Alan,
I finally had the time to fix these old patches. Sorry about the
wait.
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello,
Attached are a couple of changes to ox-koma-letter following a recent
bug report by James.
1. Minor fixes around. The way subject-format was handled
Hello,
Rasmus ras...@gmx.us writes:
I finally had the time to fix these old patches. Sorry about the
wait.
You should update Org first. I modified large parts of ox-koma-letter.el
recently so your patches will probably not apply. Also, some parts are
not necessary anymore.
Regards,
--
Nicolas Goaziou n.goaz...@gmail.com writes:
I finally had the time to fix these old patches. Sorry about the
wait.
You should update Org first. I modified large parts of ox-koma-letter.el
recently so your patches will probably not apply. Also, some parts are
not necessary anymore.
I did.
Rasmus ras...@gmx.us writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
I finally had the time to fix these old patches. Sorry about the
wait.
You should update Org first. I modified large parts of ox-koma-letter.el
recently so your patches will probably not apply. Also, some parts are
Hi Rasmus,
ras...@gmx.us writes:
[...]
3. When studying the KOMA manual to answer James' second question I
came across the komavar title which is currently not supported. I
have added support for a separate SUBJECT keyword. The heuristic
is something like this (i) if title and
Hi all,
Attached are a couple of changes to ox-koma-letter following a recent
bug report by James.
1. Minor fixes around. The way subject-format was handled before was
ugly. Updated some docstrings etc.
2. better test of whether values have changed in the buffer. I think
Alan added
Hi,
With the following patch one can set the opening via a headline.
Currently, it's pretty conservative and will only set opening if it
isn't set already. I'm open to discussion on that point.
With this patch, the following example:
--8---cut
Hi,
Nicolas Goaziou n.goaz...@gmail.com writes:
With the following patch one can set the opening via a headline.
Currently, it's pretty conservative and will only set opening if it
isn't set already. I'm open to discussion on that point.
Here are some comments about its internals.
Nicolas Goaziou n.goaz...@gmail.com writes:
(defcustom org-koma-letter-opening nil
- Letter's opening, as a string.
+ Letter's opening, as a string. If (1) this value is nil; (2)
Please start a new line after the first sentence.
This patch changes some docstrings to make ox-koma-letter
Hi,
There's a missing backtick in a function. I could swear it used to be
there. . .
–Rasmus
--
This is the kind of tedious nonsense up with which I will not putFrom b6cdbb74fc4f2bb6d1e497a932d33c640e2f2bc1 Mon Sep 17 00:00:00 2001
From: rasmus ras...@gmx.us
Date: Fri, 26 Jul 2013 11:20:41
Rasmus ras...@gmx.us writes:
There's a missing backtick in a function. I could swear it used to be
there. . .
Applied, thanks!
--
Bastien
Hi Rasmus,
Rasmus writes:
Rasmus ras...@gmx.us writes:
Rasmus ras...@gmx.us writes:
Hi,
Some more patches that should work against the master branch.
Patch 1: bug fixes. Most notably use symbols some places rather than
strings.
Patch 2 adds support for TO and FROM headings. If
Alan Schmitt alan.schm...@polytechnique.org writes:
I applied the patches (just changing a small typo in the changelog).
Thanks, let me know if any errors pop up.
–Rasmus
--
When in doubt, do it!
Rasmus ras...@gmx.us writes:
Rasmus ras...@gmx.us writes:
Hi,
Some more patches that should work against the master branch.
Patch 1: bug fixes. Most notably use symbols some places rather than
strings.
Patch 2 adds support for TO and FROM headings. If you've got time for
testing I
Hi Rasmus,
Rasmus ras...@gmx.us writes:
* ox-koma-letter.el: If tag wasn't given a headline could cause
trouble.
* ox-koma-letter.el: bug in subject-format defcustom.
* ox-koma-letter.el: some newline changes
* ox-koma-letter.el: changed varioues quoted things to symbols.
You need to
Bastien,
* ox-koma-letter.el: If tag wasn't given a headline could cause
trouble.
* ox-koma-letter.el: bug in subject-format defcustom.
* ox-koma-letter.el: some newline changes
* ox-koma-letter.el: changed varioues (sic) quoted things to symbols.
You need to tell what functions or
Rasmus ras...@gmx.us writes:
Hi,
Some more patches that should work against the master branch.
Patch 1: bug fixes. Most notably use symbols some places rather than
strings.
Patch 2 adds support for TO and FROM headings. If you've got time for
testing I would appreciate feedback. It's
Hi,
Some more patches that should work against the master branch.
Patch 1: bug fixes. Most notably use symbols some places rather than
strings.
Patch 2 adds support for TO and FROM headings. If you've got time for
testing I would appreciate feedback. It's explained in the top of the
patch.
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
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
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
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.
Hi Rasmus,
Rasmus wrote:
Attached are three patches that goes on top of Viktor's latest patch
(I've also attached it here since I rebased stuff and might have
changed it by accident).
1. Viktor's latest patch.
2. The patch describe above that gets user name and email and works
Hi Rasmus,
Rasmus wrote:
Rasmus ras...@gmx.us writes:
4. Sets defcustom org-koma-letter-signature nil since that
corresponds to default scrlttr2 behavior anyway (p. 183 in the
manual).
Re 4.: I'd like to do something similar to
org-koma-letter-subject-format. But I'm
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
Viktor Rosenfeld listuse...@gmail.com writes:
I'm also not a big fan of the title defaulting to the filename. But I
think it is a minor issue. What I think is quite useful is setting the
subject to the headline of the exported subtree. Wouldn't we also lose
this if subject is nil?
Without
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. I had to merge in some of the changes of 0002 by hand. I
suggest that we nail down the workings of AUTHOR and EMAIL first (should
be done now)
Rasmus ras...@gmx.us writes:
4. Sets defcustom org-koma-letter-signature nil since that
corresponds to default scrlttr2 behavior anyway (p. 183 in the
manual).
Re 4.: I'd like to do something similar to
org-koma-letter-subject-format. But I'm not sure how, at the moment
Michael Strey writes:
Here is a draft proposal for a user interface using Nicola's suggestion:
I like this. About the :BODY: tag, do we really need it if it's
optional? Also, do we enfore the order: what if there is a section after
we start on the ENCL or PS tags?
Alan
Hello,
Alan Schmitt alan.schm...@polytechnique.org writes:
Michael Strey writes:
Here is a draft proposal for a user interface using Nicola's suggestion:
I like this. About the :BODY: tag, do we really need it if it's
optional? Also, do we enfore the order: what if there is a section after
Hello,
Nicolas Goaziou writes:
Headlines are also possible, with a :location: property, which could be
set to, e.g. closing. See also:
http://orgmode.org/worg/org-tutorials/org-e-groff-documentation.html
for a syntax based on headlines.
Another possibility is to use a special block.
Hello,
Alan Schmitt alan.schm...@polytechnique.org writes:
Nicolas Goaziou writes:
Headlines are also possible, with a :location: property, which could be
set to, e.g. closing. See also:
http://orgmode.org/worg/org-tutorials/org-e-groff-documentation.html
for a syntax based on
Hello,
On Mon, Mar 04, 2013 at 09:38:38PM +0100, Nicolas Goaziou wrote:
[...]
Headlines are also possible, with a :location: property, which could be
set to, e.g. closing. See also:
http://orgmode.org/worg/org-tutorials/org-e-groff-documentation.html
for a syntax based on headlines.
Michael Strey mst...@strey.biz writes:
Here is a draft proposal for a user interface using Nicola's
suggestion:
Looks nice. What happens to headlines without a tag? Would they be
read as part of the body or would untagged headliens just be ignored?
–Rasmus
--
This is the kind of tedious
On Tue, Mar 05, 2013 at 01:23:40PM +0100, Rasmus wrote:
[...]
What happens to headlines without a tag? Would they be
read as part of the body or would untagged headliens just be ignored?
Untagged sections shall be treated as body.
Updated proposal:
#+BEGIN_SRC org
#+LATEX_CLASS: letter
Hello,
Alan Schmitt alan.schm...@polytechnique.org writes:
So I guess the only part of the letter design I'm worried about is
having a 'ps' with several paragraphs. (I guess it's related to the footnote
with multiple paragraphs questions, but I guess the two blank lines
approach is only for
Nicolas Goaziou writes:
Hello,
Alan Schmitt alan.schm...@polytechnique.org writes:
So I guess the only part of the letter design I'm worried about is
having a 'ps' with several paragraphs. (I guess it's related to the footnote
with multiple paragraphs questions, but I guess the two blank
Alan Schmitt alan.schm...@polytechnique.org writes:
#+AFTER_CLOSING: text that goes after closing, such as \ps{my ps}
What worries me about this is that we'll probably want something with
paragraphs. Is it possible? If not, could the approach taken with
footnotes be also allowed here?
With
Hi Alan,
On Mon, Mar 04, 2013 at 08:19:58AM +0100, Alan Schmitt wrote:
[...]
So I guess the only part of the letter design I'm worried about is
having a 'ps' with several paragraphs.
The option below makes an opening with two paragraphs.
#+BEGIN_SRC org
#+OPENING: Sehr geehrter Herr
Michael Strey writes:
Hi Alan,
On Mon, Mar 04, 2013 at 08:19:58AM +0100, Alan Schmitt wrote:
[...]
So I guess the only part of the letter design I'm worried about is
having a 'ps' with several paragraphs.
The option below makes an opening with two paragraphs.
#+BEGIN_SRC org
Hello,
Rasmus ras...@gmx.us writes:
Alan Schmitt alan.schm...@polytechnique.org writes:
#+AFTER_CLOSING: text that goes after closing, such as \ps{my ps}
What worries me about this is that we'll probably want something with
paragraphs. Is it possible? If not, could the approach taken with
Michael Strey mst...@strey.biz writes:
So where is the problem with PS?
BTW: Do you use PS in printed letters?
Yes. Recently: PS: If you need to contact me via snail mail in
country X do send it to this C/O-address
–Rasmus
--
Powered by magic pixies!
Rasmus writes:
Export the following to LaTeX:
#+BEGIN_SRC Org
#+TITLE:test
#+LATEX_HEADER:\newcommand{test}{\textsc{ps}:this is a test}
#+LATEX_HEADER:\newcommand{ttest}{\textsc{ps}\:this is a test}
#+LATEX_HEADER:\newcommand{tttest}{\textsc{ps}\\:this is a test}
Hello,
Alan Schmitt alan.schm...@polytechnique.org writes:
Rasmus writes:
Export the following to LaTeX:
#+BEGIN_SRC Org
#+TITLE:test
#+LATEX_HEADER:\newcommand{test}{\textsc{ps}:this is a test}
#+LATEX_HEADER:\newcommand{ttest}{\textsc{ps}\:this is a test}
Hi Nicolas,
Nicolas Goaziou writes:
Hello,
Alan Schmitt alan.schm...@polytechnique.org writes:
Rasmus writes:
Export the following to LaTeX:
#+BEGIN_SRC Org
#+TITLE:test
#+LATEX_HEADER:\newcommand{test}{\textsc{ps}:this is a test}
#+LATEX_HEADER:\newcommand{ttest}{\textsc{ps}\:this
Hi Alan,
Alan Schmitt alan.schm...@polytechnique.org writes:
To give you an idea of my setup, here it is.
This is nice -- would you share it on Worg?
Thanks!
--
Bastien
Bastien writes:
Hi Alan,
Alan Schmitt alan.schm...@polytechnique.org writes:
To give you an idea of my setup, here it is.
This is nice -- would you share it on Worg?
Sure. Should it go there :
http://orgmode.org/worg/exporters/index.html ?
I'll send you my ssh key.
Alan
Michael Strey mst...@strey.biz writes: Rasmus,
In fact to use the scrlttr2 support in Org I had to adjust a LCO files
because it's currently loaded after LATEX_HEADER arguments (so all
customization was overwritten). I didn't like that.
After this remark I checked my changes and compared
Alan Schmitt alan.schm...@polytechnique.org writes:
Michael Strey mst...@strey.biz writes: Rasmus,
In fact to use the scrlttr2 support in Org I had to adjust a LCO files
because it's currently loaded after LATEX_HEADER arguments (so all
customization was overwritten). I didn't like that.
Alan Schmitt alan.schm...@polytechnique.org writes:
As the order matters, as said in some replies, I prefer the
AFTER_CLOSING approach.
How can one use the a `:' in a AFTER_CLOSEing?
I rely on an lco for that. To give you an idea of my setup, here it is.
I found that with this setup I can
Hi Alan,
Alan Schmitt alan.schm...@polytechnique.org writes:
Bastien writes:
Hi Alan,
Alan Schmitt alan.schm...@polytechnique.org writes:
To give you an idea of my setup, here it is.
This is nice -- would you share it on Worg?
Sure. Should it go there :
Rasmus writes:
Alan Schmitt alan.schm...@polytechnique.org writes:
As the order matters, as said in some replies, I prefer the
AFTER_CLOSING approach.
How can one use the a `:' in a AFTER_CLOSEing?
Sorry, I don't know. I thought it was the approach you were suggesting.
I rely on an
Alan Schmitt alan.schm...@polytechnique.org writes:
Rasmus writes:
Alan Schmitt alan.schm...@polytechnique.org writes:
As the order matters, as said in some replies, I prefer the
AFTER_CLOSING approach.
How can one use the a `:' in a AFTER_CLOSEing?
Sorry, I don't know. I thought it
Hi,
Sorry for not replying earlier, I've been in a mode where I let my
orgmode mail accumulate.
Rasmus writes:
I have changed the following objects:
1. Make keys sane; no reason why open pdf is O rather than o and why
k is used in place of l (as in the tex exporter).
Yes, it's nice
Rasmus,
On Wed, Feb 27, 2013 at 01:13:25PM +0100, Rasmus wrote:
[...]
In fact to use the scrlttr2 support in Org I had to adjust a LCO files
because it's currently loaded after LATEX_HEADER arguments (so all
customization was overwritten). I didn't like that.
After this remark I checked my
On Tue, Feb 26, 2013 at 10:14:28PM +0100, Rasmus wrote:
[...]
Wouldn't it be better to use Markus Kohm's concept of letter class
options to set all the static stuff?
Potentially. What do you mean by letter class options? Are you
referring to customized LCO files or do you refer to e.g.
Michael,
I mean customized LCO files. For my former company I had made a
letter class for business letters based on scrlttr2.cls with two LCO
files. the first LCO file *company.lco* contained the general
information about the company (address, bank account, etc.). A
second LCO file
Hi,
Rasmus wrote:
Maybe we should write a user guide *before* further implementation
steps.
I agree. A question zero is whether we eventually want to have an
org-letter which could, in principle, output to something different
than scrlttr2.
That could be isodoc for which I have a bit of
Sebastien Vauban
wxhgmqzgw...@spammotel.com writes:
Hi,
Rasmus wrote:
Maybe we should write a user guide *before* further implementation
steps.
I agree. A question zero is whether we eventually want to have an
org-letter which could, in principle, output to something different
than
Hi Rasmus,
Rasmus ras...@gmx.us writes:
I have been working on extending the KOMA letter support in Org. The
backend is still rough and I would like to more stuff such as
designing firstfood and firsthead with org elements (e.g. I use a
tabularx for my firstfood with varioues stuff).
Bastien b...@altern.org writes:
I have been working on extending the KOMA letter support in Org. The
backend is still rough and I would like to more stuff such as
designing firstfood and firsthead with org elements (e.g. I use a
tabularx for my firstfood with varioues stuff).
Thanks for
I have been working on extending the KOMA letter support in Org. The
backend is still rough and I would like to more stuff such as
designing firstfood and firsthead with org elements (e.g. I use a
tabularx for my firstfood with varioues stuff).
I have changed the following objects:
Hi,
I have been working on extending the KOMA letter support in Org. The
backend is still rough and I would like to more stuff such as
designing firstfood and firsthead with org elements (e.g. I use a
tabularx for my firstfood with varioues stuff).
I have changed the following objects:
1.
76 matches
Mail list logo
