Rasmus ras...@gmx.us writes:
Keywords are akin to small headings to identify the contents of a
document. I see no reason to restrict this to the reader of the
electronic version of a document.
What are you talking about? I don't want to restrict anything: AFAIU,
the feature you propose
Gustav Wikström gustav.e...@gmail.com writes:
I don't mind. Wrote a few lines and the patch is attached!
Applied. Thank you.
Regards,
Here is my solution so far:
http://kitchingroup.cheme.cmu.edu/blog/2015/03/19/Restarting-org-babel-sessions-in-org-mode-more-effectively/
It is a few functions that can go through the code blocks and
selectively rerun only the blocks that are in the session of the block
you run the restart
Hello all,
I'm wondering what people do to keep the configuration of their Org
files in order. I use a dedicated top-level headline, with a COMMENT
keyword, but I started to think that a :noexport: tag might be a better
idea.
Are there any advantages of one over the other, or other approaches
Hi,
I have a similar setting, and it works fine for me:
#+INCLUDE: ./all_pub.html html
(notice the absence of around the file name)
I use org-8.3beta (taken from the git repo some weeks ago).
Best,
Giuseppe Lipari
2015-03-18 19:46 GMT+01:00 Rasmus ras...@gmx.us:
Hi,
Titus von der
Nicolas Goaziou m...@nicolasgoaziou.fr 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.
Do you think that a user who wants to fill pdfkeywords will always want
to also add
I suppose $^{foo}$ will do what you want. you may need some additional
\mathrm command if you do not want math fonts.
or maybe try \textsuperscript{foo}
(untested)
Andreas Leha writes:
Hi all,
quick question: What is the syntax of superscripts without a 'base
character'?
I tried to use
Hi all,
quick question: What is the syntax of superscripts without a 'base
character'?
I tried to use ^{foo} and {}^{foo} which both do not produce what I
expect in the latex export.
\nbsp^{foo} comes close.
Best,
Andreas
Hi Nicolas,
Excellent comments. Thanks a lot!
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
In this case, I suggest to change `org-koma-letter--special-headline'
into `org-koma-letter--special-tag'
I agree.
Eventually, since you're only interested in the first special tag
encountered,
Rasmus ras...@gmx.us writes:
+(defun org-koma-letter--special-tag (headline info)
+ Non-nil if HEADLINE is a special headline.
+INFO is a plist holding contextual information. Returns first
^^^
Return, per (info (elisp)Documentation
Hi Rasmus,
Thanks for your continuing help here.
Rasmus ras...@gmx.us writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi Rasmus,
Rasmus ras...@gmx.us writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Thanks for the answer. So, there is no easy way out. I
Hi Rasmus,
Rasmus ras...@gmx.us writes:
John Kitchin jkitc...@andrew.cmu.edu writes:
or maybe try \textsuperscript{foo}
This would work in at least KOMA-Script.
Check org-match-substring-regexp. As you see at subscripts must start
with something that's not a space. So I guess you could
John Kitchin jkitc...@andrew.cmu.edu writes:
or maybe try \textsuperscript{foo}
This would work in at least KOMA-Script.
Check org-match-substring-regexp. As you see at subscripts must start
with something that's not a space. So I guess you could use a filter to
remove some otherwise unused
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Thanks for the answer. So, there is no easy way out. I think I'll
stick to the \nbsp version, then. Although introducing some character
that will be removed during export through a filter might be handy in
other cases, too. I'll
Hi Rasmus,
Rasmus ras...@gmx.us writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Thanks for the answer. So, there is no easy way out. I think I'll
stick to the \nbsp version, then. Although introducing some character
that will be removed during export through a filter might
Hi John,
Thanks a lot for your answer.
John Kitchin jkitc...@andrew.cmu.edu writes:
I suppose $^{foo}$ will do what you want. you may need some additional
\mathrm command if you do not want math fonts.
or maybe try \textsuperscript{foo}
(untested)
These both work (you are right about the
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi Rasmus,
Rasmus ras...@gmx.us writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Thanks for the answer. So, there is no easy way out. I think I'll
stick to the \nbsp version, then. Although introducing some character
Ken Mankoff mank...@gmail.com writes:
On 2015-03-19 at 10:26, John Kitchin jkitc...@andrew.cmu.edu wrote:
Is it possible to restart an org-babel session from the current point?
What I mean is if you have a largish org-file with many session blocks,
and you want to go the end and continue it,
Agendas can do get exported. Current agenda buffer can be exported using
org-agenda-write to several formats. Custom agendas can be assigned file
name(s) and automatically export to one or more file types.
See: http://orgmode.org/manual/Exporting-Agenda-Views.html
-Original
On 2015-03-19 at 10:26, John Kitchin jkitc...@andrew.cmu.edu wrote:
Is it possible to restart an org-babel session from the current point?
What I mean is if you have a largish org-file with many session blocks,
and you want to go the end and continue it, you need to run each session
block
Hi all,
Is it possible to restart an org-babel session from the current point?
What I mean is if you have a largish org-file with many session blocks,
and you want to go the end and continue it, you need to run each session
block before the end to recreate the session.
I have a little function
Aloha all,
John Kitchin jkitc...@andrew.cmu.edu writes:
That is an interesting one I did not know of. I would not want to always
run every block, some of them might not be part of a session, and it is
possible to have multiple named sessions in a buffer. It might be good
practice to not do
On 2015-03-19 at 13:47, Thomas S. Dye t...@tsdye.com wrote:
Ken Mankoff mank...@gmail.com writes:
On 2015-03-19 at 10:26, John Kitchin jkitc...@andrew.cmu.edu wrote:
Is it possible to restart an org-babel session from the current point?
What I mean is if you have a largish org-file with many
That is an interesting one I did not know of. I would not want to always
run every block, some of them might not be part of a session, and it is
possible to have multiple named sessions in a buffer. It might be good
practice to not do that though ;)
I will share my way of doing this if nothing
Hi John,
t...@tsdye.com (Thomas S. Dye) writes:
Aloha all,
John Kitchin jkitc...@andrew.cmu.edu writes:
That is an interesting one I did not know of. I would not want to always
run every block, some of them might not be part of a session, and it is
possible to have multiple named sessions
Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
As a final step, would you mind preparing an entry in ORG-NEWS? I think
most of it can be extracted from your commit messages.
I don't mind. Wrote a few lines and the patch is attached!
Best regards
Gustav
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).
Thoughts?
Leo Ufimtsev | Intern Software Engineer @
Literal Examples seem to begin with the following pattern: #+BEGIN_*.
The * is often replaced by SRC EXAMPLE VERBATIM, etc..
Org Mode also recognizes Literal Examples with 'nonstandard' endings,
e.g. #+BEGIN_LANGUAGE. Should users rely on these 'nonstandard'
Literal Examples being recognized in
Hi there,
it seems that reviving old threads is my new hobby;-).
On 2014-11-29, at 22:58, Marcin Borkowski mb...@wmi.amu.edu.pl wrote:
On 2014-11-29, at 22:53, Marcin Borkowski wrote:
On 2014-11-24, at 19:38, Rasmus wrote:
Marcin Borkowski mb...@wmi.amu.edu.pl writes:
Hello,
I'm
Emacs Org Mode recognizes diary entries both inside and outside angle
brackets (less than and greater than signs), e.g.:
%%(diary-date 2015 03 19), and
%%(diary-date 2015 03 19).
Should users rely on both forms being recognized in the future?
Emacs Org Mode also fully parses / recognizes diary
Thanks Ramus and Giuseppe, as you say it works as expected in
v8.3beta.
Titus
On 2015-03-19 Thu 01:28, Giuseppe Lipari wrote:
Hi,
I have a similar setting, and it works fine for me:
#+INCLUDE: ./all_pub.html html
(notice the absence of around the file name)
I use org-8.3beta (taken
31 matches
Mail list logo
