On 4/30/10 Apr 30 -10:28 AM, Carsten Dominik wrote:
> Hi everyone,
>
> when this discussion is settled, can someone please summarize it for me
> and send me the patch everyone agrees on?
Will do.
Best,
r
>
> Thanks.
>
> - Carsten
>
> On Apr 30, 2010, at 5:15 PM, Robert Goldman wrote:
>
>> T
Hi everyone,
when this discussion is settled, can someone please summarize it for
me and send me the patch everyone agrees on?
Thanks.
- Carsten
On Apr 30, 2010, at 5:15 PM, Robert Goldman wrote:
That's an excellent idea. I will try to revise accordingly.
In my copious free time! :-)
"W
That's an excellent idea. I will try to revise accordingly.
In my copious free time! :-)
"Wes Hardaker" wrote:
>> On Thu, 29 Apr 2010 10:00:43 -0500, Robert Goldman
>> said:
>
>RG> So what I wanted here was newlines /only/ where the paragraphs
>RG> break.
>
>The other potentially bet
> On Thu, 29 Apr 2010 10:00:43 -0500, Robert Goldman
> said:
RG> So what I wanted here was newlines /only/ where the paragraphs
RG> break.
The other potentially better thing to do then is rather than use a
boolean "add-newline" type variable, instead add a more generic
"insert-after-par
Robert Goldman writes:
> A quick follow-up --- I got into trouble by sending patches computed
> versus origin/master. It turns out that this is not what I (or anyone
> else, I would have thought) wants. What I want is to get patches
> relative to the merge commit that brings together my local c
On 4/29/10 Apr 29 -12:00 PM, Bernt Hansen wrote:
> Robert Goldman writes:
>
>> On 4/29/10 Apr 29 -8:58 AM, Carsten Dominik wrote:
>>> Applied, thanks.
>>>
>>> I had two email saying patch 4/4, I too one of them, what happened with
>>> 1/4, 2/4, 3/4?
>>
>> What happened was that I am incompetent w
Robert Goldman writes:
> On 4/29/10 Apr 29 -8:58 AM, Carsten Dominik wrote:
>> Applied, thanks.
>>
>> I had two email saying patch 4/4, I too one of them, what happened with
>> 1/4, 2/4, 3/4?
>
> What happened was that I am incompetent with git. Somehow git thinks
> that my copy is four patches
On 4/29/10 Apr 29 -8:58 AM, Carsten Dominik wrote:
> Applied, thanks.
>
> I had two email saying patch 4/4, I too one of them, what happened with
> 1/4, 2/4, 3/4?
What happened was that I am incompetent with git. Somehow git thinks
that my copy is four patches away from origin/master. But, in f
On 4/29/10 Apr 29 -8:54 AM, Wes Hardaker wrote:
>> On Wed, 28 Apr 2010 16:39:59 -0500, "Robert P. Goldman"
>> said:
>
> RPG> Added a handler for blockquotes.
>
> That looks great. Thanks!
>
> RPG> Also added :body-newline-paragraph to the org-set-generic-type.
>
> I'm fine with that
Applied, thanks.
I had two email saying patch 4/4, I too one of them, what happened
with 1/4, 2/4, 3/4?
Please verify that this went well.
Thanks!
- Carsten
On Apr 29, 2010, at 3:54 PM, Wes Hardaker wrote:
On Wed, 28 Apr 2010 16:39:59 -0500, "Robert P. Goldman" > said:
RPG> Added a hand
> On Wed, 28 Apr 2010 16:39:59 -0500, "Robert P. Goldman"
> said:
RPG> Added a handler for blockquotes.
That looks great. Thanks!
RPG> Also added :body-newline-paragraph to the org-set-generic-type.
I'm fine with that too, but in the end couldn't you just put a "\n" in
the format str
From: Robert P. Goldman
Added a handler for blockquotes.
Also added :body-newline-paragraph to the org-set-generic-type. This is
intended to help handling output formats (like tikiwiki) where newlines are
treated as paragraph separators, instead of being used to fill (i.e., the
destination is e
12 matches
Mail list logo
