Charles Berry writes:
> Feng Shu gmail.com> writes:
>
>>
>>
>> #+begin_org
>>
>> * headA
>> ** headB
>>
>> #+end_org
>>
>> When export to latex, how to ignore headA and don't ignore headB?
>>
>
> With a tag. See this:
>
> http://article.gmane.org/gmane.emacs.orgmode/67692
It's very useful
On Tue, Jun 18 2013, David Engster wrote:
> Peter Münster writes:
>> * contrib/lisp/org-notify.el (org-notify-make-todo)
>> (org-notify-process, org-notify-on-action-button)
>> (org-notify-action-email, org-notify-action-window): Replace `flet'
>> and `macrolet' by `cl-flet' and `cl-macrolet'.
>
>
Nicolas Goaziou writes:
>> 1. we can add a function `(defun org-latex-add-deriverd-class (class
>> exist-class) ...) to menupulate `org-latex-classes
>> 2. My patch's approach.
>> 3. others.
>
> We can modify `org-latex-classes' docstring (e.g. by adding examples) so
> it is easier to understand
Peter Münster writes:
> * contrib/lisp/org-notify.el (org-notify-make-todo)
> (org-notify-process, org-notify-on-action-button)
> (org-notify-action-email, org-notify-action-window): Replace `flet'
> and `macrolet' by `cl-flet' and `cl-macrolet'.
cl-lib was just introduced in Emacs 24.3.
-David
* contrib/lisp/org-notify.el (org-notify-make-todo): Properties from
org-element are all uppercase now.
---
contrib/lisp/org-notify.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/lisp/org-notify.el b/contrib/lisp/org-notify.el
index 3019852..dd4100d 100644
--- a/con
* contrib/lisp/org-notify.el (org-notify-make-todo)
(org-notify-process, org-notify-on-action-button)
(org-notify-action-email, org-notify-action-window): Replace `flet'
and `macrolet' by `cl-flet' and `cl-macrolet'.
---
contrib/lisp/org-notify.el | 10 +-
1 file changed, 5 insertions(+),
Hello,
Rick Frankel writes:
> There is a bug in the processing of description list.
>
> Given the list:
>
> ,
> | - not a link :: not a link
> | - [[http://link.com][http link]] :: baz
> | - [[#href-test][custom_id link]] :: bar
> | - [[def list][search link]] :: foo
> `
>
> The latex ex
Hi Eric,
while starting to write up a test document I've found some behaviour
when executing LOB calls that warrant discussion, I think:
1. The properties are evaluated at the site of the definition rather
than the site of the call. This is simply how org-babel-process-params
works, it jumps to
Hello,
AW writes:
> isn't that quite a contradiction: according to org-syntax tables can not
> contain lists, but orgtbl-to-latex treats "1." inside a table as if it were a
> beginning of a list?
Of course it is a contradiction. As, I wrote it, "orgtbl-to-latex"
interprets Org syntax differen
Hello,
Feng Shu writes:
> Not all the org-mode users are expert of lisp and not all of the org-mode
> users are well in English, so finding the variable `org-latex-classes can
> customize latex class and adding a lisp block to it may be not a easy
> things for many users.
I understand, and I
Aloha Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> My idea is to add the table to Nicolas' draft Org Syntax document, and
>> use the classes as the basis for editing and restructuring the document
>> a bit.
>
> Please go ahead, as long as the document
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> My idea is to add the table to Nicolas' draft Org Syntax document, and
> use the classes as the basis for editing and restructuring the document
> a bit.
Please go ahead, as long as the document stays faithful to the
implementation.
[...]
> Also
Achim Gratz writes:
> Achim Gratz writes:
>> Thorsten Jolitz writes:
>>> ,-
>>> | $ git --no-pager push -v origin master:refs/heads/master
>>> | send to git://orgmode.org/worg.git
>>> | fatal: Could not read from remote repository.
>>
>> Try
Thorsten Jolitz writes:
> ,-
> | $ git --no-pager push -v origin master:refs/heads/master
> | send to git://orgmode.org/worg.git
> | fatal: Could not read from remote repository.
Try this in your ~/.gitconfig:
--8<---cut here
Achim Gratz writes:
> Thorsten Jolitz writes:
>> ,-
>> | $ git --no-pager push -v origin master:refs/heads/master
>> | send to git://orgmode.org/worg.git
>> | fatal: Could not read from remote repository.
>
> Try this in your ~/.gitconfig:
>
>
Hello,
Peter Münster writes:
> After updating org-mode from git, I noticed, that
> org-element-parse-buffer uppercases the properties now. Is this a
> feature or a bug?
>
> Example:
>
> * TODO test
> DEADLINE: <2013-06-18 Tue 12:00>
> :PROPERTIES:
> :notify: test
> :END:
>
> Result of
I use the refile cache, but there is one operation that is not
performed by the caching.
The first call to refile after rebuilding the cache takes seconds to
run. Subsequent calls are much faster.
How can I do a refile without refiling in the following defun?
(defun hoka-org-refile-rebuild-cach
On Tue, Jun 18, 2013 at 01:32:10PM +0200, Thorsten Jolitz wrote:
> Rasmus writes:
>
> > Please add it to Worg, I'd say, preferably as html, if possible.
>
> I cloned the word repo again (because my existing clone had turned into
> a mess somehow) and added the exporter doc-files (as .org files),
Feng Shu gmail.com> writes:
>
>
> #+begin_org
>
> * headA
> ** headB
>
> #+end_org
>
> When export to latex, how to ignore headA and don't ignore headB?
>
With a tag. See this:
http://article.gmane.org/gmane.emacs.orgmode/67692
HTH,
Chuck
Hi all,
I had some wierd behaviour with gnuplot source blocks and I'm not sure of
the best way to fix it.
I have gnuplot source blocks that write output files that I insert into the
document using links, as such:
#+begin_src gnuplot :file transInc.eps
reset
set encoding utf8
set outp
Hi,
Following the recent trend on the list, although this is not a question
about BibTeX as such, nor about the syntax to use for references within
the text, but rather about how to integrate references in an Org file to
be easily exportable. For now, a central database is not part of the
questio
Yue Zhu writes:
> I am sending a bug report because in my machine the HTML export cannot
> work correctly for code block (tested under C and Java). The problem is
> that it adds several trailing junk characters for each line like
> `', which are displayed as squares in the
> Firefox 21.
>
> Em
Bastien writes:
> Hi Feng,
>
> Feng Shu writes:
>
>> #+begin_org
>>
>> * headA
>> ** headB
>>
>> #+end_org
>>
>> When export to latex, how to ignore headA and don't ignore headB?
>
> You can't, sorry.
Thanks for the information
--
Dnia 2013-06-18, o godz. 15:38:27
Bastien napisał(a):
> Hi Feng,
>
> Feng Shu writes:
>
> > #+begin_org
> >
> > * headA
> > ** headB
> >
> > #+end_org
> >
> > When export to latex, how to ignore headA and don't ignore headB?
>
> You can't, sorry.
>
You can (probably), but on the LaTeX side,
Hi Feng,
Feng Shu writes:
> #+begin_org
>
> * headA
> ** headB
>
> #+end_org
>
> When export to latex, how to ignore headA and don't ignore headB?
You can't, sorry.
--
Bastien
Hi Thorsten,
Thorsten Jolitz writes:
> Seems I lost my access rights in the process - what do i have to do to
> regain them?
You lost your public key? Either recover it or create a new one that
you send to me.
Thanks,
--
Bastien
---input---
#+CAPTION: test
| a | b |
| c | d |
output-
\begin{table}[htb]
\caption{test}
% How can I insert a command in this place? for example:
% \bitablecaption{你好}{Hello}
\centering
\begin{tabular}{ll}
a & b\\
c & d\\
\end{tabular}
\end{table}
#+begin_org
* headA
** headB
#+end_org
When export to latex, how to ignore headA and don't ignore headB?
Thanks
--
Rasmus writes:
> Please add it to Worg, I'd say, preferably as html, if possible.
I cloned the word repo again (because my existing clone had turned into
a mess somehow) and added the exporter doc-files (as .org files), and
pushed, but got an error:
,
David,
just to follow up on my own email. With the attached draft,
org-caldav-sync works for me now.
Thanks,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.0.3-193-g334581
diff --git a/org-caldav.el b/org-caldav.el
index 0383366..cd5b273 100644
--- a/org-caldav.el
+++ b/or
Thorsten Jolitz writes:
> Hi List,
>
> I extracted the documentation parts of the core exporter libraries and
> converted them to pdf, so they might serve as an detailled reference for
> the new exporter, much more detailled than any tutorial could be (the pdf's
> are still impressive in size, s
Hi List,
I extracted the documentation parts of the core exporter libraries and
converted them to pdf, so they might serve as an detailled reference for
the new exporter, much more detailled than any tutorial could be (the pdf's
are still impressive in size, some 50 and 80 pages).
,---
Hi,
After updating org-mode from git, I noticed, that
org-element-parse-buffer uppercases the properties now. Is this a
feature or a bug?
Example:
* TODO test
DEADLINE: <2013-06-18 Tue 12:00>
:PROPERTIES:
:notify: test
:END:
Result of (org-element-parse-buffer 'headline):
(headline (
David Engster writes:
[...]
> PS: I know that there are problems with org-caldav and the new
> exporter. I'll switch to Org 8 soon and will then merge the pending pull
> requests.
David,
What is the status on this? I'm asking because my phone suffered a
mishap yesterday and so I'm needing to
On Mon, Jun 17, 2013 at 09:08:38PM -1000, Thomas S. Dye wrote:
>
> Also, I'd like to see the Org Syntax document become an appendix to the
> manual. I know some think that it is too developer-ish to be a part of
> the manual, but it has helped me see Org Mode documents more clearly and
> I think i
Hi Levin
On Tue, Jun 18, 2013 at 9:44 AM, Levin Du wrote:
> Below is the patch that solves this problem.
Recently I also noticed a regression of org-babel-load-file that is
resolved with your patch. Thank you for saving me of one of my TODOs.
Michael
Hi, all
I find org-babel-load-file not work for my emacs-starter-kit org file.
After some traces, I find that
(org-babel-merge-params nil nil nil)
returns:
((:comments . "") (:shebang . "") (:cache . "") (:padline . "") (:noweb
. "") (:tangle . "") (:exports . "") (:results . ""))
which
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.
-
Aloha Thorsten,
Thorsten Jolitz writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
> Hi Thomas,
>
>> The attached Org mode document contains some notes on the classification
>> of Org mode elements that might be a useful addition to Nicolas
>> Goaziou's draft Org syntax document
>> (http://orgmo
39 matches
Mail list logo
