Richard Lawrence richard.lawre...@berkeley.edu writes:
1) Is it worth allowing a name for a user-defined type in the [cite:
...] part, or is it OK to confine user-defined types to the second
part (like: [cite: ...] %%(:type foo) or [cite: ...]{:type foo})?
IMHO it is better to have such an
Kyle Meyer k...@kyleam.com writes:
remove description words like Paredit lets you do with S-expressions.
I've put these Paredit-inspired slurping and barfing commands for Org
link descriptions in org-link-edit.el
That's so need!
Did you/will you add it to contrib?
Thanks,
Rasmus
--
This
On Tuesday, 17 Feb 2015 at 22:04, Nicolas Goaziou wrote:
[...]
However, there's a simpler solution. In- ox-odt.el, function
`org-odt-link--infer-description', line 2655 (but it depends on Org
version), there is
(t (error FIXME: Resolve %s destination))
Replace it with
(t (error
On Tuesday, 17 Feb 2015 at 20:03, Richard Lawrence wrote:
[...]
I would personally (aesthetically, don't ask me why) prefer:
[cite/subtype: ...]
as do I as it mirrows mime-types, e.g. text/plain, text/x-org-mode, ...
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org
Hi Melanie,
Melanie Bacou m...@mbacou.com writes:
I'm using ox-html to work on shared documents with my
collaborators. We're working off a Dropbox account and converting our
org files to HTML periodically.
Cool.
Problem with all cloud storages is they don't work with relative links
inside
Hi Glenn,
Damian Nadales wrote:
- Run emacs -Q
- Create an org-mode file (i.e. ``myorgfile.org``)
- Insert the following text:
o #+BEGIN_SRC C++
#+END_SRC
- Edit the source block by placing the cursor inside the SRC block.
[Damian
Hi,
Eric S Fraga e.fr...@ucl.ac.uk writes:
On Wednesday, 18 Feb 2015 at 13:34, Marcin Borkowski wrote:
Hello all,
I need to embed some diagrams (graphs of functions, for instance, or
trees) in an Org file. Any suggestions on how to do it? In case of
ditaa, I can use a source block and the
i have a silly question: whatever syntax we choose, will it be able to
be used, in the future, for new org features nobody has thought of
yet, that are unrelated to citations?
my preference is to forestall future syntax creep, enhance
consistency, and amortize the effort in supporting a syntax
[disclaimer: i do not currently use citations, so i have no stake in
citation syntax per se, just a tendency to ask highly generic silly
questions.]
Richard Lawrence richard.lawre...@berkeley.edu writes:
I know that this is technically easy to handle from the backend's
perspective. But I have a concern related to Stefan's:
Stefan Nobis stefan...@snobis.de writes:
The drawback is that now subtype is hard or even impossible to vary
for
On Wednesday, 18 Feb 2015 at 13:51, Eduardo Ochs wrote:
[...]
perfect, as it supposes that the person trying it has already enabled
latex support in babel!
You mean people don't automatically have this enabled already? ;-)
But, yes, you are correct! My org customisations are so many that I
Hi Samuel,
2015ko otsailak 18an, Samuel Wales-ek idatzi zuen:
i have a silly question: whatever syntax we choose, will it be able to
be used, in the future, for new org features nobody has thought of
yet, that are unrelated to citations?
Do you mean how the syntax and implementation of links
I was thinking the same thing as Aaron ;) What could one do with a
link-like object with arbitrary attributes/properties... Hmm... maybe
this idea:
http://kitchingroup.cheme.cmu.edu/blog/2015/02/05/Extending-the-org-mode-link-syntax-with-attributes/
without the kludgy parsing? It will be so
hi aaron,
On 2/18/15, Aaron Ecay aarone...@gmail.com wrote:
Do you mean how the syntax and implementation of links was used to
support a new org feature completely unrelated to web URLs, namely
citations? ;)
heh heh. :] that applies to the outer syntax only. i mean, for
example, plists
Hi Nicolas,
2015ko otsailak 18an, Nicolas Goaziou-ek idatzi zuen:
I think we should postpone the idea of attributes for object, as it gets
in the way of the discussion. IMO,
[cite/subtype: ...]
is all we need, syntax-wise.
The question of attributes for objects arose out of the desire
Rasmus ras...@gmx.us wrote:
Kyle Meyer k...@kyleam.com writes:
remove description words like Paredit lets you do with S-expressions.
I've put these Paredit-inspired slurping and barfing commands for Org
link descriptions in org-link-edit.el
That's so need!
Did you/will you add it to
Giacomo M jackja...@gmail.com wrote:
[...]
What happens is that in project.org I end up specifying a lot of links all
starting with ~/working/project/. This is useful as I can directly jump
from organization to action, or just to switch in a quicker way across
project files.
[...]
Would you
Hello,
Joost Helberg wrote:
noweb-syntax allows blanks in names of code blocks.
Are you sure? Where did you read that?
The result-blocks of these code blocks are named as well, but have
everything behind the first word stripped. This leads to result-block
collisions in case there are two
Richard Lawrence richard.lawre...@berkeley.edu writes:
Actually, your post has convinced me that it may be worth allowing some
explicit name for a type in the [cite: ...] part of the syntax, although
I am still leery about what this would mean for non-LaTeX backends.
Each back-end can decide
On Wednesday, 18 Feb 2015 at 13:34, Marcin Borkowski wrote:
Hello all,
I need to embed some diagrams (graphs of functions, for instance, or
trees) in an Org file. Any suggestions on how to do it? In case of
ditaa, I can use a source block and the results line, and see the
image with C-c
Hello,
Stormking stormk...@web.de writes:
Without any effect, it seems. I wonder if anybody actually uses these
features.
What character do you suggest to use instead of \emph?
* is not possible due to a collision with bold syntax (i.e. *** is
parsed as a bold star).
Regards,
--
Nicolas
Nicolas Goaziou mail at nicolasgoaziou.fr writes:
Hello,
Stormking stormking at web.de writes:
Without any effect, it seems. I wonder if anybody actually uses these
features.
What character do you suggest to use instead of \emph?
Wouldn't it be better to fix the alignment code so
Hello,
Nicolas Goaziou wrote:
Sebastien Vauban writes:
As you can see on http://screencast.com/t/B0knccOCqco, the output of the
command org-clock-display (bound to C-c C-x C-d) -- which displays
subtree times in the entire buffer -- is partial: for a reason which
still escapes me,
Eric S Fraga e.fr...@ucl.ac.uk writes:
Your suggested change does indeed yield more interesting and, I guess,
potentially more helpful information. The output is:
,
| OpenDocument export failed: FIXME: Resolve #(#+NAME: fig:radar-chart-urea
| #+CAPTION: Radar chart for the urea process
Joost Helberg wrote:
Sebastien == Sebastien Vauban sva-n...@mygooglest.com writes:
Joost Helberg wrote:
noweb-syntax allows blanks in names of code blocks.
Are you sure? Where did you read that?
It's in https://www.cs.tufts.edu/~nr/noweb/johnson-lj.pdf.
Well, that's the real noweb, not
Hello,
Joost Helberg jo...@snow.nl writes:
noweb-syntax allows blanks in names of code blocks. The result-blocks
of these code blocks are named as well, but have everything behind the
first word stripped. This leads to result-block collisions in case
there are two code blocks
Francesco Pizzolante fpz@... writes:
Hi Stormking,
Sorry for my very late reply: I thank you very much for your workaround
which enables me to have well aligned clock tables.
I also take the opportunity to bump up this thread.
Without any effect, it seems. I wonder if anybody actually
Hello all,
I need to embed some diagrams (graphs of functions, for instance, or
trees) in an Org file. Any suggestions on how to do it? In case of
ditaa, I can use a source block and the results line, and see the
image with C-c C-x C-v. Can I do a similar thing with Asymptote? How
Sebastian,
Sebastien == Sebastien Vauban sva-n...@mygooglest.com writes:
From: Sebastien Vauban sva-n...@mygooglest.com
To: emacs-orgmode@gnu.org
Subject: Re: [O] Bug: code blocks with multiple word names create
Date: 2015-02-18T14:06:07+0100
Hello,
Joost Helberg wrote:
On Wed, Feb 18, 2015 at 12:19 PM, Eric S Fraga e.fr...@ucl.ac.uk wrote:
On Wednesday, 18 Feb 2015 at 13:34, Marcin Borkowski wrote:
Hello all,
I need to embed some diagrams (graphs of functions, for instance, or
trees) in an Org file. Any suggestions on how to do it? In case of
ditaa, I
Nicolas Goaziou wrote:
Sebastien Vauban writes:
See `org-clock-display-default-range'. Basically, clock display only
consider clocks in the current year, by default.
For me, what makes more sense is show all (as, unlike dynamic blocks,
we have no visible indication of what's get considered
hi,
noweb-syntax allows blanks in names of code blocks. The result-blocks
of these code blocks are named as well, but have everything behind the
first word stripped. This leads to result-block collisions in case
there are two code blocks starting with the same word.
Is this
Stormking stormk...@web.de writes:
Wouldn't it be better to fix the alignment code so it works with
pretty entities? Because that's the real problem here.
There are two problems here.
One is obviously due to misalignment when using overlays.
The other one is that \emph is not easily readable
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
See `org-clock-display-default-range'. Basically, clock display only
consider clocks in the current year, by default.
For me, what makes more sense is show all (as, unlike dynamic blocks,
we have no visible indication
On Wednesday, 18 Feb 2015 at 14:55, Nicolas Goaziou wrote:
[...]
Apparently `org-odt-inline-image-rules' dismisses pdf files as images.
What happens if you add PDF extension to the list?
Ah ha!
Adding pdf to the list of extensions (using customize, not editing the
code at this point) enables
Stormking stormk...@web.de writes:
You are right but I always have pretty entities turned on, so
it doesn't bother me that much. Wasn't it changed to \emsp
(m-dash) so it would look better in exported HTML or LaTeX?
It was.
Otherwise, I would suggest something like \-- or \__
See above.
Nicolas Goaziou mail at nicolasgoaziou.fr writes:
Stormking stormking at web.de writes:
Wouldn't it be better to fix the alignment code so it works with
pretty entities? Because that's the real problem here.
There are two problems here.
One is obviously due to misalignment when
Stormking stormking at web.de writes:
Wasn't it changed to \emsp
(m-dash) so it would look better in exported HTML or LaTeX?
I have to correct myself on this one, \emsp ist a m-space, not a m-dash
Hi Nicolas and all,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
Actually, your post has convinced me that it may be worth allowing some
explicit name for a type in the [cite: ...] part of the syntax, although
I am still leery about
Aaron Ecay aarone...@gmail.com writes:
Hi Nicolas,
2015ko otsailak 18an, Nicolas Goaziou-ek idatzi zuen:
I think we should postpone the idea of attributes for object, as it gets
in the way of the discussion. IMO,
[cite/subtype: ...]
is all we need, syntax-wise.
The question of
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
We have already seen a couple of examples in this thread of properties
that one might want to specify in a backend-agnostic way:
- special-case capitalization
- user-defined
I know the hooks are in there somewhere, but is there any relatively
straightforward way to set a particular property, or run a function to do so,
when a TODO changes status to a DONE state?
Thanks!
Subhan
This message is intended for the sole use of the individual and entity to which
it is
Hi,
When I call org-time-stamp (C-c .) from Emacs -q and give a time such as
11:00 and nothing else I get 2015-02-19. I would expect something
like 2015-02-19 11:00, as in v8.2.
—Rasmus
--
Slowly unravels in a ball of yarn and the devil collects it
Dear all,
I'm experimenting the following path structure:
1. ~/org/ is where I keep all my org files for organization purposes (e.g.
project.org contains all TODOs, notes, events, and links related to
project) and is sync'd with a GIT server.
2. ~/working/project/ is where I keep all the
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Since KEYWORDS and DESCRIPTION are really back-end dependant, I vote for
moving them from `org-export-options-alist' to back-end definitions.
Using `org-element-parse-secondary-string' will be required in this
case.
WDYT? Also, supposing you
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Perhaps there are clever ways to figure it out. I say there are too many
dynamics and fixes in the code to get cdlatex-environment to work
already. Just consider this example where | is cursor
- foo | bar
Midway through, when ENV is
46 matches
Mail list logo
