Looks cool. I already opened one issue on github. :-)
-Ivan
On Oct 31, 2013, at 10:00 PM, Matt Price wrote:
> I have just pushed a more-or-less-working version of my "Org Writer's
> Room" mode to github:
>
> https://github.com/titaniumbones/org-writers-room
>
> It's a very simple set of mos
Matt Price writes:
> I have just pushed a more-or-less-working version of my "Org Writer's
> Room" mode to github:
>
> PS, the readme on github is a little out of date, but the code itself
> is mostly documented so I hope that helps. Though there's no general
> documentation at the top of the f
I'm really sorry I didn't reply sooner. I was out of town, and then I forgot
to follow up.
On Oct 27, 2013, at 2:07 AM, Alan Schmitt
wrote:
> Hi Ivan,
>
> darthand...@gmail.com writes:
>
>> Very interesting! I have been working on a mode which gives the
>> current word-count, WPM and an est
Maybe there is something obvious I'm missing, but I'm having considerable
trouble using org-language source code blocks in Beamer export.
The objective is to show a little of the org code that made the
presentation. This means including some headers. I had thought that
declaring the source cod
Anders Johansson writes:
> Greetings,
> I want to use ido everywhere and wanted to know why this doesn't seem
> to work for setting org-mode tags (it never has for me).
>
> Using edebug to step through the call to org-icompleting-read which
> org-set-tags does I can see that it never gets to usin
All
As discussed a few days ago on this list, Carsten and the other developers are
interested in what and how us users are customizing Org mode. This was first
done in 2009, so a re-do of the survey is useful as is for how people are using
Org now, as well as a comparison to the past.
Carsten
Nicolas Goaziou writes:
> In a nutshell:
>
> (defun my-personal-table-continuation-strings (row backend info)
> (when (org-export-derived-backend-p backend 'latex)
> (replace-regexp-in-string
>"multicolumn{[0-9]+}{l}{\\(.*\\)}" "\\ldots\\ continued from previous
> page"
>
Hello,
Carsten Dominik writes:
> On 21.10.2013, at 12:03, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> Carsten Dominik writes:
>>
>>> I think one objection agains this patch is that, I think, MobileOrg
>>> relies on #+DRAWERS lines to be present to define drawers.
>>
>> The patch also contains
Hello,
Aaron Ecay writes:
> Very interesting. I did not realize that #+header: could apply to
> elements other than babel blocks. (Babel blocks are all that is
> documented in the manual, for example.) But a quick experiment shows
> that they can. I think #+header with a plist can accomplish
Hi Nicolas,
2013ko urriak 31an, Nicolas Goaziou-ek idatzi zuen:
[...]
> Moreover, your proposal, IMO, is not well-enough defined. You merely add
> a free-form string and call it "parameters". Parameters for what? Which
> syntax: a plist, switches?
I think a plist would work fine, indeed.
> Why
Hi Mark,
This seems like an intriguing idea. I have just one question: how would
this interact with editing in column view? Would function-valued
property columns be read only? Or do you have something different in
mind?
--
Aaron Ecay
r...@rickster.com writes:
> So, I've done some testing of the export functions (html and latex
> only) and found the following behaviors with this patch:
>
> - HTML
> - image in description only displayed if the protocol (file:) is
> included.
> - LaTeX
> - same, required file: protocol in descrip
On 2013-10-31 12:20, Cook, Malcolm wrote:
>> So it turns out that this is a REALLY simple patch (two characters):
>>
>> +++ b/lisp/org.el
>> @@ -18853,7 +18853,7 @@ BEG and END default to the buffer
boundaries."
>> (widen)
>> (setq beg (or beg (point-min)) end (or end (point-max)))
>> (goto-ch
Hello all,
Since the formatting on my earlier post was bad, I'm re-posting this
with a bit more information:
I would really appreciate it if it were possible to specify an
arbitrary lisp function to process node-properties when creating a
column view. Currently it is possible to have something l
Greetings,
I want to use ido everywhere and wanted to know why this doesn't seem to
work for setting org-mode tags (it never has for me).
Using edebug to step through the call to org-icompleting-read which
org-set-tags does I can see that it never gets to using ido since the
last condition be
>>
>> So it turns out that this is a REALLY simple patch (two characters):
>>
>> +++ b/lisp/org.el
>> @@ -18853,7 +18853,7 @@ BEG and END default to the buffer boundaries."
>> (widen)
>> (setq beg (or beg (point-min)) end (or end (point-max)))
>> (goto-char beg)
>> - (let ((re (concat
>>
On 2013-10-31 06:04, Alan Schmitt wrote:
r...@rickster.com writes:
So it turns out that this is a REALLY simple patch (two characters):
+++ b/lisp/org.el
@@ -18853,7 +18853,7 @@ BEG and END default to the buffer boundaries."
(widen)
(setq beg (or beg (point-min)) end (or end (point-max)))
(goto
Matt Price writes:
> (still trying to set properties automatically when a minor-mode is
> set, see first message in thread)
>
> Is there a simple way to check if the properties drawer exists before
> creating one?
> I'm trying to add a hook to org-insert-heading-hook that will create a
> property
Dnia 2013-10-31, o godz. 10:18:01
Matt Price napisał(a):
> Is there a simple way to check if the properties drawer exists before
> creating one?
> I'm trying to add a hook to org-insert-heading-hook that will create a
> property drawer if one doesn't exist (see my earlier email, in which I
> ask,
Sorry for the delayed answer.
Yes, you are right, sort of. In my set-up, the todo ended up as a
paragraph environment. I have changed my export class in order to export
the todo as a subsection or subsubsection. This gives the correct
result. My error is of course in line with the latex paragr
Is there a simple way to check if the properties drawer exists before
creating one?
I'm trying to add a hook to org-insert-heading-hook that will create a
property drawer if one doesn't exist (see my earlier email, in which I
ask,
(still trying to set properties automatically when a minor-mode is
set, see first message in thread)
Is there a simple way to check if the properties drawer exists before
creating one?
I'm trying to add a hook to org-insert-heading-hook that will create a
property drawer if one doesn't exist; I do
r...@rickster.com writes:
> On 2013-10-26 08:10, John Kitchin wrote:
>> Other than having to repeat yourself, wouldn't the
>> [[custom:file.ext][file:file.png]] syntax allow for most/all of the
>> use cases mentioned?
>>
>> rick
>>
>> Yes, I think [[custom:file.ext][file:file.png]] would cover a
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I have this, based on the example above:
>
>
> #+name: tsd-continuation-strings
> #+begin_src emacs-lisp
>
> (defun my-personal-table-continuation-strings (row backend info)
> (when (org-export-derived-backend-p 'latex)
> (replace-regexp
Hello,
co...@online.de (Jonas Hörsch) writes:
> one more patch, which takes care of re-hiding inline-tasks
> properly. finally it is possible to work with longer inline tasks
> without them getting always in the way.
Thank you for the patch. Here are a few comments.
> Subject: [PATCH] org-inlin
Hello,
Rick Frankel writes:
> On 2013-10-30 06:00, Nicolas Goaziou wrote:
>> Helo,
>> For reference, here is the suggested patch.
>>
>> Is there any strong point against it?
>
> looks great to me.
Applied.
Regards,
--
Nicolas Goaziou
>> "Jambunathan" == Jambunathan K writes:
> In LibreOffice,
> Right click on the table->Table->Text Direction->Right-to-Left.
I attach three files.
r2ltableOO.odt has been generated by OO, and displays the text as
intended.
r2ltableorg.org is the org file and displays the text as
Hello,
Aaron Ecay writes:
> 2013ko urriak 30an, Nicolas Goaziou-ek idatzi zuen:
>> IIRC, I already suggested a solution with Babel for this problem.
>> There's no need to complicate core Org syntax for such a specific
>> case.
>
> And I already said why I disagree that your proposal is a solutio
28 matches
Mail list logo
