Re: [O] git repository over http?
Jason Dunsmore writes: > If you clone via git://, it does some optimizations during the transfer, > whereas cloning via http:// does not. If I do a "git gc" on the repo, > it reduces the size of the repo on the server and the time to download > via http:// I'd suggest that the repo on the server should get a regular garbage collect (daily, perhaps via cron) and on each release an aggressive garbage collect. It will be much easier on the server (reduced traffic and fewer requests to serve). Not only is the size of the repo much larger than it needs to be, the server also has to deal with lots of small requests that can't be efficiently transferred. Cloning the repo via http protocol produces 190MByte on disk, a simple and fast 'git gc' gets that down to 63MByte, just like cloning via git protocol (ironically, the server will do that work on each clone as long as you do not do a garbage collect on the repo itself). An aggressive garbage collect takes a while longer, but reduces the size of the repo down to 44MByte. An http clone on repo.or.cz currently delivers 72MByte, so it appears they do a regular garbage collect (or it simply comes courtesy of mirroring). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
[O] tags filtering in weekly/daily agenda
Am I wrong, or is there no way to filter what is shown in the weekly/daily agenda view? I'm creating custom agendas with multiple blocks, and would like to apply the same tags/match filter to the daily agenda as I do to the TODO blocks below it. Can that be done? Eric
Re: [O] [PATCH] New function org-find-timestamps
Marc-Oliver Ihm writes: > By the way: There are surely official documentation standards, that I > could adhere for this. However, at present I cannot find them. Could > anyone provide me a pointer please ? Does the file doc/Documentation_Standards.org in the source distribution help at all? Failing that the Documentation node in the Elisp info manual has more general advice. There is also M-x checkdoc which can help check elisp doc strings. Phil
Re: [O] tags filtering in weekly/daily agenda
Eric Abrahamsen writes: > Am I wrong, or is there no way to filter what is shown in the > weekly/daily agenda view? I'm creating custom agendas with multiple > blocks, and would like to apply the same tags/match filter to the daily > agenda as I do to the TODO blocks below it. Can that be done? Hi Eric, The agenda filtering should be the same for weekly/daily and block agenda. I use persistent filtering which keeps the filter when you select other agenda views and I like this setting a lot. When I filter my block agenda view (with / TAB sometag RET) it applies to all of the sections in my block agenda. HTH, Bernt
Re: [O] Latex image placement (...again. H vs. h!)
On Sun, Aug 21, 2011 at 1:28 AM, Stefan Nobis wrote: > John Hendy writes: > >> Was just rediscovering how to properly get floats to drop in where I >> want them in LaTeX export (right where I say vs. where LaTeX thinks >> is convenient). > > Another way to tackle this problem may be to just not use floats. As > the name suggests, these construct is meant to let things float. :) > > If you want a figure or table to be placed at exactly the point where > you place it, why are you using a float environment? Most people > answer at this point, because they want the captions and all examples > with captions use the float environment. Thats because with captions > and in the general case it makes sense to let LaTeX find the right > place for these things. Huh. I didn't realize the captions triggered something than just using [[./path/to/image]] with attr_latex options passed. I just duplicated the same section and removed all captions as well as placement=[H] options and they exported right where I would have wanted them. That's interesting -- learned something new! > > If you want exact, controlled placements and also a caption, have a > look at the package 'caption' (version 3.1, author Axel > Sommerfeldt). Then you can get rid of floats and don't have to bother > with obscure placement rules. :) I'll definitely take a look at that. I may also just use descriptive intros prior to each picture, as that would do the same as a caption, I suppose. It's just weird to me that sometimes the floats don't drop until a later section, in which case I think that's definitely *too* late. Sure, if they dump at the end of Section 1.1, fine -- that's where they are discussed. But now they're showing up in 1.2? Thanks, John > > -- > Until the next mail..., > Stefan. >
Re: [O] Latex image placement (...again. H vs. h!)
> Hi John, > > I think of [h!] as "try really hard to place the float here" and [H] as > "place the float here regardless of the consequences." > Great way to put it! Thanks, John > All the best, > Tom > -- > Thomas S. Dye > http://www.tsdye.com >
Re: [O] Latex image placement (...again. H vs. h!)
On Sun, Aug 21, 2011 at 10:00 AM, John Hendy wrote: > On Sun, Aug 21, 2011 at 1:28 AM, Stefan Nobis wrote: >> John Hendy writes: >> >>> Was just rediscovering how to properly get floats to drop in where I >>> want them in LaTeX export (right where I say vs. where LaTeX thinks >>> is convenient). >> >> Another way to tackle this problem may be to just not use floats. As >> the name suggests, these construct is meant to let things float. :) >> >> If you want a figure or table to be placed at exactly the point where >> you place it, why are you using a float environment? Most people >> answer at this point, because they want the captions and all examples >> with captions use the float environment. Thats because with captions >> and in the general case it makes sense to let LaTeX find the right >> place for these things. > > Huh. I didn't realize the captions triggered something than just using > [[./path/to/image]] with attr_latex options passed. I just duplicated > the same section and removed all captions as well as placement=[H] > options and they exported right where I would have wanted them. That's > interesting -- learned something new! > >> >> If you want exact, controlled placements and also a caption, have a >> look at the package 'caption' (version 3.1, author Axel >> Sommerfeldt). Then you can get rid of floats and don't have to bother >> with obscure placement rules. :) > > I'll definitely take a look at that. I may also just use descriptive > intros prior to each picture, as that would do the same as a caption, > I suppose. It's just weird to me that sometimes the floats don't drop > until a later section, in which case I think that's definitely *too* > late. Sure, if they dump at the end of Section 1.1, fine -- that's > where they are discussed. But now they're showing up in 1.2? The placeins package offers a solution to this problem. Best, Ista > > > Thanks, > John > >> >> -- >> Until the next mail..., >> Stefan. >> > > -- Ista Zahn Graduate student University of Rochester Department of Clinical and Social Psychology http://yourpsyche.org
Re: [O] tags filtering in weekly/daily agenda
On 21.8.2011, at 15:17, Bernt Hansen wrote: > Eric Abrahamsen writes: > >> Am I wrong, or is there no way to filter what is shown in the >> weekly/daily agenda view? I'm creating custom agendas with multiple >> blocks, and would like to apply the same tags/match filter to the daily >> agenda as I do to the TODO blocks below it. Can that be done? This might be a problem with an older version of Org-mode, but we have no idea what your version is, Eric. - Carsten > > Hi Eric, > > The agenda filtering should be the same for weekly/daily and block > agenda. I use persistent filtering which keeps the filter when you > select other agenda views and I like this setting a lot. > > When I filter my block agenda view (with / TAB sometag RET) it applies > to all of the sections in my block agenda. > > HTH, > Bernt >
Re: [O] tags filtering in weekly/daily agenda
Hi Bernt and Carsten, Bernt Hansen wrote: > Eric Abrahamsen writes: > >> Am I wrong, or is there no way to filter what is shown in the weekly/daily >> agenda view? I'm creating custom agendas with multiple blocks, and would >> like to apply the same tags/match filter to the daily agenda as I do to the >> TODO blocks below it. Can that be done? > > The agenda filtering should be the same for weekly/daily and block agenda. I > use persistent filtering which keeps the filter when you select other agenda > views and I like this setting a lot. > > When I filter my block agenda view (with / TAB sometag RET) it applies to > all of the sections in my block agenda. Would it be difficult to have more filtering capabilities in the agenda views: more than on tags? Something like what C-a m does with todo keywords, but limited on what's currently displayed by the agenda, and which would be as easily accessible as the ! key binding is. Another nice addition would be to allow filtering on files, dynamically selecting one source by filtering on file name, and eventually on subtrees (something like the refiling path). Best regards, Seb -- Sebastien Vauban
Re: [O] Wishlist: allow range of table elements to be filled by sbe
Hi András, András Major writes: > Hi Eric, > >> sbe is just an elisp function which is called by the Org-mode >> spreadsheet's function evaluation mechanisms. The spreadsheet does not >> allow for insertion of results into multiple cells and thus neither does >> the use of sbe. > > Hmmm. It appears that one can make sbe set multiple cells in the > table -- simply make your code block output multiple results separated > by "|" and set ":results table". This, however, also shifts any > existing cells in the table, thus increasing the number of columns, > instead of just overwriting the given number of cells. > >> I would recommend a solution like the following, which >> reads the /entire/ table into a code block, and writes the results out >> in place. > > This isn't always practical. In the case of the Org document I'm > writing at the moment, the computation is rather expensive, and my > goal is that you can edit a row in the table and run the calculation > just for that row to see the result. Updating the entire table at > once would be much too slow. > Unfortunately I don't believe there is a good solution to this problem. > >> Every time the code block is evaluated multiple cells in the table are >> changed. To only set specific table values use of the `setf' macro >> would probably be more appropriate. > > How is setf used? I haven't found it in the documentation. > Setf can be used to update internal parts of a data structure, for example. #+results: this-is-another-table | 0 | 0 | 0 | | 0 | 0 | 0 | | 0 | 0 | 0 | #+source: this-is-another-table #+begin_src emacs-lisp :var table=this-is-another-table (setf (nth 1 table) '(2 2 2)) table #+end_src executing the code block will set the second row of the table to all twos. Hope this helps -- Eric > > András > > > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Bug: babel: results switch (output vs. value) has no or wrong effect for sh source block [7.7 (release_7.7.107.g7a82)]
András Major writes: > Hi Eric, > >> If we did return the value of shell scripts then ":results value" would >> almost always simply return 0 (or possibly an error message). For this >> reason shell code blocks do not implement value returns, but rather will >> always collect results from STDOUT. > > I think that this unnecessarily throws away potentially useful > functionality. Example: I want to fill a table with data such that > the value of a cell depends on whether a file (whose path is specified > by another cell, for instance) exists or not. This would be most > easily done using an sh block which returns a numeric exit code. I > don't see a reason for making clandestine exceptions to the rules in > the manual and strongly suggest that the output and value options be > honoured for every language. > I do see your point, and I agree that consistent behavior between languages is of paramount importance. In fact I began working on implementing the return of error codes from shell code blocks, however I ran into the following issue. For every language, when an error is thrown babel tries to open an error buffer holding the contents of the error message. This is very useful for debugging code which lives inside of a code block -- a process which can otherwise be difficult because of the extra layer of indirection babel interposes between the programmer and the codes execution. In order to return exit codes from shell blocks babel would have to silently ignore errors in shell blocks. I would lean towards thinking that passing along error messages is more important than returning error codes, but if the community thinks differently I'm happy to change the ob-sh behavior. Unfortunately it seems that in either case the sh code blocks will need to be different than other languages either in its handling of errors or of return values. This is unavoidable due to the overloading of return values in the shell as error indicators. > > In order not to break existing Org files, I would suggest that the > default choice between value and output (when not explicitly > specified) depend on the language. With this functionality, sh code > blocks that don't specify ":results output" will still work as they > did before. > I agree, if we go this route this is the way to do it. Best -- Eric > > András > > > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Bug: Babel: haskell :results options output and value work contrary to docs [7.7 (release_7.7.107.g7a82)]
András Major writes:
> Here's another one: In a haskell code, the :results options value and
> output both work erroneously. "value" returns the output, "output"
> returns nothing into the :results block.
>
> Example code:
>
> #+begin_src haskell :results value
> putStrLn "hello"
> #+end_src
>
> #+results:
> : hello
>
> #+begin_src haskell :results output
> putStrLn "hello"
> #+end_src
>
> #+results:
>
> #+begin_src haskell :results value
> import System.IO
> openFile "doesNotExist.ppt" ReadMode
> #+end_src
>
> #+results:
> : Prelude System.IO> *** Exception: doesNotExist.ppt: openFile: does
> not exist (No such file or directory)
>
> #+begin_src haskell :results output
> import System.IO
> openFile "doesNotExist.ppt" ReadMode
> #+end_src
>
> #+results:
>
>
> This just isn't right, is it?
>
No, the current behavior is not right.
These language specific files are developed as needed, and I don't
believe that ob-hsakell has seen much use up to this point. If anyone
would submit a patch to add correct value/output behavior to ob-haskell
I would be very happy to apply it.
Thanks -- Eric
>
> András
>
>
>
> Emacs : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
> of 2010-12-11 on raven, modified by Debian
> Package: Org-mode version 7.7 (release_7.7.107.g7a82)
>
> current state:
> ==
> (setq
> org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
> org-speed-command-hook '(org-speed-command-default-hook
> org-babel-speed-command-hook)
> org-babel-load-languages '((asymptote . t) (ditaa . t) (dot . t) (gnuplot .
> t)
> (haskell . t) (latex . t) (octave . t) (R . t)
> (ruby . t) (scheme . t) (sh . t))
> org-metaup-hook '(org-babel-load-in-session-maybe)
> org-after-todo-state-change-hook '(org-clock-out-if-current)
> org-babel-tangle-lang-exts '(("ruby" . "rb") ("latex" . "tex")
> ("haskell" . "hs") ("asymptote" . "asy")
> ("emacs-lisp" . "el"))
> org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup)
> org-export-latex-format-toc-function 'org-export-latex-format-toc-default
> org-tab-first-hook '(org-hide-block-toggle-maybe
> org-src-native-tab-command-maybe
> org-babel-hide-result-toggle-maybe)
> org-src-mode-hook '(org-src-babel-configure-edit-buffer
>org-src-mode-configure-edit-buffer)
> org-confirm-shell-link-function 'yes-or-no-p
> org-export-first-hook '(org-beamer-initialize-open-trackers)
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-babel-pre-tangle-hook '(save-buffer)
> org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
> org-cycle-show-empty-lines
> org-optimize-window-after-visibility-change)
> org-export-preprocess-before-normalizing-links-hook
> '(org-remove-file-link-modifiers)
> org-mode-hook '(#[nil "\300\301\302\303\304$\207"
> [org-add-hook change-major-mode-hook org-show-block-all
> append local]
> 5]
>#[nil "\300\301\302\303\304$\207"
> [org-add-hook change-major-mode-hook
> org-babel-show-result-all append local]
> 5]
>org-babel-result-hide-spec org-babel-hide-all-hashes)
> org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
> org-babel-execute-safely-maybe)
> org-confirm-elisp-link-function 'yes-or-no-p
> org-export-interblocks '((lob org-babel-exp-lob-one-liners)
> (src org-babel-exp-inline-src-blocks))
> org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
> org-occur-hook '(org-first-headline-recenter)
> org-from-is-user-regexp nil
> org-export-preprocess-before-selecting-backend-code-hook
> '(org-beamer-select-beamer-code)
> org-confirm-babel-evaluate nil
> org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
> org-beamer-auto-fragile-frames
> org-beamer-place-default-actions-for-lists)
> org-metadown-hook '(org-babel-pop-to-session-maybe)
> org-export-blocks '((src org-babel-exp-src-block nil)
>(comment org-export-blocks-format-comment t)
>(ditaa org-export-blocks-format-ditaa nil)
>(dot org-export-blocks-format-dot nil))
> )
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] result of code evaluation
Henri-Paul Indiogine writes: > Greetings! > > I have another question regarding the output of the bash script. I > have a bunch of echo statements. org-mode outputs now everything in a > table. Is it possible to suppress this and have just plain lines? > That was the behavior with a simple script. > Yes, the ":results scalar" header argument is what you want. #+begin_src sh :results scalar echo 1 echo 2 echo 3 #+end_src #+results: : 1 : 2 : 3 Best -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Bug: Babel: haskell code evaluation inconsistency [7.7 (release_7.7.160.g3e33)]
Major A writes:
> Hi again,
>
> I want to use haskell code blocks in order to evaluate them. The
> problem is that, depending on what haskell interpreters are installed
> on the computer, Babel will call a different interpreter to evaluate
> the code with. Also, the haskell interpreter interface appears to be
> highly stateful and unreliable.
>
Currently inf-haskell is used for all evaluation, so Babel inherits both
its functionality and its weaknesses. It seems that it would be
worthwhile to add non-session evaluation to haskell, and possibly a way
to specify which engine (hugs or ghci) is used in interactive
evaluation, presumably inf-haskell exports some way to make this
specification.
I personally don't have time to make these changes right now, but I'd be
happy to provide guidance and answer questions to anyone who wanted to
try to submit a patch. Also, there are a number of files which can
serve as examples of how to compile and execute code with Babel e.g.,
ob-java.el and ob-C.el.
>
> Here's an example -- ghc6 is installed, but not hugs:
>
> #+begin_src haskell :results output
> import System.IO
> openFile "doesNotExist.ppt" ReadMode
> #+end_src
>
> #+results:
> : Loading package ghc-prim ... linking ... done.
> : Loading package integer-gmp ... linking ... done.
> : Loading package base ... linking ... done.
>
> The interesting thing is that this output only occurs on the first run
> of the code -- if I hit C-cC-c again, the #+results: section will be
> empty.
>
> Now the same source, with hugs installed in addition to ghc6 -- the
> source block is the same, but the output is very different:
>
> #+results:
> : Type :? for help
> : ERROR - Syntax error in expression (unexpected keyword "import")
>
> Again, if I press C-cC-c again, the first line of output ("Type :? for
> help") is no longer present.
>
> This is what I suggest:
>
> - Do away with "haskell" as the keyword for haskell code blocks, just
> like graphviz blocks use "dot" instead of simply "graphviz".
>
> - Introduce new keywords -- I propose at least "runghc", "ghci", and
> "hugs". This is important since there are significant source-level
> differences (see above) between hugs and ghc and even between the
> compiler and interpreter from the same project (ghc and ghci).
> Without these, the progammer will never be able to predict how the
> code is evaluated and which compiler or interpreter they must code
> for.
>
> - Make sure the incorporation of the output or the value is done
> correctly (also see my previous bug report for this).
>
I would prefer to keep haskell as the source block type if only so that
the blocks are fontified with haskell-mode. However something like an
:engine or :compiler keyword could be used to specify ghc or hugs. The
other suggested changes seem like good ideas.
Best -- Eric
>
> Enough for today,
>
> András
>
>
>
> Emacs : GNU Emacs 23.3.1 (i486-pc-linux-gnu, GTK+ Version 2.24.3)
> of 2011-04-10 on raven, modified by Debian
> Package: Org-mode version 7.7 (release_7.7.160.g3e33)
>
> current state:
> ==
> (setq
> org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
> org-speed-command-hook '(org-speed-command-default-hook
> org-babel-speed-command-hook)
> org-babel-load-languages '((asymptote . t) (ditaa . t) (dot . t) (gnuplot .
> t) (haskell . t) (latex . t) (octave . t)
> (R . t) (ruby . t) (scheme . t) (sh
> . t))
> org-metaup-hook '(org-babel-load-in-session-maybe)
> org-after-todo-state-change-hook '(org-clock-out-if-current)
> org-babel-tangle-lang-exts '(("ruby" . "rb") ("latex" . "tex") ("haskell" .
> "hs") ("asymptote" . "asy")
> ("emacs-lisp" . "el"))
> org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup)
> org-export-latex-format-toc-function 'org-export-latex-format-toc-default
> org-tab-first-hook '(org-hide-block-toggle-maybe
> org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe)
> org-src-mode-hook '(org-src-babel-configure-edit-buffer
> org-src-mode-configure-edit-buffer)
> org-confirm-shell-link-function 'yes-or-no-p
> org-export-first-hook '(org-beamer-initialize-open-trackers)
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-blank-before-new-entry nil
> org-babel-pre-tangle-hook '(save-buffer)
> org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
> org-cycle-show-empty-lines
> org-optimize-window-after-visibility-change)
> org-export-preprocess-before-normalizing-links-hook
> '(org-remove-file-link-modifiers)
> org-mode-hook '(#[nil "\300\301\302\303\304$\207" [org-add-hook
> change-major-mode-hook org-show-block-all append local]
> 5]
>#[nil "\300\301\302\303\304$\207"
> [org-add-hook change-major-mode-hook
> org-babel-show-result-all append local] 5]
>
Re: [O] BUG: example/src blocks and latex export
Bastien writes:
> Hi Nick,
>
> Nick Dokos writes:
>
>> * foo
>>
>> Verbiage to begin the paragraph
>> #+begin_src shell
>> get-config.py var section [section ...]
>> #+end_src
>> and verbiage to end the same paragraph.
>>
>> * bar
>>
>> Verbiage to begin the paragraph
>> #+begin_example
>> get-config.py var section [section ...]
>> #+end_example
>> and verbiage to end the same paragraph.
>
> I tested your patch with the example above and I get this:
>
> ,
> | Verbiage to begin the paragraph
> |
> | \lstset{language=shell}
> | \begin{lstlisting}
> | get-config.py var section [section ...]
> | \end{lstlisting}
> |
> | and verbiage to end the same paragraph.
> | \section*{bar}
> | \label{sec-2}
> |
> |
> | Verbiage to begin the paragraph
> |
> | \begin{verbatim}
> | get-config.py var section [section ...]
> | \end{verbatim}
> | and verbiage to end the same paragraph.
> `
>
> It looks better than the current export (less white lines) but still
> has a problem with the first "and verbiage..." being indented.
>
> Is this intentional? Or do you want the same behavior for #+begin_src
> and #+begin_example?
>
> In overall, I think number of white lines should be the same in the Org
> source file and in the LaTeX exported file, so a patch here is welcome.
> But maybe I misunderstood something in Eric's reply.
>
I had misread Nicks first email and thus my reply made no sense. I've
applied this patch as it seems to be a definite improvement.
Thanks! -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] BUG: example/src blocks and latex export
Nick Dokos writes:
> Bastien wrote:
>
>> Hi Nick,
>>
>> Nick Dokos writes:
>>
>> > * foo
>> >
>> > Verbiage to begin the paragraph
>> > #+begin_src shell
>> > get-config.py var section [section ...]
>> > #+end_src
>> > and verbiage to end the same paragraph.
>> >
>> > * bar
>> >
>> > Verbiage to begin the paragraph
>> > #+begin_example
>> > get-config.py var section [section ...]
>> > #+end_example
>> > and verbiage to end the same paragraph.
>>
>> I tested your patch with the example above and I get this:
>>
>> ,
>> | Verbiage to begin the paragraph
>> |
>> | \lstset{language=shell}
>> | \begin{lstlisting}
>> | get-config.py var section [section ...]
>> | \end{lstlisting}
>> |
>> | and verbiage to end the same paragraph.
>> | \section*{bar}
>> | \label{sec-2}
>> |
>> |
>> | Verbiage to begin the paragraph
>> |
>> | \begin{verbatim}
>> | get-config.py var section [section ...]
>> | \end{verbatim}
>> | and verbiage to end the same paragraph.
>> `
>>
>> It looks better than the current export (less white lines) but still
>> has a problem with the first "and verbiage..." being indented.
>>
>> Is this intentional? Or do you want the same behavior for #+begin_src
>> and #+begin_example?
>>
>> In overall, I think number of white lines should be the same in the Org
>> source file and in the LaTeX exported file, so a patch here is welcome.
>> But maybe I misunderstood something in Eric's reply.
>>
>
> So here's another patch to get rid of some more newlines, these ones after
> a listings or minted environment. I tried both with the previously posted file
> and setting org-export-latex-listings to t or 'minted. AFAICT, it works as it
> should and should not break anything else, but... This is to be applied on top
> of the previous one (and it's still very much a trial balloon).
>
This seems like a logical extension of the previous patch, I've just
applied this as well.
Thanks Again -- Eric
>
> BTW, the defcustom of org-export-latex-listings seems to be outdated:
> custom thinks it's a boolean, but it can now take at least one more value
> (minted - see the docstring).
>
> Thanks,
> Nick
>
> From 5337cbb0669c6b05170190ec1e5751bdcf132d87 Mon Sep 17 00:00:00 2001
> From: Nick Dokos
> Date: Fri, 19 Aug 2011 18:36:50 -0400
> Subject: [PATCH 2/2] Get rid of gratuitous newline after listing/minted
> environment.
>
>
> Signed-off-by: Nick Dokos
> ---
> lisp/org-exp.el |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lisp/org-exp.el b/lisp/org-exp.el
> index a2a2fb3..f795fbd 100644
> --- a/lisp/org-exp.el
> +++ b/lisp/org-exp.el
> @@ -2689,11 +2689,11 @@ INDENT was the original indentation of the block."
> (format "\\begin{%s}\n%s\\end{%s}\n"
> custom-environment rtn custom-environment))
> (listings-p
> -(format "\\begin{%s}\n%s\\end{%s}\n"
> +(format "\\begin{%s}\n%s\\end{%s}"
> "lstlisting" rtn "lstlisting"))
> (minted-p
> (format
> - "\\begin{minted}[%s]{%s}\n%s\\end{minted}\n"
> + "\\begin{minted}[%s]{%s}\n%s\\end{minted}"
> (mapconcat #'make-option-string
> org-export-latex-minted-options ",")
> backend-lang rtn)))
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] [PATCH] Documentation of Babel header arguments
t...@tsdye.com (Thomas S. Dye) writes:
> Add a line to indicate header arguments are lowercase.
>
Applied, Thanks Tom -- Eric
>
> From 4a8719c9e7f95fa76041077dfaf0f5d21241517d Mon Sep 17 00:00:00 2001
> From: Tom Dye
> Date: Sat, 20 Aug 2011 06:48:35 -1000
> Subject: [PATCH] * doc/org.texi: Added a line to specify that header
> arguments are lowercase.
>
> ---
> doc/org.texi |3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/doc/org.texi b/doc/org.texi
> index f0a363b..fa051d0 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -12158,7 +12158,8 @@ evaluation of the @code{factorial} code block.
>
> @node Specific header arguments, , Using header arguments, Header arguments
> @subsection Specific header arguments
> -The following header arguments are defined:
> +Header arguments consist of an initial colon followed by the name of the
> +argument in lowercase letters. The following header arguments are defined:
>
> @menu
> * var:: Pass arguments to code blocks
> --
> 1.7.1
>
>
> All the best,
> Tom
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] [babel] [bug] inline src_R breaks downstream src block
Bastien writes:
> Hi Charles,
>
> yes, there are some problems with parsing inline source blocks.
> Stephen also reported that these colon lines
>
> : were $\beta_2$ = src_R{round(out3$coef[3], 4)}
> : and $\beta_3$ = src_R{round(out3$coef[4], 4)}
>
> where not exporting correctly... Eric, can you have a look at
> these problems?
>
> Thanks!
>
It will probably be a couple of days before I have sufficient time to
address these issues, but rest assured it is only my TODO list.
Thanks -- Eric
>
> "Charles C. Berry" writes:
>
>> ,
>> | | * inline code block example
>> | | | AAA
>> | blah blah src_R[:results output]{cat(rnorm(2))}
>> | CC
>> | #+begin_src R :eval never :exports none
>> | 1+2
>> | a <- b + c
>> | xyz
>> | #+end_src
>> |
>> `
>>
>>
>> When I run C-c C-e A y, I get a buffer that misses the 'DDD...' line.
>>
>> When I run C-c C-e L y, I get a buffer that ends like this:
>>
>>
>> | AAA
>> | blah blah \texttt{-1.172165 -0.5324113}
>> | CC
>> | \begin{src}R DDD
>> | | \end{document}
>> `
>>
>> More complicated examples exhibit other problems, I speculate that
>> parsing the inline src_R and setting up to find the next
>> #+begin_src...#+end_src instance is what has gone wrong.
>>
>> FWIW, changing the :exports header to 'code' seems to give correct
>> results
>>
>> Also, placing a dummy example like this:
>>
>> ,
>> | #+begin_example
>> | #+end_example
>> `
>>
>> after the src_R line produces correct results.
>>
>> Chuck
>>
>>
>> Charles C. BerryDept of Family/Preventive
>> Medicine
>> cbe...@tajo.ucsd.edu UC San Diego
>> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>>
>>
>>
>>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] Help confirming odt->doc bug (Was Re: [odt] User-visible improvements)
> This addition seems to be bearing fruit immediately. I just reported a > problematic behaviour with org->odt->doc conversion in LibreOffice > mailing list. See > > http://thread.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/14739 > > I am using OpenOffice.org-3.2.1 (OOO20m18/Build:9502). > Filed as https://bugs.freedesktop.org/show_bug.cgi?id=40272 (CCing the list mostly for my own later reference) --
[O] C-RET in plain lists
Hello, just starting out with emacs org-mode (I'm going through the compact guide). I'm wondering, is it possible to make C-RET (org-insert-heading-respect-content) "work" also on plain lists? i.e. make it insert a new list item of the same level *after* the sub-list. what I'm trying to do is this: I have a such nested list - powers of 1: 1. 1 2. 1 3. 1 4. and so on - powers of 3: 1. 3 2. 9 3. 27 4. and so on and I'd like to add a "powers of 2" entry in the middle... If C-RET worked like in headings I could place the cursor on "powers of 1" and do that, but it doesn't. thanks for any help, renato
Re: [O] C-RET in plain lists
Hello, Renato writes: > Hello, just starting out with emacs org-mode (I'm going through the > compact guide). I'm wondering, is it possible to make C-RET > (org-insert-heading-respect-content) "work" also on plain lists? Short answer: no. C-RET should be able to operate on headlines even in the middle of the list. > what I'm trying to do is this: I have a such nested list > >- powers of 1: >1. 1 >2. 1 >3. 1 >4. and so on >- powers of 3: >1. 3 >2. 9 >3. 27 >4. and so on > > and I'd like to add a "powers of 2" entry in the middle... If C-RET > worked like in headings I could place the cursor on "powers of 1" and > do that, but it doesn't. Move to the beginning of the line at "powers of 3" and use M-RET. Regards, -- Nicolas Goaziou
Re: [O] Org errors while building agenda: (void-function org-hh:mm-string-to-minutes)
Bastien writes: Hi Bastien, >> commit 8c3ecbe39a0c99e3724246d1eb460495a53721b6 >> Author: Bastien Guerry >> Date: Wed Aug 17 16:08:02 2011 +0200 >> >> Move three functions and add appropriate require/declarations. >> >> * org-clock.el (org-duration-string-to-minutes) >> (org-minutes-to-hh:mm-string, org-hh:mm-string-to-minutes): >> Move from org.el. >> >> has broken my agenda. > > I've reverted this commit. > > I first thought `org-duration-string-to-minutes' and associated > variables and functions would better fit into org-clock.el, but I now > see they are of more general purpose. Thanks a lot! Tassilo
Re: [O] [babel] [bug] inline src_R breaks downstream src block
I've just pushed up a change to org-exp-blocks which should fix Charles'
original problem related to conflict between inline and regular code
blocks. Please let me know if this problem persists in the latest git
HEAD.
Thanks -- Eric
Eric Schulte writes:
> Bastien writes:
>
>> Hi Charles,
>>
>> yes, there are some problems with parsing inline source blocks.
>> Stephen also reported that these colon lines
>>
>> : were $\beta_2$ = src_R{round(out3$coef[3], 4)}
>> : and $\beta_3$ = src_R{round(out3$coef[4], 4)}
>>
>> where not exporting correctly... Eric, can you have a look at
>> these problems?
>>
>> Thanks!
>>
>
> It will probably be a couple of days before I have sufficient time to
> address these issues, but rest assured it is only my TODO list.
>
> Thanks -- Eric
>
>>
>> "Charles C. Berry" writes:
>>
>>> ,
>>> | | * inline code block example
>>> | | | AAA
>>> | blah blah src_R[:results output]{cat(rnorm(2))}
>>> | CC
>>> | #+begin_src R :eval never :exports none
>>> | 1+2
>>> | a <- b + c
>>> | xyz
>>> | #+end_src
>>> |
>>> `
>>>
>>>
>>> When I run C-c C-e A y, I get a buffer that misses the 'DDD...' line.
>>>
>>> When I run C-c C-e L y, I get a buffer that ends like this:
>>>
>>>
>>> | AAA
>>> | blah blah \texttt{-1.172165 -0.5324113}
>>> | CC
>>> | \begin{src}R DDD
>>> | | \end{document}
>>> `
>>>
>>> More complicated examples exhibit other problems, I speculate that
>>> parsing the inline src_R and setting up to find the next
>>> #+begin_src...#+end_src instance is what has gone wrong.
>>>
>>> FWIW, changing the :exports header to 'code' seems to give correct
>>> results
>>>
>>> Also, placing a dummy example like this:
>>>
>>> ,
>>> | #+begin_example
>>> | #+end_example
>>> `
>>>
>>> after the src_R line produces correct results.
>>>
>>> Chuck
>>>
>>>
>>> Charles C. BerryDept of Family/Preventive
>>> Medicine
>>> cbe...@tajo.ucsd.eduUC San Diego
>>> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>>>
>>>
>>>
>>>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] [babel] [bug] inline src_R breaks downstream src block
Eric Schulte writes:
> I've just pushed up a change to org-exp-blocks which should fix Charles'
> original problem related to conflict between inline and regular code
> blocks. Please let me know if this problem persists in the latest git
> HEAD.
>
> Thanks -- Eric
>
> Eric Schulte writes:
>
>> Bastien writes:
>>
>>> Hi Charles,
>>>
>>> yes, there are some problems with parsing inline source blocks.
>>> Stephen also reported that these colon lines
>>>
>>> : were $\beta_2$ = src_R{round(out3$coef[3], 4)}
>>> : and $\beta_3$ = src_R{round(out3$coef[4], 4)}
>>>
Inline source blocks like those above should now also be exporting as
expected.
Cheers -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] C-RET in plain lists
On Sun, 21 Aug 2011 20:58:53 +0200 Nicolas Goaziou wrote: > Move to the beginning of the line at "powers of 3" and use M-RET. thanks, that satisfies my needs cheers renato
Re: [O] tags filtering in weekly/daily agenda
On Sun, Aug 21 2011, Carsten Dominik wrote:
> On 21.8.2011, at 15:17, Bernt Hansen wrote:
>
>> Eric Abrahamsen writes:
>>
>>> Am I wrong, or is there no way to filter what is shown in the
>>> weekly/daily agenda view? I'm creating custom agendas with multiple
>>> blocks, and would like to apply the same tags/match filter to the daily
>>> agenda as I do to the TODO blocks below it. Can that be done?
>
> This might be a problem with an older version of Org-mode, but we have no idea
> what your version is, Eric.
>
> - Carsten
Ah, sorry -- stupid oversight: Org-mode version 7.7
(release_7.7.160.g3e33). Should be yesterday.
I'm using plain elisp to create custom agenda views (the customize
interface is hard to look at). Here's the simplest thing I started with:
(setq org-agenda-custom-commands
'(("p" "Personal agenda plus mail"
((agenda "-CATEGORY=\"pr\"")
(tags "TODO=\"EMAIL\"-CATEGORY=\"pr\"")
The "tags" section filters correctly, but the agenda doesn't. This
probably isn't the correct way to do it, but the examples in the
manual don't show how. Bernt's pointer about dynamic filtering of an
existing agenda view works, of course, but I'm trying to have it start
out filtered.
Thanks!
Eric
[O] Not merging org-lparse, org-xhtml & org-odt to the core
Bastien I have made a decision not to merge org-lparse, org-xhtml & org-odt in to Orgmode core. It is a very difficult decision for me to take considering that I had put all my heart in to it. (Btw, this decision has nothing to with me not having enough time at hand.) I leave it up to the community on what would be the best place to "host" this software. I am a signed contributor and all the above files have their copyright assigned to FSF and the files are distributed under the same license as Emacs itself. I would like to emphasize that I am the SOLE AUTHOR of the above files. (More specifically, there is literally none of the changes made by Lennart Borgman had made it's way in to the final product. Though it retains some of the "influence" of his involvement.) At some point in time I would like to make a formal submission to GNU ELPA to host this package as a personal initiative. Not having this package in Orgmode core would also help me move fast in in having my files in a distribution head. I will happily fix any bug reports that come by way. I will be lot less aggressive in adding features though. I will not be making anymore commits to the Orgmode repo and I am switching my development to a private branch. Jambunathan K. --
Re: [O] [babel] [bug] inline src_R breaks downstream src block
On Sun, 21 Aug 2011, Eric Schulte wrote:
I've just pushed up a change to org-exp-blocks which should fix Charles'
original problem related to conflict between inline and regular code
blocks. Please let me know if this problem persists in the latest git
HEAD.
Just updated to
Org-mode version 7.7 (release_7.7.167.gfceb.dirty)
And I get
[...]
Code block evaluation complete.
if: Args out of range: -1, -1
after typing C-c C-e A RET y
:-(
Chuck
Thanks -- Eric
Eric Schulte writes:
Bastien writes:
Hi Charles,
yes, there are some problems with parsing inline source blocks.
Stephen also reported that these colon lines
: were $\beta_2$ = src_R{round(out3$coef[3], 4)}
: and $\beta_3$ = src_R{round(out3$coef[4], 4)}
where not exporting correctly... Eric, can you have a look at
these problems?
Thanks!
It will probably be a couple of days before I have sufficient time to
address these issues, but rest assured it is only my TODO list.
Thanks -- Eric
"Charles C. Berry" writes:
,
| | * inline code block example
| | | AAA
| blah blah src_R[:results output]{cat(rnorm(2))}
| CC
| #+begin_src R :eval never :exports none
| 1+2
| a <- b + c
| xyz
| #+end_src
|
`
When I run C-c C-e A y, I get a buffer that misses the 'DDD...' line.
When I run C-c C-e L y, I get a buffer that ends like this:
| AAA
| blah blah \texttt{-1.172165 -0.5324113}
| CC
| \begin{src}R DDD
| | \end{document}
`
More complicated examples exhibit other problems, I speculate that
parsing the inline src_R and setting up to find the next
#+begin_src...#+end_src instance is what has gone wrong.
FWIW, changing the :exports header to 'code' seems to give correct
results
Also, placing a dummy example like this:
,
| #+begin_example
| #+end_example
`
after the src_R line produces correct results.
Chuck
Charles C. BerryDept of Family/Preventive Medicine
cbe...@tajo.ucsd.eduUC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Charles C. BerryDept of Family/Preventive Medicine
cbe...@tajo.ucsd.eduUC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
Re: [O] tags filtering in weekly/daily agenda
"Sebastien Vauban" writes: > Hi Bernt and Carsten, > > Bernt Hansen wrote: >> Eric Abrahamsen >> writes: >> >>> Am I wrong, or is there no way to filter what is shown in the weekly/daily >>> agenda view? I'm creating custom agendas with multiple blocks, and would >>> like to apply the same tags/match filter to the daily agenda as I do to the >>> TODO blocks below it. Can that be done? >> >> The agenda filtering should be the same for weekly/daily and block agenda. I >> use persistent filtering which keeps the filter when you select other agenda >> views and I like this setting a lot. >> >> When I filter my block agenda view (with / TAB sometag RET) it applies to >> all of the sections in my block agenda. > > Would it be difficult to have more filtering capabilities in the agenda views: > more than on tags? Something like what C-a m does with todo keywords, but > limited on what's currently displayed by the agenda, and which would be as > easily accessible as the ! key binding is. > > Another nice addition would be to allow filtering on files, dynamically > selecting one source by filtering on file name, and eventually on subtrees > (something like the refiling path). Hi Seb, I am just a user here... I'm sure this is possible in elisp but I have no idea how complicated it would be to implement -- I expect it's probably non-trivial though. I use file and subtree restrictions before filtering to limit the returned agenda results (and improve the search speed) Regards, Bernt
[O] archive problem [7.7 (release_7.7.167.gfceb)]
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.
when I do C-c C-x C-a to archive a entry in the agenda view i get the
following back trace
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match("^/tmp_mnt/" nil)
abbreviate-file-name(nil)
org-archive-subtree()
org-agenda-archive-with(org-archive-subtree)
org-agenda-archive-default()
call-interactively(org-agenda-archive-default nil nil)
--
Yagnesh
--
Emacs : GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.18.9)
of 2011-08-22 on amur
Package: Org-mode version 7.7 (release_7.7.167.gfceb)
current state:
==
(setq
org-agenda-tags-todo-honor-ignore-options t
org-export-preprocess-before-selecting-backend-code-hook
'(org-beamer-select-beamer-code)
org-tab-first-hook '(yas/org-very-safe-expand org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-agenda-diary-file "~/git/org/diary.org"
org-agenda-skip-timestamp-if-done t
org-occur-hook '(org-first-headline-recenter)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-export-preprocess-before-normalizing-links-hook
'(org-remove-file-link-modifiers)
org-confirm-shell-link-function 'yes-or-no-p
org-export-latex-emphasis-alist '(("*" "\\textbf{%s}" nil) ("/"
"\\emph{%s}" nil)
("_" "\\underline{%s}" nil)
("+" "\\texttt{%s}" nil) ("=" "\\verb=%s=" nil)
("~" "\\verb~%s~" t) ("@" "\\alert{%s}" nil))
org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
org-beamer-auto-fragile-frames
org-beamer-place-default-actions-for-lists)
org-emphasis-alist '(("*" bold "" "") ("/" italic "" "")
("_" underline ""
"")
("=" org-code "" "" verbatim)
("~" org-verbatim "" "" verbatim)
("+" (:strike-through t) "" "")
("@" org-warning "" ""))
org-special-ctrl-a/e t
org-agenda-todo-ignore-scheduled t
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-agenda-skip-scheduled-if-done t
org-agenda-custom-commands '(("w" "Works for weekend" tags
"@night|@weekend!"
((org-agenda-overriding-header "weekend works")))
("d" "At WORK" tags "@day!"
((org-agenda-overriding-header "at Work")))
("n" "Evening" tags "@night!"
((org-agenda-overriding-header "Night time")))
("r" "Refile New Notes and Tasks" tags
"LEVEL=2+REFILE"
((org-agenda-overriding-header "Tasks to Refile")))
("N" "Next" tags-todo "/!NEXT")
("A" "Tasks to be Archived" tags
"LEVEL=2-REFILE/DONE|CANCELLED")
)
org-default-notes-file "~/git/org/refile.org"
org-todo-keyword-faces '(("TODO" :foreground "red" :weight bold)
("NEXT" :foreground "blue" :weight bold)
("DONE" :foreground "forest green" :weight bold)
("WAITING" :foreground "yellow" :weight bold)
("SOMEDAY" :foreground "goldenrod" :weight bold)
("CANCELLED" :foreground "orangered" :weight bold)
("OPEN" :foreground "magenta" :weight bold)
("CLOSED" :foreground "forest green" :weight bold))
org-agenda-include-diary t
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup)
org-mode-hook '(#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-show-block-all append
local]
5]
#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-babel-show-result-all
append local]
5]
org-babel-result-hide-spec org-babel-hide-all-hashes
(lambda nil (make-variable-buffer-local (quote yas/trigger-key))
(setq yas/trigger-key [tab])
(add-to-list (quote org-tab-first-hook)
(quote yas/org-very-safe-expand))
(define-key yas/keymap [tab] (quote yas/next-field))
(flyspell-mode 1))
)
org-refile-targets '((org-agenda-files :maxlevel . 5) (nil :maxleve
