Re: [O] From latest maint/master, no need to (require 'org-install): Lisp error
Rainer Stengele writes: > Actually I am confused - I did not quite understand - why do I no more > require 'org-install and also not 'org. Can you point me to some docs > about this? If you need anything at all, you now need to use (require 'org), regardless of whether it's the Org version that comes with Emacs (which has been using this in favor of org-install.el for some time) or from Git. However, you don't need any (require 'org) whatsoever if you don't happen to use customizations in your initialization file that require Org to be loaded already, since simply using any of the autoloaded functions will now arrange for the necesary files being loaded. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] [ANN] Editable HTML export of Org-mode files
Eric S Fraga writes: > Eric Schulte writes: > >> Hi, >> >> I've recently put together a web server which runs in Emacs and exports >> local Org-mode files to HTML in such a way that they may be edited from >> within a web browser with the edits saved to local files on disk. The >> code is available from github. > > Eric, > > I have been playing with this. I really like it! > Great, I'm happy its working for you, I've been using it myself and enjoying it. Hopefully now that it is ELPA installable it will be easier for more people to try it out. > > What I have been testing is how well it interacts with other CSS style > files. Some work better than others but, most importantly, they all > require adding the following: > > : #+STYLE: .raw-org { display: none;} > > to the individual org files so that the content displayed is only the > html generated by the export. There may be a better/easier way to > handle this, of course. > Yes, the above is needed to hide the raw Org-mode text until it is edited. You can customize the org-ehtml-client-style variable to set whatever CSS you like as the default. Similarly it should be fairly easy for anyone fluent in JavaScript to hack org-ehtml-client-js if they want to try different behavior. One of my main goals in writing org-ehtml was to keep things as small, simple and hackable as possible. > > More playing to be done... but I can see this being quite useful! It > works really nicely with firefox in combination with a browser plugin > which allows me to edit the text in the boxes using emacsclient (with > org mode enabled!). > Oh great, I used to use that same browser plugin, but for the last year or so I've gone whole hog and switched to using conkeror as my web browser. http://conkeror.org/ > > thanks (and to Nic as well for elnode), > eric Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [babel] howto debug #+call lines
Andreas Leha writes: > Hi all, > > I am getting different results from the evaluation of a source block and > the evaluation of a #+call line to that block. > > Therefore, my question: Is there an equivalent to > org-babel-expand-src-block (C-c C-v v) for #+call lines? > > Or more general: How do I debug #+call lines? > > Regards, > Andreas > Can you provide a minimal example? You could write a code block equivalent to the call line. E.g., #+call: foo(bar=1) is equivalent to #+begin_src emacs-lisp :var results=foo(bar=1) results #+end_src -- Eric Schulte http://cs.unm.edu/~eschulte
[O] [babel] howto debug #+call lines
Hi all, (seems like I am having trouble to post -- sorry if multiple copies of this end up on the list) I am getting different results from the evaluation of a source block and the evaluation of a #+call line to that block. Therefore, my question: Is there an equivalent to org-babel-expand-src-block (C-c C-v v) for #+call lines? Or more general: How do I debug #+call lines? Regards, Andreas
[O] Extend (org-shiftcontrolup) and (org-shiftcontroldown) with numeric arguments?
Hi! I wonder if (org-shiftcontrolup) and (org-shiftcontroldown) could be provided with the possibility to add a numeric argument. Point on CLOCK: [2012-12-09 So 09:00]--[2012-12-09 So 17:00] => 8:00 ^ I would like to be able to change the time span to today + 7 days: CLOCK: [2012-12-16 So 09:00]--[2012-12-16 So 17:00] => 8:00 This could easily be done with "C-7 C-S-up", butt cannot at the moment. Thoughts? Cheers, Rainer
[O] [babel] debug #+call lines
Hi all, I am getting different results from the evaluation of a source block itself and the evaluation of a #+call line to that block. Therefore, here is my question: Is there an equivalent to org-babel-expand-src-block (C-v C-v v) for call lines? Or how should I debug a #+call line? Regards, Andreas
[O] [babel] howto debug #+call lines
Hi all, I am getting different results from the evaluation of a source block and the evaluation of a #+call line to that block. Therefore, my question: Is there an equivalent to org-babel-expand-src-block (C-c C-v v) for #+call lines? Or more general: How do I debug #+call lines? Regards, Andreas
[O] [BUG] Parsing consecutive stars
Hi list, It looks like the stars parser has a problem with 2 consecutive stars, hence with bold in 2nd level headers. The following sums up all the relevant tests I performed. Only 3rd and 4th lines seem to be related, in a strange fashion, even, but I couldn't find anything else that would indicate lines not being independant. * Test *it* ! * *Test thouroughly* ! ** try deleting these : ** *** ** * ** *** ** ** Is *this* bold ? Note that anytime it is, editing the line gets the failure back. *** From here, it all *seems* to *works* *fine*. *** Only ** *here* it *doesn't !* *** *More* ** so *even*. I can try with text, it doesn't *change* ** *anything*. *** Darn. ** Even if I add many words it *fails* ! Hope ! ** Even if I add many words it only *fails* *once* ! But ** *sadly* it ** can *fail* *many times* ! *** If I try with *** *more* stars, it's totally *fine* It ** actually *** *helps*, *even* You *do* ** need * *a few*. But ** ** *two* is *enough* While constructing this, I was using (recent git version, and) (setq org-emphasis-regexp-components '(" \t('\"{" "- \t.,:!?;'\")}\\" " \t\r\n,\"'" "." 2)) but reverting to default with (setq org-emphasis-regexp-components '(" \t('\"{" "- \t.,:!?;'\")}\\" " \t\r\n,\"'" "." 1)) showed no improvement regarding the weird behavior. (I do imagine things could go a lot worse with hugher values, though ^_^) (problem raised on http://stackoverflow.com/questions/12736868/cant-use-bold-face-on-2nd-level-outline-in-emacs-org-mode)
Re: [O] Clocktable: Put summary line as table caption
Hello, "Sebastien Vauban" writes: > You're right. I also thought of that. But that concern is much more general > than for the clocktables: if any (future) back-end does not support captions > in his DNA, we will have to foresee a workaround in the export _anyway_, > something such as copying the text just before or after the figures, tables, > etc. Good point, indeed. >> I will commit it if there is no objection. > > None ;-) Applied. Thank you. Note: you don't need to mention "TINY CHANGE" since you signed the FSF papers already. Regards, -- Nicolas Goaziou
[O] Block-Agenda: Show whole entry
Hello, I'm trying to create an Agenda which will be printed / mailed daily. It should include the usual 'today' agenda and my shopping list. This shopping list is stored in an agenda file as a list with checkboxes. I want this list as the second block in my agenda. Is this possible? Cheers, Moritz Ulrich -- Moritz Ulrich pgpnBIMzBKJd8.pgp Description: PGP signature
[O] Bug: New Exporter macro expansion
Hello all, I've found a few issues with the new exporter (tested using org-e-latex and org-e-ascii) with regards to macro expansion on export. Using the minimal org file below with Org-mode version 7.9.2 (release_7.9.2-402-ge5e49e @ d:/Apps/Emacs/site-lisp/org/) certain macros do not expand as expected. #+begin_src org ,#+TITLE: Test ,#+author: testing ,#+macro: sample export this text ,#+macro: sample2 {{{sample}}} and this text ,#+macro: table | hello | goodbye | ,#+macro: table2 | hello | {{{sample}}} | ,* Sample headline {{{title}}} | Test |1 | | {{{TITLE}}} | {{{sample}}} | {{{table}}} {{{table2}}} #+end_src {{{title}}}, as well as {{{author}}} do not expand at all when exporting. In addition macros within table cells are treated as empty text. Regards, -- Jon
Re: [O] Some links no longer work
On 10/03/2012 07:19 PM, Simon Thum wrote: On 10/03/2012 03:09 PM, Giovanni Ridolfi wrote: Da: Simon Thum Inviato: Mercoledì 3 Ottobre 2012 14:45 Hi Simon, recently my UNC links stopped working; [...] I have links, say, [[\\server\share\some\dir\]] which (on win32) would open an explorer at the location. This is pretty handy; it is. However (dired-at-point "//myserver/dir") then C-x C-e at the end of the line is really a killer (provided you read dired's manual). Now, UNC links get me an error saying something like "file not found" right in emacs. cannot reproduce. [[\\myserver\dir]] here it works. I guess I'll retry with forward slashes - although it did not work for me without trailing backslash either. Thanks for the suggestion. I'll try tomorrow! Just to confirm it worked today, albeit after update. Cheers, Simon Org-mode version 7.9.1 (a99402facf8726 quite old: 17 Sept 2012 GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) of 2012-06-10 on MARVIN Tschüß, Giovanni
Re: [O] Bug:install: cannot stat ‘org-install.elc’
On Thursday 04 October 2012, 14:01:26, Nicolas Goaziou wrote: > AFAIU, this is a temporary fuse. As such, wouldn't it be useful to drop > a note (i.e. as a comment in the Makefile) reminding it and explaining > how to remove it when its time has come ? Actually, I would leave it in indefinately. There's just too many combinations of potentially old Org installations in load-path and the cost of keeping it is negligible. I've tested it locally by now and it does work fine. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] Bug:install: cannot stat ‘org-install.elc’
Hello, Achim Gratz writes: > Achim Gratz writes: >> One suggestion: I'd introduce an org-install.el that never gets compiled >> and only throws a warning if loaded. This will also help to defuse old >> copies of org-install that are maybe still present later in load-path. > > Here's a patch to that effect: This looks like a good idea. AFAIU, this is a temporary fuse. As such, wouldn't it be useful to drop a note (i.e. as a comment in the Makefile) reminding it and explaining how to remove it when its time has come ? Regards, -- Nicolas Goaziou
Re: [O] From latest maint/master, no need to (require 'org-install): Lisp error
Am 02.10.2012 17:39, schrieb Bastien: > Rainer Stengele writes: > >> Still complaining about org-version .. > > Dong! Fixed. Please pull again. > Thanks Bastien, works perfectly now. Actually I am confused - I did not quite understand - why do I no more require 'org-install and also not 'org. Can you point me to some docs about this? Rainer