Re: [O] comment section with latex_header
Robert Klein wrote: > On 03/24/2015 10:04 AM, Sebastien Vauban wrote: > >> Can't we say that a COMMENT'ed subtree is like having all of its >> contents commented, line by line? IOW, nothing "accessible"? > > This would probably break a lot of babel stuff. Could you elaborate why? > If there was an option to disable exports for #+NAME:-ed stuff (i.e. > data sources for babel), e.g. somtehing like > > #+NAME: xyzzy :exports none > | munich | 13 | > | cologne | 12 | > > you could deprecate and eventually disable data sources in COMMENT-ed > section. If you *not to export* some stuff in a subtree, adding the "noexport" tag would be enough, right? Best regards, Seb -- Sebastien Vauban
[O] ob-lilypond
Hey all,
looks like I’m having quite a few problems with ob-lilypond (Org-mode version
8.2.7b). To ensure that my setup is correct I ran the tests mentioned on
http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html#sec-9:
M-x load-file RET
~/path/to/current/org-mode-git-repository/testing/lisp/test-ob-lilypond.el
M-x ert RET RET
And this is what I got (short version):
Selector: t
Passed: 6
Failed: 36 (36 unexpected)
Total: 42/42
Started at: 2015-03-25 13:32:19+0100
Finished.
Finished at: 2015-03-25 13:32:19+0100
...FFF…F
Am I missing something? How can I get this to work?
Thanks for any help!
patrick
Error message (long version):
Selector: t
Passed: 6
Failed: 36 (36 unexpected)
Total: 42/42
Started at: 2015-03-25 13:32:19+0100
Finished.
Finished at: 2015-03-25 13:32:19+0100
...FFF...F
F ob-lilypond/ly-arrange-mode
(ert-test-failed
((should
(boundp 'org-babel-lilypond-arrange-mode))
:form
(boundp org-babel-lilypond-arrange-mode)
:value nil))
F ob-lilypond/ly-attempt-to-open-pdf
(void-variable org-babel-lilypond-display-pdf-post-tangle)
F ob-lilypond/ly-attempt-to-play-midi
(void-variable org-babel-lilypond-play-midi-post-tangle)
F ob-lilypond/ly-check-for-compile-error
(void-function org-babel-lilypond-check-for-compile-error)
F ob-lilypond/ly-command-ly/bound
(ert-test-failed
((should
(boundp 'org-babel-lilypond-ly-command))
:form
(boundp org-babel-lilypond-ly-command)
:value nil))
F ob-lilypond/ly-command-ly/stringp
(void-variable org-babel-lilypond-ly-command)
F ob-lilypond/ly-command-midi/bound
(ert-test-failed
((should
(boundp 'org-babel-lilypond-midi-command))
:form
(boundp org-babel-lilypond-midi-command)
:value nil))
F ob-lilypond/ly-command-midi/stringp
(void-variable org-babel-lilypond-midi-command)
F ob-lilypond/ly-command-pdf/bound
(ert-test-failed
((should
(boundp 'org-babel-lilypond-pdf-command))
:form
(boundp org-babel-lilypond-pdf-command)
:value nil))
F ob-lilypond/ly-command-pdf/stringp
(void-variable org-babel-lilypond-pdf-command)
F ob-lilypond/ly-commands/customize
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "nonsense" "bla" "fasel")))
:form
(equal
(nil nil nil)
("nonsense" "bla" "fasel"))
:value nil :explanation
(list-elt 0
(different-types nil "nonsense"
F ob-lilypond/ly-commands/darwin
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "/Applications/lilypond.app/Contents/Resources/bin/lilypond"
"open" "open")))
:form
(equal
(nil nil nil)
("/Applications/lilypond.app/Contents/Resources/bin/lilypond" "open"
"open"))
:value nil :explanation
(list-elt 0
(different-types nil
"/Applications/lilypond.app/Contents/Resources/bin/lilypond"
F ob-lilypond/ly-commands/other
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "lilypond" "xdg-open" "xdg-open")))
:form
(equal
(nil nil nil)
("lilypond" "xdg-open" "xdg-open"))
:value nil :explanation
(list-elt 0
(different-types nil "lilypond"
F ob-lilypond/ly-commands/windows-nt
(ert-test-failed
((should
(equal
(list org-babel-lilypond-ly-command org-babel-lilypond-pdf-command
org-babel-lilypond-midi-command)
(list "lilypond" "" "")))
:form
(equal
(nil nil nil)
("lilypond" "" ""))
:value nil :explanation
(list-elt 0
(different-types nil "lilypond"
F ob-lilypond/ly-compile-lilyfile
(void-variable org-babel-lilypond-ly-command)
F ob-lilypond/ly-compile-post-tangle
(ert-test-failed
((should
(boundp 'org-babel-lilypond-compile-post-tangle))
:form
(boundp org-babel-lilypond-compile-post-tangle)
:value nil))
F ob-lilypond/ly-display-pdf-post-tangle
(ert-test-failed
((should
(boundp 'org-babel-lilypond-display-pdf-post-tangle))
:form
(boundp org-babel-lilypond-display-pdf-post-tangle)
:value nil))
F ob-lilypond/ly-gen-html
(ert-test-failed
((should
(boundp 'org-babel-lilypond-gen-pdf))
:form
(boundp org-babel-lilypond-gen-pdf)
:value nil))
F ob-lilypond/ly-gen-png
(ert-test-failed
((should
(boundp 'org-babel-lilypond-gen-png))
:form
(boundp org-babel-lilypond-gen-png)
:value nil))
F ob-lilypond/ly-gen-svg
(ert-t
Re: [O] [ox, patch] Add #+SUBTITLE
Melanie Bacou writes:
> Here is how titles and subtitles are supported in Bootstrap ("the most
> popular HTML/CSS/JS framework"):
>
>
> This would be the title and this the subtitle
>
>
> ref: http://getbootstrap.com/components/#page-header
I don't know what bootstrap is. I have softened on the whole JS thing,
but a side should still work (almost) perfectly without it.
Anyway, the example looks ugly (IMO) as there's no line break. Is that a
feature? The tag seems handy though.
> Another commonly seen approach is this (many web CMS use this pseudo
> standard):
>
> My Title
> My Subtitle
This is basically how it's handled. I guess you could get the former by
writing a custom preamble and disabling title export.
Is that good enough?
—Rasmus
--
Hvor meget poesi tror De kommer ud af et glas isvand?
Re: [O] [ox, patch] Add #+SUBTITLE
Hi, Melanie Bacou writes: > I would indeed go further and suggest adding the following once and > for all as common ox features: I don't think so. Consider the ultra important ox-ical (it's important 'cause it keep my calendar in sync via org-caldav). How should it handle these fields? I think markdown also ignores them. I think it's better to identify a subset of "text exporters" (ox-ascii, ox-html, ox-latex, ox-odt) that support a larger set of keywords, but not through ox.el. (Though having it in ox makes the backend code slightly cleaner). > #+AUTHORS (support multiple) This one is tough. Recently I had to write a LaTeX title for two authors, one institutions like Author 1Author 2 Institution AFAIK, the \and does not work for this in LaTeX. It's just very hard to find a general solution. How would you even write this? How do I associate authors and institution? Previously we talked about supporting footnotes in TITLE and AUTHOR which could maybe solve the email issue. > #+EMAILS (1 per author) > #+AFFILIATIONS (1 per author) AFAIK this is supported in beamer, so we could add it there. It's also in KOMA-Script I believe. > #+CLASSIFICATION (e.g. "ACM", "JEL", "Dublin Core", "your corporate > classification", etc.) I have no clue what this means. > #+KEYWORDS > #+DESCRIPTION > #+REVISION > #+COPYRIGHT Are these fields standard? In hyperref these are supported out of the box: pdftitle pdfauthor pdfsubject pdfcreator pdfproducer pdfkeywords pdftrapped New ones can be added via pdfinfo, though. You have not specified any details about what is printed. I guess something like revision is like a subtitle, i.e. you'd want it printed? > This is not so much about what back-ends currently support (that's > irrelevant in my view), it's about what minimum meta information is > needed to publish and maintain meaningful documents. It also about having good support for our main backends. E.g. we try to support math equally well in latex and other backends. > The use of these meta fields encourage good publishing practices, and > all back-ends should eventually support all or a subset of these. Most > LaTeX journal classes do. ^^^ But ox-latex assumes the default doc. classes. > HTML would support these at least as tags. It would be great if you would concretely share examples with us, that uses all of this stuff in a concrete manner. At the very least more details is needed. You will also have to confirm whether you truly think this is an ox.el issue in the light of my comments above (what is COPYRIGHT to ical?). > ODT and DOCX can support all using templates. Org does not export to docx. —Rasmus -- . . . The proofs are technical in nature and provides no real understanding
Re: [O] [ox, patch] Add #+SUBTITLE
Rasmus writes: >> >> This would be the title and this the subtitle >> >> >> ref: http://getbootstrap.com/components/#page-header According to html5doctor.com: Note: Some have been advocating of the use of the small element to signify subtitles. This has been under discussion in the HTML working group, but no compelling arguments for its use have been made. Therefore it is not advised to use small to mark up subtitles. That puts the nail in that coffin. . . >> Another commonly seen approach is this (many web CMS use this pseudo >> standard): >> >> My Title >> My Subtitle > > This is basically how it's handled. I guess you could get the former by > writing a custom preamble and disabling title export. The same page as above leads to this interesting documents, which unfortunately has draft in its name. http://www.w3.org/html/wg/drafts/html/master/semantics.html#sub-head It suggests the following: title subtitle I really like this one! This is the HTML5 solution, it seems. Then this could be used for non-HTML5: Ramones Hey! Ho! Let's Go WDYT? —Rasmus -- And when I’m finished thinking, I have to die a lot
Re: [O] [bug?, ox-latex] creator not commented out
Hello, Rasmus writes: > This "sort of" breaks the creator field for hyperref. Now we neither have > the Org string nor the default LaTeX string. You need to set `org-export-with-creator' to t. We can also patch `org-latex--format-spec' to skip ?c entry altogether when the variable is nil, in order to get default LaTeX string. > We could make creator unconditional for meta data (makes sense) and > ask people to remove %c from the respective template*s*(!) if they > don't want it... This is what "ox-html" does, AFAICT. Either way is fine with me. Do you want to make the change? > Also, there's no longer a "created with org"-tag at the bottom of html > pages by default. This is not necessarily bad. This was a misinterpretation of `comment' value in "ox-html.el". Anyway, I think this is fine. Regards, -- Nicolas Goaziou
Re: [O] [bug?, ox-latex] creator not commented out
Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >> This "sort of" breaks the creator field for hyperref. Now we neither have >> the Org string nor the default LaTeX string. > > You need to set `org-export-with-creator' to t. We can also patch > `org-latex--format-spec' to skip ?c entry altogether when the variable > is nil, in order to get default LaTeX string. But as I started by saying this adds the creator as inline-text in latex cf. the end of org-latex-template. >> We could make creator unconditional for meta data (makes sense) and >> ask people to remove %c from the respective template*s*(!) if they >> don't want it... > > This is what "ox-html" does, AFAICT. ATM no ad is exported in the postamble. It used to printed in 8.2. I don't mind not having it. > Either way is fine with me. Do you want to make the change? Yeah, but I don't know what the right change is. I can remove the creator part from the ox-latex template and make the hyperref spec ignore :with-creator. —Rasmus -- . . . The proofs are technical in nature and provides no real understanding
[O] How to place things differently in dot
I was asked to make a diagram and was thinking that dot in org-mode could
be a good idea.
I got reasonably fast the following:
#+BEGIN_SRC dot :file test.svg :cmdline -Kdot -Tsvg
graph {
utilities [label = "Utility's"]
A
B
C
D
E
F [shape = rectangle]
subgraph cluster_resources {
color=blue
resources [label = "Resources"]
}
G
H
I
K
subgraph cluster_ta {
color=blue
{rank = same; L, M}
L
M
}
{rank = same; D, E, F}
A -- F
B -- F
C -- F
A -- D
F -- E
F -- K
F -- G
F -- H
F -- I
K -- L
K -- M
L -- M
}
#+END_SRC
This is a good deal in the right direction, but a few things should be
different:
- E should be left of F
- resource should go to the second 'line' without losing its border
- K should be a 'line' lower
Are those things possible?
As attachment how it looks now.
--
Cecil Westerhof
Re: [O] comment section with latex_header
Hi all, Sebastien Vauban writes: > Robert Klein wrote: >> On 03/24/2015 10:04 AM, Sebastien Vauban wrote: >> >>> Can't we say that a COMMENT'ed subtree is like having all of its >>> contents commented, line by line? IOW, nothing "accessible"? >> >> This would probably break a lot of babel stuff. > > Could you elaborate why? > >> If there was an option to disable exports for #+NAME:-ed stuff (i.e. >> data sources for babel), e.g. somtehing like >> >> #+NAME: xyzzy :exports none >> | munich | 13 | >> | cologne | 12 | >> >> you could deprecate and eventually disable data sources in COMMENT-ed >> section. > > If you *not to export* some stuff in a subtree, adding the "noexport" > tag would be enough, right? > > Best regards, > Seb FWIW, I agree that COMMENT should be equivalent to individual line # . Sections that should be accessible without being exported get the :noexport: tag. Is there any usecase for COMMENTed sections that is not covered by :noexport:? Regards, Andreas
[O] Org-Mode and Mac OS X advice
Hello All, I am thinking about changing to a Mac from Windows and wanted to check that there are no issues with using org-mode in OS X. I would like to know what version of Emacs people use (e.g. Aquamacs) and also if there are any issues using org-mode on a Mac. For example, I export to PDF frequently so would like to know if I need any other software for this. Many thanks, Chris
Re: [O] Org-Mode and Mac OS X advice
Hello, On 2015-03-26 13:18, "Chris Willard" writes: > I am thinking about changing to a Mac from Windows and wanted to check > that there are no issues with using org-mode in OS X. I don't have any issue here. > I would like to know what version of Emacs people use (e.g. Aquamacs) > and also if there are any issues using org-mode on a Mac. For example, > I export to PDF frequently so would like to know if I need any other > software for this. I no longer use Aquamacs as it was bundling too many things, so I now use this version of emacs: https://github.com/railwaycat/emacs-mac-port, which has great support for retina screens, among other things. I install it using homebrew (http://brew.sh/), a very convenient way of installing additional utilities. Regarding LaTeX, I use MacTex (https://tug.org/mactex/), which is basically texlive packaged in an installer. Don't hesitate to contact me directly if you have any questions. Best, Alan -- OpenPGP Key ID : 040D0A3B4ED2E5C7 signature.asc Description: PGP signature
Re: [O] Org-Mode and Mac OS X advice
I did this last summer, and I found no issues. I use an emacs built from homebrew (see https://github.com/jkitchin/jmax#mac-users). You will need a LaTeX installation for PDF export. It all works great for me. Chris Willard writes: > Hello All, > > I am thinking about changing to a Mac from Windows and wanted to check > that there are no issues with using org-mode in OS X. > > I would like to know what version of Emacs people use (e.g. Aquamacs) > and also if there are any issues using org-mode on a Mac. For example, > I export to PDF frequently so would like to know if I need any other > software for this. > > Many thanks, > > Chris -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] Org-Mode and Mac OS X advice
I'm using the dailies from ELPA, upgrading occasionally. Works well in the "normal" current Emacs from http://emacsformacosx.com/ I'd have recommended Aquamacs until recently, but the builds from link above are both more current and stable generally. For LaTeX, there are many ways to get it such as homebrew; I am quite happy with MacTeX from https://tug.org/mactex/. Note that you might have to configure paths for LaTeX in Emacs, if you start Emacs from the GUI, since changing GUI session environment on Macs is less than obvious. Alternatively: • Configure your path in your user's launchd config so that the whole session has LaTeX in your path • Modify your shell environment and just launch Emacs from the shell. The binary would then be /Applications/Emacs.app/Contents/MacOS/Emacs Cheers, Bernd On 26 March 2015 at 14:18, Chris Willard wrote: > Hello All, > > I am thinking about changing to a Mac from Windows and wanted to check > that there are no issues with using org-mode in OS X. > > I would like to know what version of Emacs people use (e.g. Aquamacs) > and also if there are any issues using org-mode on a Mac. For example, > I export to PDF frequently so would like to know if I need any other > software for this. > > Many thanks, > > Chris > > > > -- Senior Software Engineer Xaidat GmbH Wickenburggasse 5 8010 Graz Austria / Europe web: http://www.xaidat.com/ phone: +43-676-845023-706 email: bernd.h...@xaidat.com FN 384295s, LG ZRS Graz UID-Nr. ATU67414611
Re: [O] Org-Mode and Mac OS X advice
On 2015-03-26 14:50, Bernd Haug writes: > Alternatively: > > • Configure your path in your user's launchd config so that the whole > session has LaTeX in your path > • Modify your shell environment and just launch Emacs from the shell. > The binary would then be /Applications/Emacs.app/Contents/MacOS/Emacs I'm using this nice trick (passed to me by a colleague) that sets the environment variables and path to be the same in zsh and emacs (launched From the GUI). #+begin_src emacs-lisp (let ((vars (split-string-and-unquote (shell-command-to-string ". ~/.zshrc; export") "\n"))) (mapcar (lambda (X) (let ((var_val (split-string-and-unquote X "="))) (setenv (car var_val) (cadr var_val vars) (setq exec-path (append (split-string-and-unquote (getenv "PATH") ":") exec-path))) #+end_src Alan -- OpenPGP Key ID : 040D0A3B4ED2E5C7 signature.asc Description: PGP signature
[O] [bug] fuzzy link not matching commented headlines
Guess it's a bug that fuzzy links won't match a commented headline whereas the other internal link types (custom_id and org ID) do. Or is there a special purpose for this specific type of link regarding comments? Just check the following example: ,-- | * First headline | 1. fuzzy link to [[Second headline]] -- ok | 2. fuzzy link to commented [[Third headline]] -- fails | | 3. custom_id link to commented [[#Fourth][Fourth headline]] -- ok | 4. id link to commented [[id:D91E1EF3-2918-4F37-98EB-E2C92ACBE372][Fifth headline]] -- ok | | * Second headline | | * COMMENT Third headline | | * COMMENT Fourth headline | :PROPERTIES: | :CUSTOM_ID: Fourth | :END: | | * Fifth headline | :PROPERTIES: | :ID: D91E1EF3-2918-4F37-98EB-E2C92ACBE372 | :END: | `-- -- Fetch my gnupg key: gpg --keyserver pgp.mit.edu --recv-keys 7E3CA33F smime.p7s Description: S/MIME cryptographic signature
[O] org-drill problem: questions are blank
>From time to time Org-drill shows me a blank window instead of a question. The frame, mode line and prompt to answer are visible, but there's nothing in the window at all. As a workaround I can type "t" to edit the tags, and the question will appear. A sample file is enclosed. It's a new file without any of the org-drill property drawers just to keep the example short and to avoid having to wait for the question to be scheduled to be shown again, but the problem *does* still happen when the drawers are present. To reproduce the bug, run org-drill in drillbug.org; the question "MC" gives a blank screen. I'm using org-drill with the latest version of Org-mode, git commit 2f58e3c011ec84f621905332d8df68b83da580d9, on Emacs 24.3.1, 2014-09-30. Peter.
Re: [O] Space at end of monospace string?
On Tuesday, 24 Mar 2015 at 11:04, Loris Bennett wrote: > Hi, > > I'm writing a beamer presentation and have the followoing > >- =--nodes=2= $\Rightarrow$ 2 /or more/ nodes >- =--nodes=2-4= $\Rightarrow$ 2 to 4 nodes > > It would be nice to have the arrows line up, but doing =--nodes=2 = > obviously doesn't work. If you want things to line up, I would recommend using either tables (e.g. with \Rightarrow as column separator specified in the table attributes) or one of the aligned equation environments in LaTeX with \mbox or \textrm for the actual text elements. Using font spacing is always going to be messy... -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-790-gb719c1.dirty
Re: [O] How to place things differently in dot
On Thursday, 26 Mar 2015 at 13:14, Cecil Westerhof wrote: > I was asked to make a diagram and was thinking that dot in org-mode could > be a good idea. [...] > This is a good deal in the right direction, but a few things should be > different: The graphviz tools are fantastic for quick and dirty graphs but the layout algorithms are not easily controlled... I would highly recommend tikz ... If you do want to use dot, I have only ever managed to get what I want by changing the order in which I specify the connections and/or more use of sub-graphs. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-790-gb719c1.dirty
Re: [O] How to place things differently in dot
On 2015-03-26 at 11:52, e.fr...@ucl.ac.uk wrote: > The graphviz tools are fantastic for quick and dirty graphs but the > layout algorithms are not easily controlled... I would highly > recommend tikz ... Or perhaps ditaa. -k.
Re: [O] Org-Mode and Mac OS X advice
There are no issues. Use Brew to install the `emacs' recipe. It uses the [GNU build.] It is the best supported build. MacTex is the best LaTeX release. Even Brew will tell you so. Download the DMG yourself; the Brew Cask installer is not guaranteed to choose a download site close to you. My configurations for running on OSX are not org specific but might be valuable to you: • [https://github.com/grettke/home/blob/master/.emacs.el#L844] • [https://github.com/grettke/home/blob/master/.emacs.el#L844] • [https://github.com/grettke/home/blob/master/.emacs.el#L853] • [https://github.com/grettke/home/blob/master/.emacs.el#L863] [GNU build.] https://github.com/Homebrew/homebrew/blob/master/Library/Formula/emacs.rb#L5 On Thu, Mar 26, 2015 at 8:18 AM, Chris Willard wrote: > Hello All, > > I am thinking about changing to a Mac from Windows and wanted to check > that there are no issues with using org-mode in OS X. > > I would like to know what version of Emacs people use (e.g. Aquamacs) > and also if there are any issues using org-mode on a Mac. For example, > I export to PDF frequently so would like to know if I need any other > software for this. > > Many thanks, > > Chris > > > > -- Grant Rettke g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson
Re: [O] Org-Mode and Mac OS X advice
On Thu Mar 26 2015 at 08:18, "Chris Willard" wrote: > Hello All, > > I am thinking about changing to a Mac from Windows and wanted to check > that there are no issues with using org-mode in OS X. > > I would like to know what version of Emacs people use (e.g. Aquamacs) > and also if there are any issues using org-mode on a Mac. For example, > I export to PDF frequently so would like to know if I need any other > software for this. I do this to get emacs on my macbook pro: ,[ emacs-install ] | #!/usr/local/bin/bash | brew update | brew unlink emacs | brew uninstall emacs | brew install emacs --HEAD --use-git-head --cocoa --with-gnutls --with-rsvg --with-imagemagick | brew linkapps ` I don't think I've had any mac-specific problems with orgmode - I use it every day. And as others have said, mactex is very nice: https://tug.org/mactex/ Cheers - bw -- Bill White . bi...@wolfram.com "No ma'am, we're musicians."
Re: [O] How to place things differently in dot
2015-03-26 17:07 GMT+01:00 Ken Mankoff : > > On 2015-03-26 at 11:52, e.fr...@ucl.ac.uk wrote: > > The graphviz tools are fantastic for quick and dirty graphs but the > > layout algorithms are not easily controlled... I would highly > > recommend tikz ... > > Or perhaps ditaa. > It is certainly quick. I wait if they find it acceptable: if not I can always check-out tikz or ditaa. -- Cecil Westerhof
Re: [O] How to place things differently in dot
Cecil Westerhof writes:
> I was asked to make a diagram and was thinking that dot in org-mode could
> be a good idea.
>
> I got reasonably fast the following:
> #+BEGIN_SRC dot :file test.svg :cmdline -Kdot -Tsvg
> graph {
> utilities [label = "Utility's"]
>
> A
> B
> C
>
> D
> E
> F [shape = rectangle]
>
>
> subgraph cluster_resources {
> color=blue
> resources [label = "Resources"]
> }
>
> G
> H
> I
>
> K
> subgraph cluster_ta {
> color=blue
> {rank = same; L, M}
> L
> M
> }
>
> {rank = same; D, E, F}
>
>
> A -- F
> B -- F
> C -- F
> A -- D
>
> F -- E
>
> F -- K
> F -- G
> F -- H
> F -- I
>
>
> K -- L
> K -- M
> L -- M
> }
> #+END_SRC
>
> This is a good deal in the right direction, but a few things should be
> different:
> - E should be left of F
> - resource should go to the second 'line' without losing its border
> - K should be a 'line' lower
>
> Are those things possible?
As a last resort, you can edit the svg file.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] How to place things differently in dot
2015-03-26 18:00 GMT+01:00 Thomas S. Dye :
> Cecil Westerhof writes:
>
> > I was asked to make a diagram and was thinking that dot in org-mode could
> > be a good idea.
> >
> > I got reasonably fast the following:
> > #+BEGIN_SRC dot :file test.svg :cmdline -Kdot -Tsvg
> > graph {
> > utilities [label = "Utility's"]
> >
> > A
> > B
> > C
> >
> > D
> > E
> > F [shape = rectangle]
> >
> >
> > subgraph cluster_resources {
> > color=blue
> > resources [label = "Resources"]
> > }
> >
> > G
> > H
> > I
> >
> > K
> > subgraph cluster_ta {
> > color=blue
> > {rank = same; L, M}
> > L
> > M
> > }
> >
> > {rank = same; D, E, F}
> >
> >
> > A -- F
> > B -- F
> > C -- F
> > A -- D
> >
> > F -- E
> >
> > F -- K
> > F -- G
> > F -- H
> > F -- I
> >
> >
> > K -- L
> > K -- M
> > L -- M
> > }
> > #+END_SRC
> >
> > This is a good deal in the right direction, but a few things should be
> > different:
> > - E should be left of F
> > - resource should go to the second 'line' without losing its border
> > - K should be a 'line' lower
> >
> > Are those things possible?
>
> As a last resort, you can edit the svg file.
>
It did cross my mind, but I am afraid it is not a real option (for me).
--
Cecil Westerhof
Re: [O] Space at end of monospace string?
Hello, writes: > On Tuesday, 24 Mar 2015 at 11:04, Loris Bennett wrote: >> Hi, >> >> I'm writing a beamer presentation and have the followoing >> >>- =--nodes=2= $\Rightarrow$ 2 /or more/ nodes >>- =--nodes=2-4= $\Rightarrow$ 2 to 4 nodes >> >> It would be nice to have the arrows line up, but doing =--nodes=2 = >> obviously doesn't work. > > If you want things to line up, I would recommend using either tables > (e.g. with \Rightarrow as column separator specified in the table > attributes) or one of the aligned equation environments in LaTeX with > \mbox or \textrm for the actual text elements. Using font spacing is > always going to be messy... The OP can also use a spacing entity, e.g., \nbsp. Regards, -- Nicolas Goaziou
[O] RDF/Linked Data?
I googled "rdf linked data org mode" and got exactly one link to something from 2009 called gnowsys, which is not really doing anything with org-mode anymore? I saw how babel will do spaql, which is cool. Any other such efforts out there? LB
Re: [O] How to place things differently in dot
2015-03-26 17:57 GMT+01:00 Cecil Westerhof : > 2015-03-26 17:07 GMT+01:00 Ken Mankoff : > >> >> On 2015-03-26 at 11:52, e.fr...@ucl.ac.uk wrote: >> > The graphviz tools are fantastic for quick and dirty graphs but the >> > layout algorithms are not easily controlled... I would highly >> > recommend tikz ... >> >> Or perhaps ditaa. >> > > It is certainly quick. I wait if they find it acceptable: if not I can > always check-out tikz or ditaa. > I looked at ditaa and tikz. Especially ditta is very nice. It has document and database elements, but it would also a lot more work to create and especially to maintain. So I hope my dot version is acceptable. -- Cecil Westerhof
Re: [O] org-drill problem: questions are blank
Peter Westlake writes: > From time to time Org-drill shows me a blank window instead of a > question. The frame, mode line and prompt to answer are visible, but > there's nothing in the window at all. As a workaround I can type "t" to > edit the tags, and the question will appear. > > A sample file is enclosed. It's a new file without any of the org-drill > property drawers just to keep the example short and to avoid having to > wait for the question to be scheduled to be shown again, but the problem > *does* still happen when the drawers are present. > > To reproduce the bug, run org-drill in drillbug.org; the question "MC" > gives a blank screen. > > I'm using org-drill with the latest version of Org-mode, git commit > 2f58e3c011ec84f621905332d8df68b83da580d9, on Emacs 24.3.1, 2014-09-30. > > Peter. There's no attached file...
Re: [O] org-babel source code :fonts serif not working
On Thu, 26 Mar 2015, Vikas Rawal wrote:
The following code does not produce image with serif fonts for me. It
used to work earlier but it seems the behaviour has changed. Could
anyone confirm.
AFAICS, it does not work in R.
FWIW, the code that Babel sends to R is (after some formatting):
#+BEGIN_SRC R
png(filename="filename.png",width=1200,height=700,fonts="serif")
tryCatch({
your plot goes here
},
error=function(e){
plot(x=-1:1, y=-1:1, type='n', xlab='', ylab='',
axes=FALSE)
text(x=0, y=0, labels=e$message, col='red')
paste('ERROR', e$message, sep=' : ')})
dev.off()
#+END_SRC
If you can get that or something like to work in R, report back here.
Otherwise take this to one of the R lists.
Also, I note that the filename "filename.png" seems troublesome even apart
from the font issue. I do not have time to run down why that might be.
Chuck
#+BEGIN_SRC R :results output graphics :exports results :file filename.png
:width 1200 :height 700 :fonts serif
<>
#+END_SRC
Re: [O] [ox, patch] Keywords & what should go in ox?
Hi, Nicolas Goaziou writes: >> First, as discussed a while back we want to move DESCRIPTION and KEYWORDS >> out of ox.el as they are specific to certain backends. The first patch >> does this. > > [...] You need to update (info "(org)Publishing options") accordingly, > too. I have now reviewed this section twice, and I have no clue what you want me to change there. There's no :with-keywords or :with-description. At least SUBTITLE for ox-texinfo in not documented here. —Rasmus -- Enough with the bla bla!
Re: [O] [bug] fuzzy link not matching commented headlines
Hello, Martin Carlé writes: > Guess it's a bug that fuzzy links won't match a commented headline > whereas the other internal link types (custom_id and org ID) do. > > Or is there a special purpose for this specific type of link regarding > comments? > > Just check the following example: > > ,-- > | * First headline > > | 1. fuzzy link to [[Second headline]] -- ok > > | 2. fuzzy link to commented [[Third headline]] -- fails > > | > > | 3. custom_id link to commented [[#Fourth][Fourth headline]] -- ok > > | 4. id link to commented [[id:D91E1EF3-2918-4F37-98EB-E2C92ACBE372][Fifth > headline]] -- ok > | > > | * Second headline > > | > > | * COMMENT Third headline > > | > > | * COMMENT Fourth headline > > | :PROPERTIES: > > | :CUSTOM_ID: Fourth > > | :END: > > | > > | * Fifth headline > > | :PROPERTIES: > > | :ID: D91E1EF3-2918-4F37-98EB-E2C92ACBE372 > > | :END: > > | > > `-- Thank you. This should be fixed in 22f732c2553cc8ab42e8465018042bf0f49b6f4f. However, this kind of link is sort of pointless, since it is bound to fail during export, as the targeted headline will be removed. As a consequence, this document cannot be exported, even though COMMENT keyword is only meaningful during export. Regards, -- Nicolas Goaziou
Re: [O] comment section with latex_header
Sebastien Vauban writes: > Can't we say that a COMMENT'ed subtree is like having all of its > contents commented, line by line? IOW, nothing "accessible"? There is, at least, one problem. Comments are always comments (really). However COMMENT keyword is only active during export. That means the behaviour will differ unexpectedly when exporting a document, as reported by Robert Klein. Anyway, anything is possible as long as it is clearly documented. Regards,
Re: [O] comment section with latex_header
Andreas Leha writes: > FWIW, I agree that COMMENT should be equivalent to individual line # . I hope you mean it should be equivalent during export only. Otherwise, it would introduce some serious slowdown as COMMENT can be inherited. > Sections that should be accessible without being exported get > the :noexport: tag. > > Is there any usecase for COMMENTed sections that is not covered > by :noexport:? Babel code from a :noexport: headline is executed. It isn't when in a COMMENT headline. I think both are useful. Regards,
Re: [O] How to place things differently in dot
Cecil Westerhof writes:
> I was asked to make a diagram and was thinking that dot in org-mode could be
> a good idea.
>
> I got reasonably fast the following:
> This is a good deal in the right direction, but a few things should be
> different:
> - E should be left of F
> - resource should go to the second 'line' without losing its border
> - K should be a 'line' lower
>
Maybe this will help although it's not a complete implementation of
what you have. The idea is to define rows and arrange your nodes into
those rows by using rank=same. Then make the row nodes and edges
invisible. It's also important to do the sequencing correctly, e.g.
in your example, if you just switch F -- E to E -- F, E will be to the
left of F as you want. But I don't know how to get the resources
subgraph to be treated as a node and thereby place it on the same row as F.
In any case, here's the current trial balloon:
--8<---cut here---start->8---
#+BEGIN_SRC dot :file test2.svg :cmdline -Kdot -Tsvg
graph foo {
row1--row2--row3--row4 [style="invisible"];
row1, row2, row3, row4 [style="invisible"];
utilities [label = "Utilities"]
A
B
C
D
E
F [shape="rectangle"]
G
H
I
K
subgraph cluster_ta {
color=blue
{rank = same; L, M;}
L
M
}
{rank=same; row1 utilities A B C; }
{rank=same; row2 D E F;}
{rank=same; row3 G H I;}
{rank=same; row4 K;}
subgraph cluster_resources {
resources [label = "Resources"]
graph[color=red];
}
A -- F
B -- F
C -- F
A -- D
E -- F
F -- G
F -- H
F -- I
F -- K
K -- L
K -- M
L -- M
}
#+END_SRC
--8<---cut here---end--->8---
HTH,
Nick
Re: [O] [RFC][PATCH] Store links to named elements
Hello, Jacob Gerlach writes: > In [1], storing links to named elements was discussed. AFAICT, no > patches came from that discussion. The current behavior is that given: > > * Headline > > #+Name: foo > > org-store-link will store a link to `*Headline' rather than `foo'. > > Attached is a very rough first attempt at patching org-store-link to > recognize and link to the name. > > Is this approach worth fleshing out or are there problems associated > with this type of link? Using the above example, [[foo]] seems to be a > valid link, recognized by both export and org-open-at-point. > > If doable, a couple of specific questions: > This attached patch makes no attempt to store the file name as > currently done for headlines. Would it be better to check for a name > in the headline linking code (the final "t" in the org-mode-p `cond' > in org-store-link) or rather reproduce file name code separately. The problem is that links to #+NAME are internal, i.e., they doesn't behave well when targeting a different document. Therefore, I'm not sure there's a real benefit from automating it. Links to headlines are much more robust. > Does a context string make sense for links to element names? No, it doesn't. Regards, -- Nicolas Goaziou
Re: [O] [ox, patch] Keywords & what should go in ox?
Rasmus writes: > I have now reviewed this section twice, and I have no clue what you want > me to change there. There's no :with-keywords or :with-description. I don't know either. I was sure that :keywords and :description were here, but, oddly, it isn't the case. That's a documentation bug as long as these keywords are in "ox.el". > At least SUBTITLE for ox-texinfo in not documented here. That's also a documentation bug. Note that it should probably be :texinfo-subtitle (and :texinfo-subauthor). Regards,
Re: [O] comment section with latex_header
Hi Nicolas, Nicolas Goaziou writes: > Andreas Leha writes: > >> FWIW, I agree that COMMENT should be equivalent to individual line # . > > I hope you mean it should be equivalent during export only. Otherwise, > it would introduce some serious slowdown as COMMENT can be inherited. > I see. I did not consider any possible slow-downs. I'd expect COMMENT to behave exactly like # in every regard -- not only export. That is a clearly defined behaviour, that should not produce confusion. But I am not sure (hence my question below) whether there are use cases that need different behaviour. If COMMENT is only valid for export, then I would actually recommend to rename it to make that clear. >> Sections that should be accessible without being exported get >> the :noexport: tag. >> >> Is there any usecase for COMMENTed sections that is not covered >> by :noexport:? > > Babel code from a :noexport: headline is executed. It isn't when in > a COMMENT headline. I think both are useful. I completely agree. My question was, what a use case would be that requires a COMMENT that behaves different from #'ing the individual lines (and is not covered by :noexport: already). Regards, Andreas
Re: [O] Org-Mode and Mac OS X advice
"Chris Willard" writes: > Hello All, > > I am thinking about changing to a Mac from Windows and wanted to check > that there are no issues with using org-mode in OS X. > > I would like to know what version of Emacs people use (e.g. Aquamacs) > and also if there are any issues using org-mode on a Mac. For example, > I export to PDF frequently so would like to know if I need any other > software for this. > > Many thanks, > > Chris I have used the Homebrew version of Emacs and more recently have compiled Emacs from source. In general the Max OS X version works of Emacs great. I had tried Aquamacs in the past, but the configuration is different and it wasn't worth the hassle. I did find that graphical dialog boxes from Emacs would crash the program (not sure if this has been fixed). I put this in my init file to fix that: (setq use-dialog-box nil)) Finally, org-mode works great (I use the latest version from the git repository) on the Mac. There are a couple of conflicts with some Mac keybindings (I think the control-arrow keys were a problem), but it is easy to reassign these keys in the Mac system settings or use alternatives in Emacs. I had to install an additional program to get PDF generation, but unfortunately I have forgotten the details. It was easy though... David
Re: [O] Updating to the current org-mode in emacs trunk, and Org stable
Am 25.03.2015 14:29, schrieb Rasmus: Hi, Oleh Krehel writes: What's the schedule of merging these changes to the stable versions of Org and to Emacs trunk? My guess: After v8.3 is released. I don't think anybody is working preparing a release at the moment. —Rasmus which would be a pity ... Is there any way, how, many hands with small contributions might get this going ? I mean: get real work done, instead of just nudging the usual activists ? regards Marc
Re: [O] How to place things differently in dot
2015-03-26 21:27 GMT+01:00 Nick Dokos :
> Cecil Westerhof writes:
>
> > I was asked to make a diagram and was thinking that dot in org-mode
> could be a good idea.
> >
> > I got reasonably fast the following:
> > > This is a good deal in the right direction, but a few things should be
> different:
> > - E should be left of F
> > - resource should go to the second 'line' without losing its border
> > - K should be a 'line' lower
> >
>
> Maybe this will help although it's not a complete implementation of
> what you have. The idea is to define rows and arrange your nodes into
> those rows by using rank=same. Then make the row nodes and edges
> invisible. It's also important to do the sequencing correctly, e.g.
> in your example, if you just switch F -- E to E -- F, E will be to the
> left of F as you want. But I don't know how to get the resources
> subgraph to be treated as a node and thereby place it on the same row as F.
>
> In any case, here's the current trial balloon:
>
> --8<---cut here---start->8---
> #+BEGIN_SRC dot :file test2.svg :cmdline -Kdot -Tsvg
> graph foo {
> row1--row2--row3--row4 [style="invisible"];
> row1, row2, row3, row4 [style="invisible"];
>
> utilities [label = "Utilities"]
> A
> B
> C
> D
> E
> F [shape="rectangle"]
> G
> H
> I
> K
> subgraph cluster_ta {
> color=blue
> {rank = same; L, M;}
> L
> M
> }
>
> {rank=same; row1 utilities A B C; }
> {rank=same; row2 D E F;}
> {rank=same; row3 G H I;}
> {rank=same; row4 K;}
>
> subgraph cluster_resources {
> resources [label = "Resources"]
> graph[color=red];
> }
>
> A -- F
> B -- F
> C -- F
> A -- D
> E -- F
> F -- G
> F -- H
> F -- I
> F -- K
> K -- L
> K -- M
> L -- M
> }
> #+END_SRC
>
> --8<---cut here---end--->8---
>
I did it a little differently:
#+BEGIN_SRC dot :file test.png :cmdline -Kdot -Tpng
graph {
utilities [label = "Utility's"]
A
B
C
D
E
F [shape = rectangle]
subgraph cluster_resources {
color=blue
resources [label = "Resources"]
}
G
G_ [style="invisible"]
H
I
K
subgraph cluster_ta {
color=blue
{rank = same; L, M}
L
M
}
{rank = same; D, E, F}
{rank = same; G_, K}
A -- F
B -- F
C -- F
A -- D
E -- F
F -- K
F -- G
F -- H
F -- I
G -- G_ [style="invisible"]
K -- L
K -- M
L -- M
}
#+END_SRC
In this way I do not get an empty column. It would be better when K would
put between and below H and I, but I think I can live with it.
--
Cecil Westerhof
Re: [O] Updating to the current org-mode in emacs trunk, and Org stable
Marc Ihm writes: >>> What's the schedule of merging these changes to the stable versions of >>> Org and to Emacs trunk? >> >> My guess: After v8.3 is released. I don't think anybody is working >> preparing a release at the moment. >> >> —Rasmus >> > > which would be a pity ... > Is there any way, how, many hands with small contributions might get > this going ? If you want to help make a release you should get in touch with Bastien and ask how you can help, I guess. I have absolutely no clue what a release entails. . . Other than creating a changelog... > I mean: get real work done, instead of just nudging the usual activists ? I don't know what you are trying to say here. Plenty of work is going on IRL and in Org master. Thanks, Rasmus -- May contains speling mistake
Re: [O] How to place things differently in dot
Cecil Westerhof writes: > In this way I do not get an empty column. It would be better when K > would put between and below H and I, but I think I can live with it. > Just put I after K and the subgraph. Nick
Re: [O] How to place things differently in dot
Cecil Westerhof writes:
>
> In this way I do not get an empty column.
You can make the rows be of size 0:
--8<---cut here---start->8---
#+BEGIN_SRC dot :file test2.svg :cmdline -Kdot -Tsvg
graph foo {
row1--row2--row3--row4 [style="invis", fixedsize="true", width="0", height="0"];
row1, row2, row3, row4 [style="invis", fixedsize="true", width="0", height="0"];
...
--8<---cut here---end--->8---
Nick
Re: [O] How to place things differently in dot
2015-03-26 22:49 GMT+01:00 Nick Dokos :
> Cecil Westerhof writes:
>
> > In this way I do not get an empty column. It would be better when K
> > would put between and below H and I, but I think I can live with it.
> >
>
> Just put I after K and the subgraph.
>
That works. It is even better when I put both H and I after it.
I also found a way to get resources at the correct place.
It know becomes:
#+BEGIN_SRC dot :file test.png :cmdline -Kdot -Tpng
graph {
A
B
C
utilities [label = "Utility's"]
D
E
F [shape = rectangle]
subgraph cluster_resources {
color=blue
resources [label = "Resources"]
}
G
G_ [style="invisible"]
K
subgraph cluster_ta {
color=blue
{rank = same; L, M}
L
M
}
H
I
{rank = same; D, E, F}
{rank = same; G_, K}
A -- F
B -- F
C -- F
A -- D
utilities -- resources [style="invisible"]
E -- F
F -- K
F -- G
F -- H
F -- I
G -- G_ [style="invisible"]
K -- L
K -- M
L -- M
}
#+END_SRC
That looks very good indeed: I think I do not need to start working with
ditaa. :-)
Everyone thanks for the help.
--
Cecil Westerhof
Re: [O] org-babel source code :fonts serif not working
>
> #+BEGIN_SRC R
> png(filename="filename.png",width=1200,height=700,fonts="serif")
> tryCatch({
> your plot goes here
> },
> error=function(e){
> plot(x=-1:1, y=-1:1, type='n', xlab='', ylab='', axes=FALSE)
> text(x=0, y=0, labels=e$message, col='red')
> paste('ERROR', e$message, sep=' : ')})
> dev.off()
> #+END_SRC
>
> If you can get that or something like to work in R, report back here.
Thanks for the pointer. It is an issue with the graphics device being used.
Using cairo and family (instead of fonts) works for me:
#+BEGIN_SRC R :results output graphics :exports results :file filename.png
:width 1200 :height 700 :type cairo :family serif
<>
#+END_SRC
Vikas
[O] :ignoreheading: works with LaTeX export, but not HTML
I want to put some headers in my org file that don't get exported. If I put
:ignoreheading: after the title, it correctly does not get exported to LaTeX,
but it still appears when I export to HTML (with the text :ignoreheading: on
the same line). Am I missing something? In my setup I have the lines
(defun sa-ignore-headline (contents backend info)
"Ignore headlines with tag `ignoreheading'"
(when (and (org-export-derived-backend-p backend 'latex 'html 'ascii)
(string-match "\\`.*ignoreheading.*\n"
(downcase contents)))
(replace-match "" nil nil contents)))
(defun headline-nonumber (contents backend info)
"Make headlines with nonumber."
(when (and (org-export-derived-backend-p backend 'latex 'html 'ascii)
(string-match "\\`.*nonumber.*\n"
(downcase contents)))
(let ((output contents))
(setq output (replace-regexp-in-string "section{" "section*{" contents))
(setq output (replace-regexp-in-string "hfill{}textsc{nonumber}"
"" output))
output)))
(add-to-list 'org-export-filter-headline-functions 'sa-ignore-headline)
(add-to-list 'org-export-filter-headline-functions 'headline-nonumber)
Thanks for any suggestions.
By the way, this is with org-mode release_8.3beta-951-g2f58e3
Richard Stanton
Re: [O] Org-Mode and Mac OS X advice
Bill White writes: > On Thu Mar 26 2015 at 08:18, "Chris Willard" wrote: > >> Hello All, >> >> I am thinking about changing to a Mac from Windows and wanted to check >> that there are no issues with using org-mode in OS X. >> >> I would like to know what version of Emacs people use (e.g. Aquamacs) >> and also if there are any issues using org-mode on a Mac. For example, >> I export to PDF frequently so would like to know if I need any other >> software for this. > > I do this to get emacs on my macbook pro: > > ,[ emacs-install ] > | #!/usr/local/bin/bash > | brew update > | brew unlink emacs > | brew uninstall emacs > | brew install emacs --HEAD --use-git-head --cocoa --with-gnutls --with-rsvg > --with-imagemagick > | brew linkapps > ` Great, thank you ! I never looked at the upgrade process of emacs via brew. That's done (one more TODO marked done :D). Regards -- Xavier.
Re: [O] How to place things differently in dot
2015-03-26 23:19 GMT+01:00 Cecil Westerhof :
> 2015-03-26 22:49 GMT+01:00 Nick Dokos :
>
>> Cecil Westerhof writes:
>>
>> > In this way I do not get an empty column. It would be better when K
>> > would put between and below H and I, but I think I can live with it.
>> >
>>
>> Just put I after K and the subgraph.
>>
>
> That works. It is even better when I put both H and I after it.
>
> I also found a way to get resources at the correct place.
>
I changed to a digraph:
#+BEGIN_SRC dot :file test.png :cmdline -Kdot -Tpng
digraph {
A
B
C
utilities [label = "Utility's"]
D
E
F [shape = rectangle]
subgraph cluster_resources {
color=blue
resources [label = "Resources"]
}
G
G_ [style="invisible"]
K
subgraph cluster_ta {
color=blue
{rank = same; L, M}
L
M
}
H
I
{rank = same; D, E, F}
{rank = same; G_, K}
A -> F
B -> F
C -> F
A -> D
utilities -> resources [style="invisible"]
E -> F
F -> K [dir = back]
F -> G [dir = back]
F -> H [dir = back]
F -> I [dir = back]
G -> G_ [style="invisible"]
K -> L
K -> M
L -> M
}
#+END_SRC
There is only one problem: I see the arrowhead with:
utilities -> resources
and:
'G -> G_'
Is there a way to get rid of those?
--
Cecil Westerhof
