c On Mon, May 30, 2011 at 5:00 PM, wrote: > Send Emacs-orgmode mailing list submissions to > emacs-orgmode@gnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.gnu.org/mailman/listinfo/emacs-orgmode > or, via email, send a message with subject or body 'help' to > emacs-orgmode-request@gnu.org > > You can reach the person managing the list at > emacs-orgmode-owner@gnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Emacs-orgmode digest..." > > > Today's Topics: > > 1. Re: Beamer and non-frames (Sander Boer) > 2. Re: Beamer and non-frames (Rasmus Pank Roulund) > 3. Re: [Orgmode] Re: [Feature Request] Cross headings in tables > (Carsten Dominik) > 4. Re: How to disable description lists? (Markus Berlin) > 5. Re: How to disable description lists? (Nicolas Goaziou) > 6. (French/german) Collecting holidays? (Philipp Haselwarter) > 7. HTML Syntax Highlighting Questions (Avdi Grimm) > 8. Re: HTML Syntax Highlighting Questions (Jambunathan K) > 9. Re: HTML Syntax Highlighting Questions (Avdi Grimm) > 10. Re: HTML Syntax Highlighting Questions (Jambunathan K) > 11. Re: [Announce] A GitHub Issues interface for Org-mode > (William Henney) > 12. git submodule and the bzr mirror on launchpad (Memnon Anon) > 13. Re: [Announce] A GitHub Issues interface for Org-mode > (Puneeth Chaganti) > 14. Re: HTML Syntax Highlighting Questions (Puneeth Chaganti) > 15. Re: Problem with make and autoloads (suvayu ali) > 16. Re: (French/german) Collecting holidays? (Christian Egli) > 17. Re: orgmode/beamer - won't export blocks (Benjamin Slade) > 18. [PATCH] Makefile robustness tweak (Barak A. Pearlmutter) > 19. Re: [Announce] A GitHub Issues interface for Org-mode > (William Henney) > 20. Re: orgmode/beamer - won't export blocks (Sebastien Vauban) > 21. Re: git submodule and the bzr mirror on launchpad (Eric Schulte) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 29 May 2011 19:04:53 +0200 > From: Sander Boer > To: emacs-orgmode@gnu.org > Subject: Re: [O] Beamer and non-frames > Message-ID: > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > 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} > > \againframe<2>{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 > > > > > ------------------------------ > > Message: 2 > Date: Sun, 29 May 2011 19:18:19 +0200 > From: Rasmus Pank Roulund > To: emacs-orgmode@gnu.org > Subject: Re: [O] Beamer and non-frames > Message-ID: > Content-Type: text/plain; charset=utf-8 > > > > 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: \againframe<2>{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 > > > > > ------------------------------ > > Message: 3 > Date: Sun, 29 May 2011 20:18:38 +0200 > From: Carsten Dominik > To: Achim Gratz , Lawrence Mitchell > Cc: emacs-orgmode@gnu.org > Subject: Re: [O] [Orgmode] Re: [Feature Request] Cross headings in > tables > Message-ID: > Content-Type: text/plain; charset=us-ascii > > > 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 > > > > > ------------------------------ > > Message: 4 > Date: Sun, 29 May 2011 20:44:05 +0200 > From: Markus Berlin > To: emacs-orgmode@gnu.org > Subject: Re: [O] How to disable description lists? > Message-ID: <20110529184403.GA10375@gmail.com> > Content-Type: text/plain; charset=us-ascii > > * Eric Abrahamsen [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 > > > > > > ------------------------------ > > Message: 5 > Date: Sun, 29 May 2011 21:31:29 +0200 > From: Nicolas Goaziou > To: Markus Berlin > Cc: emacs-orgmode@gnu.org > Subject: Re: [O] How to disable description lists? > Message-ID: <87pqn1gv72.fsf@gmail.com> > Content-Type: text/plain > > Hello, > > Markus Berlin 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 > > > > ------------------------------ > > Message: 6 > Date: Mon, 30 May 2011 01:19:19 +0200 > From: Philipp Haselwarter > To: emacs-orgmode@gnu.org > Subject: [O] (French/german) Collecting holidays? > Message-ID: <87boyl9jt4.fsf@nzebook.haselwarter.org> > Content-Type: text/plain > > 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 > > > > > ------------------------------ > > Message: 7 > Date: Sun, 29 May 2011 20:50:05 -0400 > From: Avdi Grimm > To: emacs-orgmode > Subject: [O] HTML Syntax Highlighting Questions > Message-ID: > Content-Type: text/plain; charset=ISO-8859-1 > > 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 > > > > ------------------------------ > > Message: 8 > Date: Mon, 30 May 2011 07:02:51 +0530 > From: Jambunathan K > To: avdi@avdi.org > Cc: emacs-orgmode > Subject: Re: [O] HTML Syntax Highlighting Questions > Message-ID: <81zkm5otvg.fsf@gmail.com> > Content-Type: text/plain > > Avdi Grimm 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 ... > in html export should in it's odt equivalent be emitted as > .... > > 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. > -- > > > > ------------------------------ > > Message: 9 > Date: Sun, 29 May 2011 22:25:31 -0400 > From: Avdi Grimm > To: Jambunathan K > Cc: emacs-orgmode > Subject: Re: [O] HTML Syntax Highlighting Questions > Message-ID: > Content-Type: text/plain; charset=ISO-8859-1 > > On Sun, May 29, 2011 at 9:32 PM, Jambunathan K > 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 > > > > ------------------------------ > > Message: 10 > Date: Mon, 30 May 2011 08:50:14 +0530 > From: Jambunathan K > To: avdi@avdi.org > Cc: emacs-orgmode > Subject: Re: [O] HTML Syntax Highlighting Questions > Message-ID: <81pqn0q3gx.fsf@gmail.com> > Content-Type: text/plain > > Avdi Grimm writes: > > > On Sun, May 29, 2011 at 9:32 PM, Jambunathan K > 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. > > > > > > ------------------------------ > > Message: 11 > Date: Sun, 29 May 2011 22:46:32 -0500 > From: William Henney > To: Puneeth Chaganti > Cc: emacs-orgmode > Subject: Re: [O] [Announce] A GitHub Issues interface for Org-mode > Message-ID: > Content-Type: text/plain; charset=ISO-8859-1 > > Dear Puneeth > > On Tue, May 24, 2011 at 11:40 PM, Puneeth Chaganti > 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 > > > > ------------------------------ > > Message: 12 > Date: Mon, 30 May 2011 04:30:02 +0000 (UTC) > From: Memnon Anon > To: emacs-orgmode@gnu.org > Subject: [O] git submodule and the bzr mirror on launchpad > Message-ID: <87tyccygj3.fsf@mean.albasani.net> > Content-Type: text/plain; charset=us-ascii > > 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 > | 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 > > > > > > > > > ------------------------------ > > Message: 13 > Date: Mon, 30 May 2011 10:13:54 +0530 > From: Puneeth Chaganti > To: William Henney > Cc: emacs-orgmode > Subject: Re: [O] [Announce] A GitHub Issues interface for Org-mode > Message-ID: > Content-Type: text/plain; charset=UTF-8 > > William, > > Thanks for trying it out! > > On Mon, May 30, 2011 at 9:16 AM, William Henney 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 > > > > ------------------------------ > > Message: 14 > Date: Mon, 30 May 2011 10:17:38 +0530 > From: Puneeth Chaganti > To: avdi@avdi.org > Cc: emacs-orgmode , Jambunathan K > > Subject: Re: [O] HTML Syntax Highlighting Questions > Message-ID: > Content-Type: text/plain; charset=UTF-8 > > On Mon, May 30, 2011 at 7:55 AM, Avdi Grimm wrote: > > On Sun, May 29, 2011 at 9:32 PM, Jambunathan K > 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 > > > > ------------------------------ > > Message: 15 > Date: Sun, 29 May 2011 23:40:21 -0700 > From: suvayu ali > To: Org Mode > Subject: Re: [O] Problem with make and autoloads > Message-ID: > Content-Type: text/plain; charset=ISO-8859-1 > > On Thu, May 26, 2011 at 9:56 AM, Matt Lundin wrote: > > Recently, autoloads ceased to work in my local org-mode installation. > > > > My typical update routine is to: > > > > 1. Pull the most recent changes into my local org-mode repository, > > located at "~/org-mode". > > 2. Run "make clean && make". > > > > My .emacs file contains the following lines: > > > > --8<---------------cut here---------------start------------->8--- > > (add-to-list 'load-path "~/org-mode/lisp") > > (require 'org-install) > > --8<---------------cut here---------------end--------------->8--- > > I see identical behaviour after I updated org today. > > -- > Suvayu > > Open source is the future. It sets us free. > > > > ------------------------------ > > Message: 16 > Date: Mon, 30 May 2011 13:39:39 +0200 > From: Christian Egli > To: emacs-orgmode@gnu.org > Subject: Re: [O] (French/german) Collecting holidays? > Message-ID: <87wrh8qux0.fsf@sbs.ch> > Content-Type: text/plain; charset=utf-8 > > Philipp Haselwarter writes: > > > 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 :) > > Have you checked > http://www.emacswiki.org/emacs/CalendarLocalization#toc12? > > -- > Christian Egli > Swiss Library for the Blind, Visually Impaired and Print Disabled > Grubenstrasse 12, CH-8045 Z?rich, Switzerland > > > > > ------------------------------ > > Message: 17 > Date: Sun, 29 May 2011 12:06:08 -0500 > From: Benjamin Slade > To: emacs-orgmode@gnu.org > Subject: Re: [O] orgmode/beamer - won't export blocks > Message-ID: > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Seb, > > So you don't include LaTeX packages that you always want to be loaded > in the .emacs config? I have a bunch of packages that I would need for > my beamer presentations and it would be nice just to have them > automatically included every time. > > By the bye, I found the old config code from here: > > http://emacs-fu.blogspot.com/2009/10/writing-presentations-with-org-mode-and.html > > cheers, > --Ben > > ----------------------------------------------------------------------------- > From: Sebastien Vauban > Subject: Re: [O] orgmode/beamer - won't export blocks > Date: Fri, 27 May 2011 23:35:11 +0200 > User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (windows-nt) > > Hi Benjamin, > > Benjamin Slade wrote: > > Thank you for the help. > > > > Yes, removing the configuration code from .emacs results in the > > correct behaviour (i.e. blocks are now exported properly). > > Where did you find that way to do? I guess in old threads... Is it still > on > Worg, this should be removed. > > > Quick question -- is there still a way of setting up beamer/orgmode > > configuration in .emacs? > > Why are you asking that? It's even better: you don't need any special > configuration anymore (like before) for beamer to work out of the box. > > The only lines I still have in my .emacs about beamer are: > > #+begin_src emacs-lisp > ;; XXX 2010-03-25 TEMP Fix for conflict TikZ/hyperref: loading > ;; `atbegshi' before document class beamer > (add-to-list 'org-export-latex-classes > '("beamer" > "\\RequirePackage{atbegshi} > \\documentclass{beamer}\n" > org-beamer-sectioning)) > #+end_src > > Maybe even not needed anymore... > > Best regards, > Seb > > -- > S??bastien Vauban > > > > ------------------------------ > > Message: 18 > Date: Mon, 30 May 2011 09:25:35 +0100 > From: "Barak A. Pearlmutter" > To: emacs-orgmode@gnu.org > Subject: [O] [PATCH] Makefile robustness tweak > Message-ID: > Content-Type: text/plain; charset=us-ascii > > >From 7c79ea0a21ad6d2646958d25c298a1ac9624e9f6 Mon Sep 17 00:00:00 2001 > From: Barak A. Pearlmutter > Date: Sun, 29 May 2011 22:20:31 +0100 > Subject: [PATCH] fail to rm or build incorrect files when doc directory > nonexistent > > --- > Makefile | 24 ++++++++++++------------ > 1 files changed, 12 insertions(+), 12 deletions(-) > > diff --git a/Makefile b/Makefile > index 9693fd3..239ab2e 100644 > --- a/Makefile > +++ b/Makefile > @@ -238,30 +238,30 @@ lisp/org-install.el: $(LISPFILES0) Makefile > mv org-install.el lisp > > doc/org: doc/org.texi > - (cd doc; $(MAKEINFO) --no-split org.texi -o org) > + (cd doc && $(MAKEINFO) --no-split org.texi -o org) > > doc/org.pdf: doc/org.texi > - (cd doc; $(TEXI2PDF) org.texi) > + (cd doc && $(TEXI2PDF) org.texi) > > doc/orgguide.pdf: doc/orgguide.texi > - (cd doc; $(TEXI2PDF) orgguide.texi) > + (cd doc && $(TEXI2PDF) orgguide.texi) > > doc/org.html: doc/org.texi > - (cd doc; $(TEXI2HTML) --no-split -o org.html org.texi) > + (cd doc && $(TEXI2HTML) --no-split -o org.html org.texi) > UTILITIES/manfull.pl doc/org.html > > doc/orgcard.pdf: doc/orgcard.tex > - (cd doc; pdftex orgcard.tex) > + (cd doc && pdftex orgcard.tex) > > doc/orgcard.txt: doc/orgcard.tex > - (cd doc; perl ../UTILITIES/orgcard2txt.pl orgcard.tex > > orgcard.txt) > + (cd doc && perl ../UTILITIES/orgcard2txt.pl orgcard.tex > > orgcard.txt) > > doc/orgcard_letter.tex: doc/orgcard.tex > perl -pe 's/\\pdflayout=\(0l\)/\\pdflayout=(1l)/' \ > doc/orgcard.tex > doc/orgcard_letter.tex > > doc/orgcard_letter.pdf: doc/orgcard_letter.tex > - (cd doc; pdftex orgcard_letter.tex) > + (cd doc && pdftex orgcard_letter.tex) > > # Below here are special targets for maintenance only > > @@ -427,11 +427,11 @@ cleancontrib: > cleanelc: > rm -f $(ELCFILES) > cleandoc: > - (cd doc; rm -f org.pdf org org.html orgcard.pdf orgguide.pdf) > - (cd doc; rm -f *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys *.pg > *.pgs) > - (cd doc; rm -f *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps) > - (cd doc; rm -f orgcard_letter.tex orgcard_letter.pdf) > - (cd doc; rm -rf manual) > + -(cd doc && rm -f org.pdf org org.html orgcard.pdf orgguide.pdf) > + -(cd doc && rm -f *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys *.pg > *.pgs) > + -(cd doc && rm -f *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps) > + -(cd doc && rm -f orgcard_letter.tex orgcard_letter.pdf) > + -(cd doc && rm -rf manual) > > cleanrel: > rm -rf RELEASEDIR > -- > 1.7.2.5 > > > > > ------------------------------ > > Message: 19 > Date: Mon, 30 May 2011 09:38:08 -0500 > From: William Henney > To: Puneeth Chaganti > Cc: emacs-orgmode > Subject: Re: [O] [Announce] A GitHub Issues interface for Org-mode > Message-ID: > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Puneeth > > On Sun, May 29, 2011 at 11:43 PM, Puneeth Chaganti > wrote: > > William, > > > > Thanks for trying it out! > > > > No problem - anything to avoid doing my real work.... > > > On Mon, May 30, 2011 at 9:16 AM, William Henney > 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. > > > > Is the v2 API missing some features you need? Maybe it would be better > to use that until v3 is out of beta > > > > >> 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. > > > > Well, the wiping of text directly below an issue's level 2 heading is > a data-loss bug, so I would suggest that you certainly don't do that > :) > > With respect to sub-headings (level 3 or below) that are added by hand > to the github.org file, I would suggest that by default you do not > sync them with GitHub. Maybe you could have a function called > something like org-ghi-make-heading-a-comment that would work in a > similar way to org-ghi-make-todo-an-issue. However, it seems that > GitHub issue comments only understand markdown syntax, not org syntax, > so unless the comment is just simple text it would require an export > step (https://github.com/alexhenning/ORGMODE-Markdown might help > there). > > Cheers > > Will > > > -- > > ? Dr William Henney, Centro de Radioastronom?a y Astrof?sica, > ? Universidad Nacional Aut?noma de M?xico, Campus Morelia > > > > ------------------------------ > > Message: 20 > Date: Mon, 30 May 2011 16:42:03 +0200 > From: "Sebastien Vauban" > To: emacs-orgmode@gnu.org > Subject: Re: [O] orgmode/beamer - won't export blocks > Message-ID: <80boykxnb8.fsf@somewhere.org> > Content-Type: text/plain; charset=utf-8 > > Hi Benjamin, > > Benjamin Slade wrote: > > So you don't include LaTeX packages that you always want to be loaded in > the > > .emacs config? > > No, I tend to avoid doing such. This really is the worst place to think > of... > because your .emacs file is personal. Then, you cannot (easily) share any > of > your custom with anybody... > > > I have a bunch of packages that I would need for my beamer presentations > and > > it would be nice just to have them automatically included every time. > > If you want to do so, either put your list of packages > > - in an Org file that you #+INCLUDE as needed, or > - in your own theme (that's what I generally end up doing). > > Both are better places, IMHO, for customs. > > Best regards, > Seb > > -- > S?bastien Vauban > > > > > ------------------------------ > > Message: 21 > Date: Mon, 30 May 2011 09:33:18 -0600 > From: Eric Schulte > To: Memnon Anon > Cc: emacs-orgmode@gnu.org > Subject: Re: [O] git submodule and the bzr mirror on launchpad > Message-ID: <87k4d8b3up.fsf@gmail.com> > Content-Type: text/plain > > Hi, > > Memnon Anon writes: > > > 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 > > | 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? > > That is correct, the only submodule is jump.el which isn't required for > normal use, but is included for navigation of the testing framework. > See the contents of the .gitmodules file in the Org-mode directory > > ,----[.gitmodules] > | [submodule "testing/jump"] > | path = testing/jump > | url = git://github.com/eschulte/jump.el.git > `---- > > > > > 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. > > > > Not that I can think of. > > > > > 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. > > > > Is it possible to simply ignore the jump submodule (maybe skip that > commit) and then move forward with bzr synchronization. There's no need > to include jump in the bzr repository as it's entirely optional and is > only needed for writing/using the test suite (which doesn't happen that > frequently anyways). > > If there is no way to skip that commit on the bzr-synchronization side, > it shouldn't be difficult to create an alternate git repository which > mirrors the main repo but skips the submodule commit. Once this is > setup the bzr repository could track this alternate git repository. > > Hope this helps -- Eric > > > > > - Memnon > > > > > > > > > > > > > > -- > Eric Schulte > http://cs.unm.edu/~eschulte/ > > > > End of Emacs-orgmode Digest, Vol 63, Issue 31 > ********************************************* >