I never used Hyperbole back in the day so this is all fresh for me. I am
also an avid org-mode user. The following feedback is based on about 48
hours of usage.
Hyperbole is a suite of tools. One of them is an outliner that overlaps
quite a bit with org-mode. It has some interesting features like
Hi all,
I would like detangling to work even where there are Noweb references in
code chunks.
My reason for this is that I've have hit the following case several times
and haven't found a satisfactory answer yet:
1. I would like to break up the code within braces or parens into their own
chunks
2.
Hi all,
How do I get code on my beamer slides to print with color and highlighting?
I'm doing the standard:
#+BEGIN_SRC blah
#+END_SRC
but all my source blocks come out the same.
Thanks!
-deech
Hi all,
When weaving with noweb style chunks is there a way for the noweb
references to become links back to the chunk in the exported HTML?
For example when the following is woven:
** weaving :PROPERTIES:
:tangle: yes :END:
#+name: foo#+begin_src emacs-lisp
(foo)
#+end_src#+begin_sr
n Fri, Oct 18, 2013 at 11:44 AM, Eric Schulte wrote:
> aditya siram writes:
>
> > Hi all,
> > Currently when I export a literate program I can see the chunks but not
> > where they end up. It would be really useful if the chunks had a footnote
> > or something that
Hi all,
Currently when I export a literate program I can see the chunks but not
where they end up. It would be really useful if the chunks had a footnote
or something that linked to the file where they were tangled. Is there a
header argument that does that?
Thanks!
-deech
Hi all,
Currently the links generated in tangled files are absolute even if the
path to the tangled file is relative. In such cases is there any way to get
it to create a relative path back to the Org file? It makes it impossible
for other people to de-tangle.
-deech
The problem is fill-column indicator [1]. When I loaded Emacs without it
there were no garbage characters. I'm not sure who I should be reporting
this issue to.
-deech
[1] http://www.emacswiki.org/emacs/FillColumnIndicator
On Sat, Sep 21, 2013 at 3:53 PM, aditya siram wrote:
> You&
quot;) (require 'org) (message (org-version)))"
> 8.2
>
> 14:35 bagel:/tmp emacs --version
> GNU Emacs 24.3.1
> Copyright (C) 2013 Free Software Foundation, Inc.
> GNU Emacs comes with ABSOLUTELY NO WARRANTY.
> You may redistribute copies of Ema
this on export to other backends?
>
> aditya siram writes:
>
> > Hi all,
> > I'm on org-mode version:
> > Org-mode version 8.2 (release_8.2-8-g16a57e @
> > /home/deech/EmacsConfig/org-mode/lisp/)
> >
> > Unfortunately the html exporter has som
Hi all,
I'm on org-mode version:
Org-mode version 8.2 (release_8.2-8-g16a57e @
/home/deech/EmacsConfig/org-mode/lisp/)
Unfortunately the html exporter has some garbage characters at the end of
every line.
Here's a small org file:
* Headline
#+BEGIN_SRC sh
test source
#+END_SRC
The resultin
Hi all,
I'm on org-mode version:
Org-mode version 8.2 (release_8.2-8-g16a57e @
/home/deech/EmacsConfig/org-mode/lisp/)
Unfortunately the html exporter has some garbage characters at the end of
every line.
Here's a small org file:
* Headline
#+BEGIN_SRC sh
test source
#+END_SRC
The resultin
Yup running C-c C-c solved it! Didn't know about that.
And I can't believe I made the "padlines" typo.
Thanks for taking the time!
-deech
On Wed, Sep 18, 2013 at 1:59 PM, Sebastien Vauban
wrote:
> aditya siram wrote:
> > Sebastien Vauban wrote:
> >> adit
I tried `#+PROPERTY :padlines no` , `#+PROPERTY: padlines no` and
`#+PROPERTY padlines no` all with the same result.
Thanks!
-deech
On Wed, Sep 18, 2013 at 12:20 PM, Sebastien Vauban
wrote:
> aditya siram wrote:
> > Here's the org-file with padlines set to "no" up top:
&
ine:1 ends here */
On Wed, Sep 18, 2013 at 2:31 AM, Sebastien Vauban
wrote:
> Hi Aditya,
>
> aditya siram wrote:
> > It appears as though buffer wide properties are ignored when tangling
> > source blocks. This is easily reproducible by add a `#+PROPERTY:
> :padlines
>
I believe this may have been an instance of the regex being too greedy
which is fixed by the patch I submitted.
-deech
On Fri, Sep 13, 2013 at 12:05 PM, Eric Schulte wrote:
> aditya siram writes:
>
> > Hi all,
> > `org-babel-get-src-block-info` on an empty block fa
es not need to do any back tracking.
>
> 3. You can easily use the simple regexps to find a heading. If you need
> detailed info, match again with looking-at and then use the match data.
>
> Regards
>
> - Carsten
>
> On 14.9.2013, at 23:30, aditya siram wrote:
>
>
Hi all,
What's the rationale for having padlines by default in tangled source? It
generates wrong programs for languages where whitespace is significant
(Haskell) and, for me, doesn't noticeably improve the look of the tangled
file in cases where it isn't.
Thanks!
-deech
Hi all,
It appears as though buffer wide properties are ignored when tangling
source blocks. This is easily reproducible by add a `#+PROPERTY: :padlines
no` to the top of the file and tangling something. The source has padlines.
I tried variations on including `#+PROPERTY: padlines no` and `#+PROP
Hi all,
Org-mode uses two regex's to find headings, one from outline.el and one
defined internally and captures more information. I propose we stop using
the one from outline.el.
org-mode uses `org-back-to-heading` a lot to navigate point back to the
nearest heading.
This just delegates to `outli
Thanks!
-deech
On Sat, Sep 14, 2013 at 10:53 AM, aditya siram wrote:
> Thanks for your feedback and your work on org-babel!
>
> Oops, the maintain-point was a hold-over and isn't actually used in the
> code. I'll remove it.
>
> I will incorporate your suggestions.
&g
d and when I need different behavior in the else
cases?
On Sat, Sep 14, 2013 at 10:44 AM, Eric Schulte wrote:
> aditya siram writes:
>
> > Attached is a patch that fixes a bug with jumping from source block back
> to
> > the Org file. The problem is that the current detangli
I believe I may have fixed the problem. I submitted two patches yesterday.
Hopefully they're formatted ok.
-deech
On Fri, Sep 13, 2013 at 7:27 PM, Suvayu Ali wrote:
> Hello Aditya,
>
> On Fri, Sep 13, 2013 at 06:42:13PM -0500, aditya siram wrote:
> > Hi all
> > I'
Hi all,
This patch fixes a bug where the regexp for parsing source blocks is too
greedy on the body and so fails in the presence of empty code blocks. For
instance given the following:
#+begin_src c
#+end_src
#+begin_src c
hello world
#+end_src
, doing (org-babel-get-src-block-info) the first #+
Attached is a patch that fixes a bug with jumping from source block back to
the Org file. The problem is that the current detangling behavior does not
take the :padlline flag into account. This stopped.
Hopefully this is helpful to others ...
-deech
src_block_jump_fix.patch
Description: Binary d
Hi all
I've made a couple of changes to the latest source tree but I can't seem to
create patches because of some merges that happened subsequently. Is there
some way for me to issue a pull-request?
-deech
Hi all,
`org-babel-get-src-block-info` on an empty block fails.
Given:
#+BEGIN_SRC c
#+END_SRC
#+BEGIN_SRC c
non-empty
#+END_SRC
Running `org-babel-get-src-block-info` with point at the beginning of the
first line gives:
("c" "#+END_SRC
#+BEGIN_SRC c
non-empty" ((:colname-names) (:rowname-names
Hi all,
Currently in HEAD a file tangled with org-babel-tangle does not detangle
with org-babel-detangle.
The problem is that the chunk delimiters in the tangled file are cushioned
with empty lines whereas the same chunk in the Org file is not. So when
'org-babel-detangle' tries to determine the b
Hi all,
When I tangle a source block with ":comments yes" any spaces in the
sub-heading in which the block is found are replaced with "%2520"
instead of "%20". As a consequence when I "org-babel-detangle" the
correct heading is not found.
As an example given the following org file:
* Babel Tanglin
does the exported `.tex` file look like?
>
> Chris
>
> On Oct 7, 2011, at 12:07 PM, aditya siram wrote:
>
> > Hi all,
> > This is probably a really simple question but I'd like to double space my
> Latex output. I added #+LaTeX_CLASS_OPTIONS:[setspace, doublespace]
Hi all,
This is probably a really simple question but I'd like to double space my
Latex output. I added #+LaTeX_CLASS_OPTIONS:[setspace, doublespace] to the
header and I do have the setspace package, but the output is still
single-spaced. Any ideas?
Thanks!
-deech
I am experiencing *so* much cognitive dissonance right now.
-deech
On Sat, Aug 27, 2011 at 10:46 AM, suvayu ali wrote:
> On Sat, Aug 27, 2011 at 5:05 PM, Bastien wrote:
> > Hi folks,
> >
> > http://lumiere.ens.fr/~guerry/theorgfather.html
> >
> > Enjoy!
>
> Ignoring the Hindi audio was a bit dif
Hi all,
Are special characters allowed in tags? I have a set of source blocks
that use certain Haskell functions and to the heading I'd like to add
tags with those function names. But the functions are named eg. (&&&)
which won't show up if typed normally. Is there an escape character
that will all
Ok, I'm a fool, nothing to see here :).
I was mistakenly calling "org-babel-exp-src-block" instead of
"org-babel-expand-src-block".
-deech
On Sat, Jul 9, 2011 at 11:19 AM, aditya siram wrote:
> Hi all,
> I recently tried to insert noweb-style chunks in my source
Hi all,
I recently tried to insert noweb-style chunks in my source and when I
try to expand the source block I am getting an error. Example breaking
code and the error are posted to http://hpaste.org/48874. The error,
however had a bunch of unprintable characters so I include the message
below with
Hi all,
I was running into an issue where "lua-mode" would throw an error that
stopped "org-babel-tangle" function in "ob-tangle.el". I have patched
"org-babel-tangle" to ignore errors thrown by invoking any language's
mode. The patch is attached.
-deech
From 2093523c672b83d53d9eca3680cb10682784df
It appears I misread the manual. 'no-expand' works only for tangling -
but my original question stands. Is there a header that provides this
feature for weaving with links to the chunk like a noweb document?
-deech
On Tue, Oct 5, 2010 at 10:12 PM, aditya siram wrote:
> Hi all,
Hi all,
I may have understood the :no-expand header incorrectly, but I thought
it suppressed expanding noweb references while exporting but seems to
expand them.
For example I have an org file that looks like this (simplified) :
* Root
#+begin_src fundamental :noweb yes :no-expand :tangle Root.txt
the
> highlighted upcoming section visible.
>
> John
> On Wed, Sep 8, 2010 at 9:12 AM, Dan Davison wrote:
>>
>> aditya siram writes:
>>
>> > Hi all,
>> > I am wondering how to get an outline in an org-beamer presentation.
>> > Cur
Hi all,
I am wondering how to get an outline in an org-beamer presentation.
Currently I have a structure that looks like:
#+TITLE: My Title
#+AUTHOR: Me
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_FRAME_LEVEL: 2
#+COLUMNS: %35ITEM %10BEAMER_env(Env) %10BEAMER_envargs(Env A
e block lives in the
> original Org file.
>
> See [1] for information on the :comment header argument, and see [2] for
> information on using header arguments in general.
>
> Best -- Eric
>
> aditya siram writes:
>
> > Hi all,
> > How do I get the org file line n
Hi all,
How do I get the org file line numbers in the tangled source? This way error
messages point to the org file.
thanks ...
-deech
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.g
Hi all,
I have a heading like this :
* Root
Comments about root.
#+begin_src haskell :noweb yes :comments yes :tangle Main.hs
main = print "hello world"
#+end_src
When I tangle the file, I would expect the "Comments about root" to be a
comment above the source like so:
-- Comments about root
ma
The function that loads the code block into the interpreter
org-babel-load-in-session does not do noweb reference expansion.
I have included a git patch that adds that functionality.
-deech
On Sat, Aug 21, 2010 at 4:42 PM, aditya siram wrote:
> Hi all,
> I have the development version
The last patch is formatted for email. Here's the correct one. Sorry.
-deech
On Sun, Aug 22, 2010 at 4:21 PM, aditya siram wrote:
> The function that loads the code block into the interpreter
> org-babel-load-in-session does not do noweb reference expansion.
>
> I have included
Hi all,
I have the development version of org-mode and org-babel noweb style
references are not expanding during evaluation, they are instead copied
literally into the temp file. They seem to expand fine when tangling. Here
is file that is failing:
* Root
#+begin_src haskell :noweb yes :tangle Main
Is there a way to link headlines across several files?
For example, I have a Projects.org and Contacts.org
Projects.org*
* Mow the lawn
# << Chem Lawn >>
End**
***Contacts.org**
* Chem Lawn
555-555-
***End***
When I
Thanks, this is exactly what I wanted.
Deech
From: Carsten Dominik <[EMAIL PROTECTED]>
To: Deech <[EMAIL PROTECTED]>
CC: emacs-orgmode@gnu.org
Subject: Re: [Orgmode] Org Mode Searching Bug?
Date: Mon, 15 Jan 2007 17:23:32 +0100
Hi Deech,
this is intentional, the headline following a headline
48 matches
Mail list logo
