[O] Beamer and non-frames
Hi,
How do I put text between frames in an Org-Beamer document?
What I really want to do is something like:
#+begin_src LaTeX
...
\end{frame}
\againframe2{overview.fig}
\end{frame}
#+end_src
But there is /plenty/ of use of being able to write in-between frames.
I imagine two ways this could be archived,
a. Use a special property for a headline
b. Have a '#+LaTeX_Beamer:' option.
Are anybody aware of any quick fixes?
Thanks,
Rasmus
--
Sent from my Emacs
[O] How to disable description lists?
Hello everybody, is there a simple way to disable the description list syntax in a document? That is, how can I prevent emacs from interpreting '::' as a description list separator (in a given document)? The background is that I often use '::' or '::=' in my text (e.g. talking about types in Haskell or using BNF notation). It is only a minor issue, but I would very much prefer emacs not mis-interpreting and highlighting the left hand sides as description headings. Thanks, Markus
Re: [O] How to disable description lists?
Hello everybody, is there a simple way to disable the description list syntax in a document? That is, how can I prevent emacs from interpreting '::' as a description list separator (in a given document)? The background is that I often use '::' or '::=' in my text (e.g. talking about types in Haskell or using BNF notation). It is only a minor issue, but I would very much prefer emacs not mis-interpreting and highlighting the left hand sides as description headings. Put your code within babel block. I believe it shouldn't happen then. Are just turn off orgmode. #+begin_src whatever text goes here #+end_src Thanks, Markus --
Re: [O] How to disable description lists?
* Jambunathan K kjambunat...@gmail.com [29.05.2011 15:20]: is there a simple way to disable the description list syntax in a document? That is, how can I prevent emacs from interpreting '::' as a description list separator (in a given document)? Put your code within babel block. I believe it shouldn't happen then. Are just turn off orgmode. #+begin_src whatever text goes here #+end_src Yes, I do that whenever I have block-level code. But often I want to use inline '::' notation in normal org-mode lists, something like: , ! - a type is a collection of related values ! - notation: ~v :: T~, v is a value in the type T, v has type T ` Thanks, Markus
Re: [O] How to disable description lists?
Markus Berlin ecce.ber...@googlemail.com writes: * Jambunathan K kjambunat...@gmail.com [29.05.2011 15:20]: is there a simple way to disable the description list syntax in a document? That is, how can I prevent emacs from interpreting '::' as a description list separator (in a given document)? Put your code within babel block. I believe it shouldn't happen then. Are just turn off orgmode. #+begin_src whatever text goes here #+end_src Yes, I do that whenever I have block-level code. But often I want to use inline '::' notation in normal org-mode lists, something like: , ! - a type is a collection of related values ! - notation: ~v :: T~, v is a value in the type T, v has type T ` If you use the code markup (which might be desirable anyway, if you're mixing code and regular text), org mode should not interpret anything inside that markup as org text. So: - notation: =~v :: T~=, v is a value Ought to work. Eric
Re: [O] Beamer and non-frames
On 29-5-2011 10:36, Rasmus Pank Roulund wrote:
Hi,
How do I put text between frames in an Org-Beamer document?
What I really want to do is something like:
#+begin_src LaTeX
...
\end{frame}
\againframe2{overview.fig}
\end{frame}
#+end_src
But there is /plenty/ of use of being able to write in-between frames.
I imagine two ways this could be archived,
a. Use a special property for a headline
b. Have a '#+LaTeX_Beamer:' option.
Are anybody aware of any quick fixes?
Thanks,
Rasmus
Hi Rasmus,
I am sorry I have no solution for you just now.
This behavior you're seeking is something I long for as well, to insert
a this frame only custom background, to be precise.
The issue lies in the org-beamer.el way of divvying up the file into
frames (if memory servers me, it's the org-beamer-sectioning function,
but I can be mistaken), it's a big function that handles most of
org-beamers functionality. For the behavior that we seek we need to
implement a function that can encapsulate the \begin{frame} ...
\end{frame} code. However, this is not trivial.
It has my interest, but don't expect anything useful from me in the
short term, as I am an elisp noob and I am just getting acquainted with
the org api.
sander
Re: [O] Beamer and non-frames
I am sorry I have no solution for you just now.
This behavior you're seeking is something I long for as well, to
insert a this frame only custom background, to be precise.
So many great things can be put in-between
\end{frame}
...
\begin{frame}
in Beamer
The issue lies in the org-beamer.el way of divvying up the file into
frames (if memory servers me, it's the org-beamer-sectioning function,
but I can be mistaken), it's a big function that handles most of
org-beamers functionality. For the behavior that we seek we need to
implement a function that can encapsulate the \begin{frame}
... \end{frame} code. However, this is not trivial.
Yeah, I gussed it was something like that..
However, maybe something like to the following could be implemented.
I note the following in my file:
** Frame
...
#+latex_beamer_outside_frame: \againframe2{overview.fig} %(1)
** Next frame
The 'Org-exporter' notices (1) and stores it in a list L. Each time it
writes \end{frame} it also checks L and if L is non-empty the exporter
will dump whatever currently exists in L after \end{frame}.
I do, however, not know whether this is easily implemented.
It has my interest, but don't expect anything useful from me in the
short term, as I am an elisp noob and I am just getting acquainted
with the org api.
I am neither good at lisp nor programming in general, although I do need
the command for a Python presentation. I guess I'll have to fix the Beamer
code 'by hand'.
–Rasmus
--
Sent from my Emacs
Re: [O] [Orgmode] Re: [Feature Request] Cross headings in tables
On 8.2.2011, at 22:52, Achim Gratz wrote: If anybody wants to test the current state of affairs, I've just set up a fork repository to make it easier. Assuming you already have orgmode.git cloned, do a git remote add -t tableheadings remote-tableheadings git://repo.or.cz/org-mode/org-tableheadings.git git fetch remote-tableheadings tableheadings:local-tableheadings git checkout local-tableheadings to get it (change remote-tableheadings and local-tableheadings to suit your naming conventions for remotes and local branches, respectively). I will be _rebasing_ against master during development, so expect history in this branch to be volatile. As before, test cases and comments welcome. Hi Achim, hi Lawrence, this looks pretty good. One thing I found missing is that header lines should be exempted from column formulas being applied. This works for the headlines at the top of the table, but not in the middle. Try C-c C-c in the TBLFM line of: | aaa | bbb | ccc | ddd | |-+-+-+-| | ddd | eee | fff | 41 | | ddd | eee | fff | 41 | | ddd | eee | fff | 41 | |~+~+~+~| | ddd | | fff | ddd | |-+-+-+-| | ddd | eee | fff | 41 | | ddd | eee | fff | 41 | | xxx | yyy | zzz | 41 | #+TBLFM: $4=41 Also documentation in the manual is missing - one or two sentences in the right place should be enough. - Carsten
Re: [O] How to disable description lists?
* Eric Abrahamsen e...@ericabrahamsen.net [29.05.2011 16:32]: If you use the code markup (which might be desirable anyway, if you're mixing code and regular text), org mode should not interpret anything inside that markup as org text. So: - notation: =~v :: T~=, v is a value Ought to work. Thanks, but unfortunately it doesn't work. In fact, I have already been using code markup, but with ~ instead of =. Anyway, neither notation prevents org from interpreting :: inside code environments as part of description lists. BTW, I'm having the same issue with =[[--]]= notations which should not be interpreted as links. Thanks, Markus
Re: [O] How to disable description lists?
Hello, Markus Berlin ecce.ber...@googlemail.com writes: is there a simple way to disable the description list syntax in a document? That is, how can I prevent emacs from interpreting '::' as a description list separator (in a given document)? No. The background is that I often use '::' or '::=' in my text ::= shouldn't define a description list. Could you post an ECM where it does? The real separators are [space]::[space] and [space]::[end-of-line], not :: by itself. Regards, -- Nicolas Goaziou
[O] (French/german) Collecting holidays?
Would it make sense to share setups for `holiday-local-holidays'? Maybe on worg or emacs-wiki? I'm looking for french and german holidays, if anyone happens to have those set up :) -- Philipp Haselwarter
[O] HTML Syntax Highlighting Questions
I feel like this is a stupid question, but I'm having trouble finding the info I need. How do I control syntax highlighting in HTML export? Specifically, how can I: A. Disable syntax highlighting entirely B. Switch from inline colors to semantic tagging that I can style with a stylesheet? I could swear that I've seen instructions about this somewhere in the past. Bonus question: why would HTML syntax highlighting come out monochrome (as seen here: http://avdi.org/devblog/wp-content/uploads/2011/05/html.png) when the export is done in batch mode from the command line? And, more importantly, how can I fix it to generate full-color highlighting in batch mode? Thanks, -- Avdi Grimm http://avdi.org
Re: [O] HTML Syntax Highlighting Questions
Avdi Grimm a...@avdi.org writes: I feel like this is a stupid question, but I'm having trouble finding the info I need. How do I control syntax highlighting in HTML export? Specifically, how can I: A. Disable syntax highlighting entirely Remove htmlize from your load path. B. Switch from inline colors to semantic tagging that I can style with a stylesheet? I could swear that I've seen instructions about this somewhere in the past. Slightly off-topic. As part of my odt exporter work, I would very much want to have the exported code snippets marked up, well, differently. i.e., I need flexibility in *choosing* what the tag ought to be - what you call as semantic tagging. To illustrate, what gets emitted as span.../span in html export should in it's odt equivalent be emitted as text:span.../text:span. I have emphasized it elsewhere, I think Org should use htmlfontify and not htmlize. The principle is that something that is right within the core should be given preference to that which is 3 rd party. Furthermore, htmlfontify can generate htmlized source code that is cross-referenced based on a etags database. If you browse to http://rtfm.etla.org/emacs/htmlfontify/src/htmlfontify.el.html and click on some of the links within the body text you would see that it jumps to their corresponding definitions. Bonus question: why would HTML syntax highlighting come out monochrome (as seen here: http://avdi.org/devblog/wp-content/uploads/2011/05/html.png) when the export is done in batch mode from the command line? And, more importantly, how can I fix it to generate full-color highlighting in batch mode? Let me guess - It is either htmlize not being in your load path during the batch run or font lock being not being explicity turned on during the batch run or font-locking simply not making sense during batch mode. Ultimately htmlize or for that matter htmlfontify seem to depend on the fontification done by the fontification engine. Jambunathan K. --
Re: [O] HTML Syntax Highlighting Questions
On Sun, May 29, 2011 at 9:32 PM, Jambunathan K kjambunat...@gmail.com wrote: Let me guess - It is either htmlize not being in your load path during the batch run or font lock being not being explicity turned on during the batch run or font-locking simply not making sense during batch mode. Ultimately htmlize or for that matter htmlfontify seem to depend on the fontification done by the fontification engine. Hm. Bonus question, then: source code highlighting via Pygments works great with LaTeX export and the minted package. How hard would it be to use Pygments instead of htmlize/htmlfontify for HTML-exported syntax highlighting? ...and who do I need to buy beer for to make this happen, since I don't have time to do it myself? -- Avdi Grimm http://avdi.org
Re: [O] HTML Syntax Highlighting Questions
Avdi Grimm a...@avdi.org writes: On Sun, May 29, 2011 at 9:32 PM, Jambunathan K kjambunat...@gmail.com wrote: Let me guess - It is either htmlize not being in your load path during the batch run or font lock being not being explicity turned on during the batch run or font-locking simply not making sense during batch mode. Ultimately htmlize or for that matter htmlfontify seem to depend on the fontification done by the fontification engine. Hm. Bonus question, then: source code highlighting via Pygments works great with LaTeX export and the minted package. How hard would it be to use Pygments instead of htmlize/htmlfontify for HTML-exported syntax highlighting? ...and who do I need to buy beer for to make this happen, since I don't have time to do it myself? May be you could buy yourself a beer. AFAICS, htmlize generates the css based on face attributes. I am sure you could improve the results by customizing your face definitions - font-lock-keyword-face, font-lock-comment-face etc etc. As someone who is authoring a book you requirements could be stringent. May be you use latex for producing book digitally and html for getting the word out and striving to have similar visual effects on both the mediums. Jambunathan K.
Re: [O] [Announce] A GitHub Issues interface for Org-mode
Dear Puneeth On Tue, May 24, 2011 at 11:40 PM, Puneeth Chaganti puncha...@gmail.com wrote: Issue Tracker integration with Org-mode has been something that a lot of people have been looking for. Being the GitHub addict, that I am, I decided to hack up something that integrates GitHub issues with Org-mode. This looks very promising - thanks! It is a shame though that the body of the issue and the comments don't get synched (I see that you have these listed as TODO). I also noticed that if I type any text directly under the issue's heading in my org file, then this text is /wiped/ when I execute =org-ghi-update-current-issue=. However, any subheadings (and their text) do survive, but they never get synched back to GitHub. Cheers Will It presently allows - Importing all open issues from a project into an org-file. [Milestone due dates (if any) are added as Deadlines. - Closing Issues, Editing Tags, Changing Issue Name - Convert a TODO item into an Org-mode issue. However, it uses APIv3 of GitHub, which is Beta. So, expect some erratic behaviour. :) I have put up my code here [1]. The code isn't all that clean and robust, but it works. Hope atleast some of you will find it useful. Any suggestions, feedback and code help is more than welcome. -- Dr William Henney, Centro de Radioastronomía y Astrofísica, Universidad Nacional Autónoma de México, Campus Morelia
[O] git submodule and the bzr mirror on launchpad
Hi, I am trying to familiarize myself with bazaar, so I had a look at the org-mode bzr mirror of the git repo. https://code.launchpad.net/org-mode It fails to import since a couple of weeks, probably since this commit: , | commit 509ee52b5317cbcd4a611f57980038c7249363ce | Author: Eric Schulte schulte.e...@gmail.com | Date: Sun Oct 3 10:50:21 2010 -0600 ` Turns out that there is some trouble handling git submodules in the import; (see: https://bugs.launchpad.net/bzr/+bug/402814 ) they are working on this issue. Am I right that since march there is only the jump.el submodule? I am not familiar with git, but I was wondering if there is another way in this miraculous toolbox that is git - other than submodule - to get the current behaviour. It is not worth significant effort, especially because there is hope this issue will be solved on launchpads/bzr side hopefully soon, but if there is an easy and quick way, it would be nice to get the bzr mirror (and with it the daily .deb snapshots for ubuntu) back running. - Memnon
Re: [O] [Announce] A GitHub Issues interface for Org-mode
William, Thanks for trying it out! On Mon, May 30, 2011 at 9:16 AM, William Henney when...@gmail.com wrote: This looks very promising - thanks! It is a shame though that the body of the issue and the comments don't get synched (I see that you have these listed as TODO). I also noticed that if I type any text directly This is Experimental and I am open to suggestions, but one of the problems I have is that the GitHub API v3 is unstable and causing some trouble. I initially had a version, where the BODY of the issue was being sync-ed, but after a while, I stopped getting the body of the issue in the JSON. I'm not sure what went wrong, but a simple GET using curl also failed to give me the body. I shall look at it again, in a short while. under the issue's heading in my org file, then this text is /wiped/ when I execute =org-ghi-update-current-issue=. However, any subheadings (and their text) do survive, but they never get synched back to GitHub. I haven't figured out what would be the right way to do this. I am open to any suggestions from your side. Thanks, Puneeth
Re: [O] HTML Syntax Highlighting Questions
On Mon, May 30, 2011 at 7:55 AM, Avdi Grimm a...@avdi.org wrote: On Sun, May 29, 2011 at 9:32 PM, Jambunathan K kjambunat...@gmail.com wrote: Let me guess - It is either htmlize not being in your load path during the batch run or font lock being not being explicity turned on during the batch run or font-locking simply not making sense during batch mode. Ultimately htmlize or for that matter htmlfontify seem to depend on the fontification done by the fontification engine. Hm. Bonus question, then: source code highlighting via Pygments works great with LaTeX export and the minted package. How hard would it be to use Pygments instead of htmlize/htmlfontify for HTML-exported syntax highlighting? I've some hackish code, which I use to publish my blog. It essentially, looks at all the code blocks in the html output and replaces them with Pygments output for them. The code is here [1] HTH, Puneeth [1] https://github.com/punchagan/org-hyde/blob/master/org-hyde.el#L109
