On Monday, 9 Mar 2015 at 17:36, Richard Lawrence wrote:
[...]
> I feel the same as you do about this, so here's one more thought for the
> thread. How about this alternative?
>
> We keep the existing syntax for keys, which disallows key-ending
> punctuation, but we also allow a second style of
Bug: org-babel-parse-src-block-match reporting "Wrong type argument:
stringp, nil" when exporting a org-mode file with a lots of code blocks
[8.3beta (release_8.3beta-895-g375c83 @ /usr/share/emacs/site-lisp/org/)]
the following is *Messages* buffer
https://www.refheap.com/98243
the follow
Eric S Fraga writes:
>> We keep the existing syntax for keys, which disallows key-ending
>> punctuation, but we also allow a second style of key, in which curly
>> braces surround the key name proper, like:
>>
>> @{Doe1999}
>
> I like this much better.
I'd rather have a single syntax for keys.
Gregor Zattler writes:
> As you might guess this part represents an email, the multi line
> node being the message body. How would one incorporate such
> info in proper org-mode syntax? Since as of now I do not query
> the name=value pairs this is no strict necessity for me.
It depends on what
Hello,
Eric Abrahamsen writes:
> And just for the heck of it, here's another patch that does it with
> narrowing.
Thanks for the patch.
However, I don't think it belongs to `org-adaptive-fill-function' to
handle this. All this Message mode processing should probably be
delegated to the orgstru
Hello,
Linus Arver writes:
> Meanwhile from the Org side, perhaps we can have a way to let the user
> select which program to use for syntax highlighting? Maybe something
> external like Pygments [3]?
Would you want to provide a patch for that?
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> I'd rather have a single syntax for keys.
Me to.
> Since this one is not much more intrusive than the previous one, we
> could as well drop @key in favor of @{key}.
It seems like a moderately dear price to pay for everyone with "normal"
citation keys... It's better t
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> And just for the heck of it, here's another patch that does it with
>> narrowing.
>
> Thanks for the patch.
>
> However, I don't think it belongs to `org-adaptive-fill-function' to
> handle this. All this Message mode processing s
On Sunday 08 March 2015 09:58 PM, Nicolas Goaziou wrote:
> Agreed. I introduced yet another syntax change in "wip-cite" branch.
>
> Now there are two separate objects "citation" and "citation-reference".
> So the following multicite
>
> [cite:prefix; pre @a post; @b]
>
> is parsed like
>
>
John Kitchin writes:
> I don't believe this is possible out of the box. The first RESULTS block
> from the beginning of the buffer will be updated, and not the others.
>
> You might be able to use a hook function to do this, something like:
>
> #+BEGIN_SRC emacs-lisp
> (defun update-results () (i
Aaron Ecay writes:
> Hi Rainer,
>
> 2015ko martxoak 9an, Rainer M Krug-ek idatzi zuen:
>>
>> Hi
>>
>> Consider the following:
>>
>> --8<---cut here---start->8---
>> * The calculation
>> #+NAME: testcode :exports both
>
> It looks like you’ve tried to put a head
Rainer M Krug writes:
> John Kitchin writes:
>
>> I don't believe this is possible out of the box. The first RESULTS block
>> from the beginning of the buffer will be updated, and not the others.
>>
>> You might be able to use a hook function to do this, something like:
>>
>> #+BEGIN_SRC emacs-l
Hi,
Aaron Ecay writes:
> I’ve pushed an update to my branch.
Thank you Aaron! I appreciate the work. While the below may sound
bitter, it's not!
> These are then slurped by org, and used to fill in printf-style
> templates. Some people mentioned using citations as generated by
> citeproc-ja
On Tuesday, 10 Mar 2015 at 09:50, Rasmus wrote:
> Nicolas Goaziou writes:
>> Since this one is not much more intrusive than the previous one, we
>> could as well drop @key in favor of @{key}.
>
> It seems like a moderately dear price to pay for everyone with "normal"
> citation keys... It's bette
> Nikolai Weibull :
> Would it be of interest to anyone else if the bleeding edge version
> was available via elpa?
Isn't this what's MELPA is for?
http://www.emacswiki.org/emacs/MELPA
Ie. GNU ELPA for the official releases and MELPA for git master HEAD.
Eric Abrahamsen writes:
> If we really want to get all the message-specific stuff refactored into
> orgstruct++ mode, I guess we could (in the `orgstruct++-mode' function)
> bind `normal-auto-fill-function' and `adaptive-fill-function' to new
> functions, which first check for message-mode specif
On 2015-03-10T06:21:10+1100, T.F. Torrey
said:
TFT> The biggest obstacle I to this that I see is that developers
tend TFT> to hate the package manager and love git.
This developer appreciates both, and thus particularly appreciates
MELPA as well. :-)
Alexis.
John Kitchin writes:
> weird. I swear it worked in the little toy problem I made ;)
>
> I think this is a more robust function:
>
> #+BEGIN_SRC emacs-lisp
> (defun update-results ()
> ;; get name of src block
> (let* ((name (org-element-property :name (org-element-at-point)))
> (resul
Rainer M Krug writes:
> John Kitchin writes:
>
>> weird. I swear it worked in the little toy problem I made ;)
>>
>> I think this is a more robust function:
>>
>> #+BEGIN_SRC emacs-lisp
>> (defun update-results ()
>> ;; get name of src block
>> (let* ((name (org-element-property :name (org-e
Matthew Gidden writes:
> Another option would be to simply move BEAMER_HEADER to inject code where I
> have implemented BEAMER_HEADER_EXTRA. That would provide the same
> functionality with a reasonable name. I still need to better format my
> commit message (I forgot to before submitting), so I
I am not sure what the convention there is.
John
---
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
On Tue, Mar 10, 2015 at 1
On Tue, Mar 10, 2015 at 9:13 AM, Rainer M Krug wrote:
> Hi
>
> I am struggling with float positioning. I would like to have a float at
> the bottom of a page. Consider the following code:
>
> --8<---cut here---start->8---
> * Some text
> #+NAME: test
> #+begin_s
Hi
I am struggling with float positioning. I would like to have a float at
the bottom of a page. Consider the following code:
--8<---cut here---start->8---
* Some text
#+NAME: test
#+begin_src R :exports results :file-ext pdf :results graphics :width 8 :height
> I am struggling with float positioning. I would like to have a float at
> the bottom of a page.
Maybe something like this:
* Some text
#+LATEX_HEADER: \renewcommand{\topfraction}{1}
#+LATEX_HEADER: \renewcommand{\bottomfraction}{1}
#+NAME: test
#+begin_src R :exports results :file-ext pdf :re
On Mon, Mar 9, 2015 at 7:28 PM, John Kitchin wrote:
> I think you need to set
>
> (setq org-id-link-to-org-use-id 'create-if-interactive)
Indeed, this is a variation of what Leo suggested and customizing
org-id-link-to-org-use-id is almost working for me...
Unfortunately, I want the links to exp
On Tue, Mar 10, 2015 at 6:18 AM, Eric S Fraga wrote:
> On Tuesday, 10 Mar 2015 at 09:50, Rasmus wrote:
> > Nicolas Goaziou writes:
> >> Since this one is not much more intrusive than the previous one, we
> >> could as well drop @key in favor of @{key}.
> >
> > It seems like a moderately dear pri
On Tue, Mar 10, 2015 at 9:44 AM, Nicolas Goaziou
wrote:
> Matthew Gidden writes:
>
> > Another option would be to simply move BEAMER_HEADER to inject code
> where I
> > have implemented BEAMER_HEADER_EXTRA. That would provide the same
> > functionality with a reasonable name. I still need to bet
Updated patch with updated commit message attached.
On Tue, Mar 10, 2015 at 9:45 AM, Matthew Gidden wrote:
>
>
> On Tue, Mar 10, 2015 at 9:44 AM, Nicolas Goaziou
> wrote:
>
>> Matthew Gidden writes:
>>
>> > Another option would be to simply move BEAMER_HEADER to inject code
>> where I
>> > hav
John Hendy writes:
> On Tue, Mar 10, 2015 at 9:13 AM, Rainer M Krug wrote:
>> Hi
>>
>> I am struggling with float positioning. I would like to have a float at
>> the bottom of a page. Consider the following code:
>>
>> --8<---cut here---start->8---
>> * Some t
`package-pinned-packages' seems to allow for user choice here. It is
still easy to muck up one's installation, but that is between the user
and package.el, not any particular package, I believe.
On Tue, Mar 10, 2015 at 6:01 AM, Alexis wrote:
>
> On 2015-03-10T06:21:10+1100, T.F. Torrey said:
>
>
Eric S Fraga writes:
> On Tuesday, 10 Mar 2015 at 09:50, Rasmus wrote:
>> Nicolas Goaziou writes:
>>> Since this one is not much more intrusive than the previous one, we
>>> could as well drop @key in favor of @{key}.
>>
>> It seems like a moderately dear price to pay for everyone with "normal"
Hi Rasmus,
Thanks, your post was very informative.
Rasmus writes:
> ...
>> Can you turn off the automatic addition of commas in BibLaTeX by setting
>> something in the preamble?
>
> Preamble or using \AtNextCite
>
>> If so, would that be the right solution here? It might be easier to
>> remove
I'm not sure if this counts as a bug or not:
If I run a custom agenda (eg. "R") with sticky agendas, it displays in an
buffer with the name
*Org Agenda (R)*
If this buffer is then renamed to e.g.
(rename-buffer "*R-Agenda*")
*R-Agenda*
And is then refreshed by hitting r, the agenda is properly re
Hi Aaron and all,
Aaron Ecay writes:
> I’ve pushed an update to my branch. The major change is to use
> citeproc-java for the generation of the bibliography and the parsing of
> names.
That is awesome! Thank you for your work.
> The former is straightforward. For the latter, I have created
I could not reproduce this on 8.2.10. I tangled 106 blocks out with no
errors.
XIE Yuheng writes:
> Bug: org-babel-parse-src-block-match reporting "Wrong type argument:
> stringp, nil" when exporting a org-mode file with a lots of code blocks
> [8.3beta (release_8.3beta-895-g375c83 @ /usr/share/e
Steinar Bang writes:
> Isn't this what's MELPA is for?
> http://www.emacswiki.org/emacs/MELPA
MELPA is unable to provide a correctly installable package for Org since
they just pull down the tree and don't do the necessary build steps.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron micr
XIE Yuheng gmail.com> writes:
>
>
> Bug: org-babel-parse-src-block-match reporting "Wrong type argument:
> stringp, nil" when exporting a org-mode file with a lots of code blocks
> [8.3beta (release_8.3beta-895-g375c83
> /usr/share/emacs/site-lisp/org/)]
>
> the following is *Messages* buf
Hi,
I am using babel with awk to generate some LaTeX code that I would like
exported and interpreted as LaTeX. I have the following which works if
I were to use the src block directly but I wish to /call/ the src block
with different tables:
#+begin_src org
,* layout
,#+caption: Position of
Hi Eric,
Eric S Fraga writes:
> Hi,
>
> I am using babel with awk to generate some LaTeX code that I would like
> exported and interpreted as LaTeX. I have the following which works if
> I were to use the src block directly but I wish to /call/ the src block
> with different tables:
>
> #+begin
On Tuesday, 10 Mar 2015 at 08:42, Thomas S. Dye wrote:
[...]
> Have you tried
>
> #+call: drawlayout[:stdin solution]() :results raw
>
> or,
>
> #+call: drawlayout[:stdin solution]() :results latex
>
> which should make the print "#+begin_latex" etc. lines of drawlayout
> redundant?
Both work p
When I export an org file to LaTeX using the class rhs-article, defined as
follows:
‘("rhs-article"
"\\documentclass{article}
\\usepackage[top=1in, bottom=1.in, left=1in, right=1in]{geometry}
[PACKAGES]
[EXTRA]" ;;header-string
On Tue, Mar 10, 2015 at 12:12 PM, John Kitchin wrote:
> As far as I know you have only two options to use refs to a headline in
> Latex export.
>
> 1) Use a CUSTOM_ID property on a heading and then use [[#your-custom-id]] as
> your link. You have to put relevant text in like: see section
> [[#your
Aloha Eric,
Eric S Fraga writes:
> On Tuesday, 10 Mar 2015 at 08:42, Thomas S. Dye wrote:
>
> [...]
>
>> Have you tried
>>
>> #+call: drawlayout[:stdin solution]() :results raw
>>
>> or,
>>
>> #+call: drawlayout[:stdin solution]() :results latex
>>
>> which should make the print "#+begin_latex"
Dear Org-Mode Community,
I have been using Emacs org-mode for about 3 months now, loving every bit
of it so far. One of the killer feartures is the capture from external
applications (e.g. Web Browsers). After some struggling, I can
successfully capture from Firefox and Chrome, but I am still
Matthew Gidden writes:
> Updated patch attached
Applied. Thank you.
Regards,
Richard Stanton writes:
> When I export an org file to LaTeX using the class rhs-article, defined as
> follows:
>
>‘("rhs-article"
> "\\documentclass{article}
> \\usepackage[top=1in, bottom=1.in, left=1in, right=1in]{geometry}
> [PACKAGES]
> [
Hello,
Subhan Michael Tindall writes:
> I'm not sure if this counts as a bug or not:
>
> If I run a custom agenda (eg. "R") with sticky agendas, it displays in an
> buffer with the name
> *Org Agenda (R)*
> If this buffer is then renamed to e.g.
> (rename-buffer "*R-Agenda*")
Why would you nee
emac...@gmail.com (Richard Y. Kim) writes:
> tftor...@tftorrey.com (T.F. Torrey) writes:
>
>> I wonder how much effort it would take to copy onto my own machine the
>> scripts on the server that package the git maint version into an ELPA
>> version, and modify them to package master instead. Prob
Am 10.03.2015 21:04, schrieb Marcin Borkowski:
Hi,
my emacs-installation does not know this as a function or a variable.
Does your emacs respond on `C-h f q u o t e - s e c t i o n' ?
(sorry, if I misunderstood your question)
best regards,
Marc
A remedy from the past cf. org-news.
--
The second rule of Fight Club is: You do not talk about Fight Club
The patch causes an informative error message to be reported for src
blocks like this (no language):
#+begin_src
(+ 1 2)
#_end_src
when exporting instead of failing with a cryptic error message.
Arguably, it would be better to skip the malformed src block as
`org-babel-map-src-blocks' does
On 2015-03-10, at 21:50, Rasmus wrote:
> A remedy from the past cf. org-news.
Thanks!
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
Achim Gratz writes:
> Richard Y. Kim writes:
>> # server.mk has the elpaplus makefile target
>> echo " include mk/server.mk" >> Makefile
> […]
>> # Undo the change made above
>> git checkout Makefile
>
> You know, local.mk was introduced specifically so you wouldn't have to
> do anything like tha
Hello Aaron,
Aaron Ecay writes:
>> If the goal is to have the latest and greatest version of Org available via
>> ELPA (for all the reasons some people use ELPA instead of git), there
>> are two obvious options:
>>
>> 1. Org could have a stable release every month or so.
>>
>> 2. The Org server
Hi Rasmus,
Thanks for your comments. Some replies:
2015ko martxoak 10an, Rasmus-ek idatzi zuen:
>> These are then slurped by org, and used to fill in printf-style
>> templates. Some people mentioned using citations as generated by
>> citeproc-java directly. However, I don’t believe this is rel
I need to insert a table in an mdframed box, for which I need to turn off
:float. The following, however, does not give me the caption:
#+name: milk-consumption-india
#+attr_latex: :float nil :environment tabular :caption
\caption{\label{milk-consumption-india}Average consumption of milk, India,
Hi Richard,
Thanks for your comments, and for your work on an implementation.
2015ko martxoak 10an, Richard Lawrence-ek idatzi zuen:
> I have actually been working on the same problem, using citeproc-hs as
> the CSL processor instead of citeproc-java.
This is an interesting approach. What versi
Hi Terry,
2015ko martxoak 10an, "T.F. Torrey"-ek idatzi zuen:
> Of the things in your list, I think only the NEWS and Changelog are
> absent from the master branch in git. Lots of us happily use Org master
> from git without them every day. Do they really need to be done at
> all?
Many people
I'm trying to use the :session option so I can import modules, etc., just once
at the beginning of my document, like with am IPython notebook. Unfortunately,
the output from these code blocks contains some extraneous characters. For
example:
#+BEGIN_SRC python :session :results output
a = 2
b =
This seems to work:
#+name: milk-consumption-india
#+attr_latex: :placement [H] :environment tabular :caption
\captionof{table}{\label{milk-consumption-india}Average consumption of milk,
India, kilograms per capita per annum}
| Year| Rural | Urban | All |
|--
Aloha Aaron,
Aaron Ecay writes:
> I have made citeproc-java give output like:
>
> Smith2014
> Doe1999
> Smith et al.2005
>
> I parse that into lists of (author, year) pairs by splitting on the
> . Then I expose a template to elisp: “%p%a (%y%s)” (for prefix,
> author, year, and
61 matches
Mail list logo
