On Wednesday, 30 Apr 2014 at 16:59, John Kitchin wrote:
Greetings,
All the talk about citations in org-mode inspired me to finish and polish
some code I have been working on for my group for a while on
bibtex/reftex/org-mode integration. I packaged it up in a literate
programming org-file
From 9191e4a364e251119cf8b7c72e41f6c0d09583f2 Mon Sep 17 00:00:00 2001
Message-ID: 87ha5aqa93@treetowl.lan
MIME-Version: 1.0
Content-Type: text/plain
*lisp/org.el: Advise commands which jump to the mark
---
There are several non-org commands that jump to a location and would be
unwieldy if
From dc0b727328266785528fe160046ae1aa8df8a993 Mon Sep 17 00:00:00 2001
Message-ID: 87zjj2ous9@treetowl.lan
MIME-Version: 1.0
Content-Type: text/plain
* lisp/ob-core.el: Test that all elements are in a list are lists
instead of just the first.
org-babel table output uses different formatting
Ian Kelling writes:
org-babel table output uses different formatting for a list of lists,
but detects it incorrectly causing an error, as in this example:
#+begin_src emacs-lisp
'((1) 2)
#+end_src
So this isn't a proper table, what do you expect to happen?
-
Achim Gratz strom...@nexgo.de writes:
Ian Kelling writes:
org-babel table output uses different formatting for a list of lists,
but detects it incorrectly causing an error, as in this example:
#+begin_src emacs-lisp
'((1) 2)
#+end_src
So this isn't a proper table, what do you expect to
Charles C. Berry ccbe...@ucsd.edu writes:
On Wed, 30 Apr 2014, Rainer M Krug wrote:
Charles Berry ccbe...@ucsd.edu writes:
Rainer M Krug Rainer at krugs.de writes:
Hi
Attached please find seven patches for review to implement the storing
of org variables in their own environment and to
Ian Kelling i...@iankelling.org writes:
Achim Gratz strom...@nexgo.de writes:
Ian Kelling writes:
org-babel table output uses different formatting for a list of lists,
but detects it incorrectly causing an error, as in this example:
#+begin_src emacs-lisp
'((1) 2)
#+end_src
So this
Ian Kelling i...@iankelling.org writes:
Below is a patch that addresses the 2 previously mentioned
problems.
It's a bit late. here is the same patch with correct indentation.
-- 8 --
Subject: [PATCH] Fix error prone babel table output format detection
* lisp/ob-core.el: Test that all
Ian Kelling i...@iankelling.org writes:
It's a bit late. here is the same patch with correct indentation.
That patch went out of it's way not to check more of the list than was
necessary, but after sending it, I kept thinking that it does extra
things which possibly negate any performance
John,
I've been playing with the package although, so far, only for
citations. A few points:
1. Do you have any support for choosing the type of citation entry
(i.e. \cite versus \autocite versus ...) when inserting a
citation in the text?
2. You define org-link-types.
Hi,
How I can convince github to recognize the '#+TITLE:' field of an
org-file? This should be a 'h1' heading, while it is currently treated
as normal text (for example, see
https://github.com/julian-gehring/vignettes/blob/master/README.org). I
know that this is a problem of the parsing on
Julian Gehring julian.gehr...@gmail.com writes:
Hi,
How I can convince github to recognize the '#+TITLE:' field of an org-file?
This should be a 'h1' heading, while it is
currently treated as normal text (for example, see
Hello Shin,
On 2014-04-30 20:17 Shin Sungmin wrote:
But, how does it make it easier to assign a person to a task in my
todo.org? Is there any type of auto complete functionality?
You have the function org-contacts which helps you search through your
contacts. From there you can quickly jump to
Julian Gehring wrote:
How I can convince github to recognize the '#+TITLE:' field of an org-file?
This should be a 'h1' heading, while it is currently treated as normal text
(for example, see
https://github.com/julian-gehring/vignettes/blob/master/README.org). I know
that this is a problem
Hi Eric,
Now that you have mentioned it, do you have a good web resource / manual
for your set up, or would you mind sharing bits of it? It looks eminently
useful. I have a set up largely following this
Thanks for the feedback. I moved the key-bindings for f10-12 out of org-ref.
On Thu, May 1, 2014 at 6:01 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote:
John,
I've been playing with the package although, so far, only for
citations. A few points:
1. Do you have any support for choosing the type
sorry, premature send!
On Thu, May 1, 2014 at 8:36 AM, John Kitchin jkitc...@andrew.cmu.eduwrote:
Thanks for the feedback. I moved the key-bindings for f10-12 out of
org-ref.
On Thu, May 1, 2014 at 6:01 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote:
John,
I've been playing with the package
Hi Seb,
Nice. So it seems that github is using an older version of org-ruby. Is
it clear what the update policy/cycle of github for softwares like
org-ruby is?
Best wishes
Julian
On 01.05.2014 14:17, Sebastien Vauban wrote:
Julian Gehring wrote:
How I can convince github to recognize
On Thursday, 1 May 2014 at 08:47, John Kitchin wrote:
[...]
Hi John,
thanks for your quick response!
an alternative would be to use a prefix command that gave you an option to
change the cite format, similar to the minibuffer menu for cite links. I
have not written much prefix code before,
On Thursday, 1 May 2014 at 08:21, Seb Frank wrote:
Hi Eric,
Now that you have mentioned it, do you have a good web resource / manual
for your set up, or would you mind sharing bits of it? It looks eminently
useful. I have a set up largely following this
Hello,
Particularly in the Org Beamer documentation, headlines seems the most
used term while there is a tag ignoreheading...
I have the impression that both terms (heading and headline) are
synonyms. Though, is this true, or is there some subtle nuance?
Best regards,
Seb
--
Sebastien
I've searched the docs, and looked through my .emacs and custom.el files, but
I don't see anywhere that lets me set the default view for the Agenda.
I would like it to come up in Fortnight mode as a default. Is this possible?
Thanks.
Dave in New Port Richey, FL
Julian Gehring wrote:
On 01.05.2014 14:17, Sebastien Vauban wrote:
Julian Gehring wrote:
How I can convince github to recognize the '#+TITLE:' field of an
org-file? This should be a 'h1' heading, while it is currently
treated as normal text (for example, see
J. David Boyd wrote:
I've searched the docs, and looked through my .emacs and custom.el files, but
I don't see anywhere that lets me set the default view for the Agenda.
I would like it to come up in Fortnight mode as a default. Is this possible?
(setq org-agenda-span 'fortnight)
?
Best
Dave,
J. David Boyd wrote:
I've searched the docs, and looked through my .emacs and custom.el files, but
I don't see anywhere that lets me set the default view for the Agenda.
I would like it to come up in Fortnight mode as a default. Is this possible?
I can't recall if there is specific
Sebastien Vauban sva-n...@mygooglest.com writes:
J. David Boyd wrote:
I've searched the docs, and looked through my .emacs and custom.el files,
but I don't see anywhere that lets me set the default view for the Agenda.
I would like it to come up in Fortnight mode as a default. Is this
Charles Millar mill...@verizon.net writes:
Dave,
J. David Boyd wrote:
I've searched the docs, and looked through my .emacs and custom.el files,
but I don't see anywhere that lets me set the default view for the Agenda.
I would like it to come up in Fortnight mode as a default. Is this
I implemented some of this partially. I made it so you can specify the
default cite link in a user variable, with a default of cite. When you type
C-c ], this format will automatically be used. If you want to choose
another format, type C-u C-c ] which will prompt you for a type, and then
use the
Using org-mode version 7.93f, when exporting to ASCII it doesn't respect
the current fill column. Can this be enforced?
Also, I've noticed that org doesn't remove verbatim tags (=verbatim=)
but removes BEGIN_EXAMPLE blocks and presumably other BEGIN_xxx blocks;
is this by design?
Yes, i meant org-contacts.I created a file I called people.org and I input some contacts in it.But, how does it make it easier to assign a person to a task in my todo.org? Is there any type of auto complete functionality? Do I have to make a manual link to the people.org file instance to be
Thank you for your quick reply Eric.Using M-x customize-group RET org RET was one of the first things I did. Maybe even the first thing I did in Org-mode to try to get a better understanding about what is possible.It is really amazing how customizable everything is. That is why it would be
Nicolas Goaziou n.goaz...@gmail.com writes:
I would like to install the following patches on master. Basically, they
consist of a full rewrite of all indentation related functions, with
explicit rules in docstrings, comprehensive test suites, and backed-up
by the parser.
Here's an update for
Perhaps you are doing cutting edge stuff that no one has even
considered before, which is great.
Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi
gret...@acm.org | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become
A discussion about contacts, etc. from a couple of years ago might be
useful.
http://comments.gmane.org/gmane.emacs.orgmode/57972
Charlie Millar
If it intended that setting :mkdirp yes should break tangling with
'directory-free' file names?
I.e., should
#
#+TITLE: test
#+BEGIN_SRC python :mkdirp yes :tangle test.py
print 1+2
#+END_SRC
###
tangle without error?
It currently doesn't because (file-name-directory
Hi,
Org-mode version 8.2.6. Loaded from MELPA org-2014-04-28.
The nice github flavored markdown package is in there ox-gfm.el.
My goal is to use it to do a Markdown export of an org document
instead of the vanilla exporter.
In an attempt to do so, I ran at startup:
(require
Shin Sungmin sungsongs...@daum.net writes:
Well, I will just look through the old survey
(http://orgmode.org/worg/org-configs/org-customization-survey.html) I
am sure that will give a ton of ideas as well.
Beware however that some variable names (in particular, export-related
ones) were
Hi,
Org 8.2.6, Emacs 24.3.1.
Working on large literate org documents takes a lot longer when ispell
reports errors in the source
code. My goal is to avoid spell checking anything inside the source
blocks. For example the following lines would not be spell checked at
all:
#+begin_src emacs-lisp
Miguel Guedes miguel.a.guedes at gmail.com writes:
Using org-mode version 7.93f, when exporting to ASCII it doesn't respect
the current fill column. Can this be enforced?
Miguel,
Upgrade to current org-mode (version 8.2.6) before you do anything else.
Then modify `org-ascii-text-width' to
Grant Rettke gcr at wisdomandwonder.com writes:
Hi,
Org-mode version 8.2.6. Loaded from MELPA org-2014-04-28.
The nice github flavored markdown package is in there ox-gfm.el.
My goal is to use it to do a Markdown export of an org document
instead of the vanilla exporter.
In an
Hello:
this is another small patch to org-capture.el to make sure that after
completion it returns to the same place from where it was invoked. This way
users won't loose track of where they were before capturing something. The
minimal setup to reproduce the case where capture fails to return to
sorry, I accidentally sent my previous patch. This is the one that belongs
here.
On Thu, May 1, 2014 at 7:00 PM, Alex Kosorukoff a...@3form.com wrote:
Hello:
this is another small patch to org-capture.el to make sure that after
completion it returns to the same place from where it was
Charles,
Thanks very much for the tips -- they certainly helped!
Miguel
On 02/05/14 00:56, Charles Berry wrote:
Miguel Guedes miguel.a.guedes at gmail.com writes:
Using org-mode version 7.93f, when exporting to ASCII it doesn't respect
the current fill column. Can this be enforced?
On 04/30/2014 05:55 PM, Brady Trainor wrote:
Hi, I was curious if anyone had org-protocol working on Fedora.
...
It's working in Opera on Fedora.
Brady
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
I would like to install the following patches on master. Basically, they
consist of a full rewrite of all indentation related functions, with
explicit rules in docstrings, comprehensive test suites, and backed-up
by the parser.
Wish I was
Hi, yes this issue would be fixed once Github upgrades the Ruby
implementation of the parser.
To upgrade the version it takes making a pull request to the github/markup
repository so that they bump the version and do the release, but it takes
some time before the upgrade is validated (security
46 matches
Mail list logo
