Nick Dokos wrote:
> Marcin Borkowski writes:
>> On 2015-03-20, at 10:07, Sebastien Vauban wrote:
>>> Marcin Borkowski wrote:
I'm wondering what people do to keep the configuration of their Org
files in order.
>>>
>>> I'm not sure to correctly grasp your objective. Could you restate it?
Hello,
Rasmus writes:
> As is evident from the git log, I have made the following mistake at least
> twice:
>
>(org-element-parse-secondary-string nil restrictions)
>
> I wish this would just return nil instead of an error. In particular, in
> ox files you have to do
>
>(org-element-par
On 2015-03-20T22:45:02+1100, Randomcoder
said:
R> Does the ID property have any use? I know I can disable it,
but R> where
R> is it being used ? (the ID property that org-mobile generates
for R> each heading)
R> Are there any drawbacks to just disabling it with (setq R>
org-mobile-for
Rasmus writes:
> Nicolas Goaziou writes:
>
>> Do you think that you /always/ want "pdfkeywords" to hold exactly the
>> same contents as what you could put in your document?
>
> You as in me: yes most certainly.
IIUC, it contradicts your initial post where you wanted, at some later
time, to add
Alexis wrote:
> On 2015-03-20T22:45:02+1100, Randomcoder said:
>
> R> Does the ID property have any use? I know I can disable it, but R> where
>
> R> is it being used ? (the ID property that org-mobile generates for R> each
> heading)
>
> R> Are there any drawbacks to just disabling it with (setq
Leo Ufimtsev writes:
> Interesting, I didn't know that. Thank you for pointing it out.
>
> Maybe then just go along with the variable that would give people the choice,
> (I wouldn't mind '\emsp' being the default, so long as it can be
> changed to something else).
Having a variable to choose i
On 2015-03-21, at 04:05, Nick Dokos wrote:
> Yes, but why do you do that? What are you trying to accomplish? What
> does "keeping the configuration in order" mean?
I have that org-one-to-many utility, which splits the Org file at
(selected) headings, effectively making them separate Org files.
Marcin Borkowski wrote:
> On 2015-03-21, at 04:05, Nick Dokos wrote:
>
>> Yes, but why do you do that? What are you trying to accomplish? What
>> does "keeping the configuration in order" mean?
>
> I have that org-one-to-many utility, which splits the Org file at
> (selected) headings, effectively
On 2015-02-18, at 20:37, Andreas Leha
wrote:
> I also use tikz in my org files. I just include a slightly more
> involved version of Eric's example to show some of the beauty of org.
OK, so I'm trying to understand it. (One of the reasons is that it
doesn't work for me; somehow I couldn't ge
Sebastien Vauban
writes:
I can tell you they aren't isomorphic... The noexport tag simply says
"don't export this subtree". The COMMENT keyword adds "don't run any
Babel code block in there".
>>
>> COMMENT also says that the whole subtree is not to be exported according
>> to the
Sebastien Vauban
writes:
> Marcin Borkowski wrote:
>> On 2015-03-21, at 04:05, Nick Dokos wrote:
>>
>>> Yes, but why do you do that? What are you trying to accomplish? What
>>> does "keeping the configuration in order" mean?
>>
>> I have that org-one-to-many utility, which splits the Org file at
On 21 March 2015, Martin Leduc wrote:
I'm using org-mode to write a paper and export it to a pdf. It compiles just
fine.
However, when opening the experted pdf (with evince or okular) and searching
for a word, the output from the search function is a list of words with
apparently incorrect c
Thanks for your response Bill.
You can find a minimal example here, with the org file, and the tex and pdf
files generated from it. Firts try to search within the pdf. It does not work
(at least on my side) To solve the problem, remove the line with
\usepackage[T1]{fontenc}
in the tex file, an
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.
-
Good day,
I use the org-mode to take statistical data from remote servers. And founf out
that current scheme such this doesn't support a port value:
#+name: ALLODS-248601-database
#+header: :engine mysql
#+header: :dbhost 127.0.0.1
#+header: :dbuser test
#+header: :dbpassword test
#+header: :da
I appologize, send the fixed of-sql.el file
Пересылаемое сообщение
От кого: Денис Мекшун
Кому: emacs-orgmode@gnu.org
Дата: Среда, 18 марта 2015, 18:12 +03:00
Тема: To support the ":dbport" value
Good day,
I use the org-mode to take statistical data from remote servers. And f
I guess this is either a feature request or a discussion point, but is there a
good reason that footnotes aren't considered as links for the purposes of
things like `org-next-link` (despite being displayed like links)? From where
I'm sitting, this would be very useful for the sake of things like
Hi Marcin,
see some inline comments. Note, that I have not done much research
on this and all my information may be outdated
Marcin Borkowski writes:
> On 2015-02-18, at 20:37, Andreas Leha
> wrote:
>
>> I also use tikz in my org files. I just include a slightly more
>> involved version
Hi all,
please find attached a small patch that fixes a problem discussed
in [1].
In short, when executing a latex src block and htlatex is a valid
option, it should be used even if imagemagick is part of the headers.
Regards,
Andreas
[1] http://permalink.gmane.org/gmane.emacs.orgmode/96257
Rasmus writes:
> Nicolas Goaziou writes:
>
>> Document properties are keywords where `org-element-context' is allowed
>> to return an object. It doesn't make sense to add random keywords
>> specific to some export back-ends to the list.
>
> I think something like SUBJECT in ox-koma-letter makes
On 2015-03-21T01:59:07+1100, Richard Lawrence
said:
RL> I am not sure if this counts as a bug or not, so someone else
RL> should still address this question. Maybe this is the
desired RL> behavior, given that the link text is hidden? Or
maybe it's just RL> not possible to search in hidde
Hi Rainer,
In terms of searching through all open buffers,
here is what I use (helm and helm-multi-occur):
,
| (setq helm-M-x-requires-pattern 0)
|
| ;; http://emacs.stackexchange.com/a/740
| (require 'helm-regexp)
| (eval-after-load "helm-regexp"
| '(setq helm-source-moccur
| (hel
Nicolas Goaziou writes:
>> I think something like SUBJECT in ox-koma-letter makes sense.
>
> It seems we are failing to communicate.
Probably I'm just slower :)
> I have nothing against SUBJECT being parsed in "ox-koma-letter".
> However, `org-element-document-properties' are keywords expected
On Sat, Mar 21, 2015 at 7:34 PM, Alexis wrote:
>
> On 2015-03-21T01:59:07+1100, Richard Lawrence
> said:
>
> RL> I am not sure if this counts as a bug or not, so someone else
> RL> should still address this question. Maybe this is the desired
> RL> behavior, given that the link text is hidden?
Rasmus writes:
> I /think/ that is what I would like. But I don't understand the what you
> mean concretely: would you have something like:
>
> (:subject "SUBJECT" nil nil space parsed)
(:subject "SUBJECT" nil nil parsed)
`parsed' behavior implies `space' anyway, since we're talki
Nicolas Goaziou writes:
> Rasmus writes:
>
>> I /think/ that is what I would like. But I don't understand the what you
>> mean concretely: would you have something like:
>>
>> (:subject "SUBJECT" nil nil space parsed)
>
>
>(:subject "SUBJECT" nil nil parsed)
>
> `parsed' behavior i
26 matches
Mail list logo
