Hi Ross,
thanks for the patch. Do you mind filling the copyright
assignment so we can accept the patch ?
http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt
Also, please have a look at this page with guidance on how
to submit a patch with a ChangeLog etc.
http://orgmod
Hi Nicolas,
Nicolas Goaziou writes:
> I tend to think it's more a developer information. By looking at the
> manual, there's no confusion possible for a user.
A footnote would not hurt, if only as a way to answer future
questions?
> Maybe it should go in `org-export-options-alist' docstring in
On 28-06-13 04:26, Nick Dokos wrote:
> Rasmus writes:
>
> The old latex exporter was much more finicky about such structure
> violations: I tried 7.7 (and 7.9.4 to see if it was ever changed) and it
> does indeed eat the subsubsection.
>
>> To solve your problem:
>> 1. see if it works as expec
Hello,
I'm trying to find a way to create an agenda bloc (of type agenda) that
is restricted to a set of tags. I tried using a skip function but (as I
explained in another mail) I cannot get it to work. If someone has done
it before, I'd gladly have a look at how to do it.
Thanks,
Alan
Alan Schmitt writes:
> Hello,
>
> I'm trying to find a way to create an agenda bloc (of type agenda) that
> is restricted to a set of tags. I tried using a skip function but (as I
> explained in another mail) I cannot get it to work. If someone has done
> it before, I'd gladly have a look at how
Hi Noorul,
noo...@noorul.com writes:
> Alan Schmitt writes:
>
>> Hello,
>>
>> I'm trying to find a way to create an agenda bloc (of type agenda) that
>> is restricted to a set of tags. I tried using a skip function but (as I
>> explained in another mail) I cannot get it to work. If someone has d
* Peter Salazar wrote:
>
> Github supports org-mode files, and has a renderer that parses .org files
> and converts them to HTML form. Headings appear in larger font, org tables
> are converted to graphical HTML tables, etc.
If you want to know, what features are supported by github, take a
look
* Rick Frankel wrote:
> And here's a simplier version which uses a graph table in the
> following format:
[...]
I tried to use your solution with the "#+call:" method.
Unfortunately, it fails and due to my limited ELISP knowledge, I can
not debug this issue. I've got the feeling that you might
Hello,
Yoshinari Nomura writes:
> Thanks, you encouraged me. Also, while I made this patch, I was in
> the mood for consolidating some exporter-local functions around the
> captions. Especially, ox-odt and ox-ascii seem to have rich functions to
> add ordinal numbers to captions. It might be ove
Hello Nicolas,
Nicolas Goaziou wrote:
>> What do you call a recent Org? I'm blocked on commit 26a9b02, from May 27th,
>> as long as the #+SETUPFILE: bug is not fixed (fontification is broken).
>>
>> So, is that one (4 weeks old) a recent Org?
>
> No. I fixed it ten days ago (dffdc49).
Though I'm
Bastien gnu.org> writes:
> > The way elpa works, it automatically adds packages to `load-path'. There is
> > therefore no need to have such a line
> >
> > (add-to-list 'load-path (or (file-name-directory #$) (car load-path)))
> >
> > in the `package-autoloads.el" file.
>
> Where is this file?
Rene writes:
>> > The way elpa works, it automatically adds packages to `load-path'. There
>> > is
>> > therefore no need to have such a line
>> >
>> > (add-to-list 'load-path (or (file-name-directory #$) (car load-path)))
>> >
>> > in the `package-autoloads.el" file.
>>
>> Where is this file?
Hi Xiao-Yong,
I have applied this patch, thank you.
- Carsten
On 28.6.2013, at 06:55, Xiao-Yong Jin wrote:
> On Jun 1, 2013, at 3:17 PM, Carsten Dominik wrote:
>
>> Hi Xiao,
>>
>> I remember that I struggled with the problem that I had to make sure that
>> column view used a fixed-width fa
You are right, I forgot about that. I also have (setq
bidi-paragraph-direction nil) in my org-mode-hook.
Regadrs,
Dov
On Wed, Jun 26, 2013 at 4:49 AM, Manuel GJT wrote:
> It turns out that org mode does force directionality in its buffers. I found
> in org.el the line
>
> 5308 (setq bidi-parag
Hi Nicolas,
On Fri, 28 Jun 2013 11:23:41 +0200,
Nicolas Goaziou said:
> (setq caption-predicate
> (if (org-element-property :caption destination)
>(lambda (elem &optional info)
> (org-element-property :caption elem))
> (lambda (elem &optional info)
>
Achim Gratz nexgo.de> writes:
> > Line 4 of `org-autoloads.el" in org/elpa package.
>
> Since this file is created by package manager this is probably how it
> adds Org to the load path, don't you think?
What I notice is that for elpa packages that don't hold such a line in their
`package-autol
On Thu, 27 Jun 2013 17:32:17 +0200 Bastien wrote:
> Just one question: do you get feedback from todo-mode.el users?
> Do you know if there are some/many out there? Just curious to
> see other's people use.
Since I became the maintainer more than four years ago there haven't
been any bug reports
On 2013-06-28 05:20, Karl Voit wrote:
* Rick Frankel wrote:
And here's a simplier version which uses a graph table in the
following format:
[...]
I tried to use your solution with the "#+call:" method.
Unfortunately, it fails and due to my limited ELISP knowledge, I can
not debug this issue.
So I tried adding a "(nil)" in the custom agenda section. If this were
allowed (presumably ignored), I could write a function that returns nil
unless there were items tagged REFILE, in which case it would return
(tags "REFILE" ((org-agenda-overriding-header "REFILE")))
But having (nil) caused a
export as html is crashing with this (from *Messages* buffer)
org-export-preprocess-string: Wrong number of arguments: (then all sorts of
unprintable chars)
---
(setq
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-metaup-hook
On Fri, Jun 28, 2013 at 10:42 PM, Rustom Mody wrote:
> export as html is crashing with this (from *Messages* buffer)
>
> org-export-preprocess-string: Wrong number of arguments: (then all sorts
> of unprintable chars)
>
I should have added this information
The file I am exporting is just these
it seems that the :colnames header is not being respected on parsing the
input
to a `#+call:' line containing arguments, but is being applied to the
output!
For example:
#+BEGIN_SRC org
* Identity
#+name: table
| a | b | c |
|---+---+---|
| 1 | 2 | 3 |
#+name: identity
#+BEGIN_SRC emacs-lisp
Rustom Mody writes:
> On Fri, Jun 28, 2013 at 10:42 PM, Rustom Mody wrote:
>
> export as html is crashing with this (from *Messages* buffer)
>
> org-export-preprocess-string: Wrong number of arguments: (then all sorts
> of unprintable chars)
>
> I should have added this information
Hi All,
I am just starting to dig into using the new exporter for generating
beamer presentations.
I want to include my collaborators in the header of each org file just
as I would authors, that is by including a line like
#+COLLABORATORS: Alice & Bob
I've found some limited documentation on mo
Hi List,
I wonder how I can find out in a (elisp) program the points in the parse
tree (returned by org-element-parse-buffer) where shared structures are
used.
In the read-syntax, its easy to see (especially with `print-circle' set
to non-nil):
#+begin_src emacs-lisp
#2=(org-data nil #1=(he
Josiah Schwab writes:
> Hi All,
>
> I am just starting to dig into using the new exporter for generating
> beamer presentations.
>
> I want to include my collaborators in the header of each org file just
> as I would authors, that is by including a line like
>
> #+COLLABORATORS: Alice & Bob
>
> I
Thorsten Jolitz writes:
> Hi List,
>
> I wonder how I can find out in a (elisp) program the points in the parse
> tree (returned by org-element-parse-buffer) where shared structures are
> used.
>
> In the read-syntax, its easy to see (especially with `print-circle' set
> to non-nil):
>
> #+begi
> Maybe, maybe not. Difficult to say unless you give us a better idea of
> what kind of changes you plan on making.
I'm a little hazy, partially because my ideas seem to change quickly as
I learn more.
One of the more ambitious things that I'd like to do is to be able to
associate BibTeX referen
I confirm the following bug in git master.
P.S. One possibility for the OP's question would be to allow a
special prefix arg to select the list item and its children as a
region then call refile region.
On 1/17/12, Jeff Horn wrote:
> On Wed, Aug 17, 2011 at 05:32, Bastien wrote:
>> I pushed th
Hello!
Here comes another (tiny) patch which fixes generation of external links
to relative file paths.
Apparently =./Media/logo.png= has to be inserted as
=href=../Media/logo.png=.
At least on LibreOffice 3 and 4 anything else fails. LibreOffice always
shows and uses the
absolute path an
Daimrod writes:
> Thorsten Jolitz writes:
[...]
>> but when processing the parse tree as a list in elisp, how can I
>> detect the fact that
>>
>> ,
>> | :parent #2#
>> `
>>
>> refers to
>>
>> ,-
>> | #2=(org-data nil
>> `-
>>
>> i.e. poi
Hello,
how can I customize "info:" links in HTML output?
I'd like replace "info:" links with HTML links to the corresponding
upstream manuals, such as
http://www.gnu.org/software/emacs/manual/html_node/emacs/Commands.html#Commands
for an info link "info:emacs#Commands", just like in Texinfo HTML
Hello,
"Sebastien Vauban"
writes:
>> No. I fixed it ten days ago (dffdc49).
>
> Though I'm now on Org-mode version 8.0.3 (release_8.0.3-295-g91a4c8), pulled
> this morning, I don't see it fixed.
I realize that the patch won't fix it. This patch was introduced to
allow something like:
#+begi
HI:
In my thesie, I need add a caption to table or figure with
\bicaption{中文标题}{English title}
I can't find the easy way to do this in org-mode ,so I add :caption to
#+attr_latex:
for example:
#+attr_latex: :caption \bicaption{...}{}
But the below function doesn't work as expected, som
Bastien writes:
> thanks for the patch. Do you mind filling the copyright
> assignment so we can accept the patch ?
I already have an FSF Emacs Assignment from 2008-12-22, RT 393650. Is
there something else I need to do?
> http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future
hi, Bastien,
>> hi. what happened to this patch? i don't see it anywhere. cheers!
> Can you give a pointer to "this" patch?
here is the thread:
http://comments.gmane.org/gmane.emacs.orgmode/64229
cheers, Greg
Nick Dokos wrote:
> emacs version? org version? backtrace?
> I cannot reproduce with ...
>
Ok I thought the org-submit-bug takes care of all this. Find it is partly
true -- dont see emacs version in my report. So
GNU Emacs 23.4.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.12) of 2012-09-22
on alls
37 matches
Mail list logo