Hi!
torys.ander...@gmail.com (Tory S. Anderson) writes:
2) As Peter originally mentioned, I see only five tasks on the list; I
have more than that each week. Can this be expanded with some
variable?
AFAICS this is variable org-clock-history-length.
Having looked into problem 2 by going to
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Thank you. I have applied a slightly different patch.
Thanks!
The formatting is still not optimal, however, as you can end up with
something like
[...]
I guess a threshold would then be needed, though, as the following is
still nice and
Excellent answers, on both fronts. Thanks! I couldn't spot
`org-clock-history-length` in the code. That does the trick!
Thanks for the answer about the ?A. It's devilishly hard to Google that kind
of thing... time to RTM.
Marco Wahl marcowahls...@gmail.com writes:
Hi!
Hello,
Rasmus ras...@gmx.us writes:
Consider the following example:
(with-temp-buffer
(require 'ox-ascii)
(insert
-
[[http://www.npr.org/blogs/monkeysee/2009/03/a_very_long_url_makes_a_very_s.html][A
label with a long link]] :: Lorem ipsum dolor sit amet, consectetur
Now I'm loving this tool but I'm looking for two tweaks that would make a big
difference.
1) I use work.org to track my weekly work hours; each week is mostly the same
tasks, but new time frames. I need to be able to make sure my recent clock
list is talking about the item for this week, not
Tory S. Anderson wrote:
Sebastien Vauban sva-n...@mygooglest.com writes:
Peter Münster wrote:
On Sat, Jan 24 2015, Peter Münster wrote:
- There are duplicates in the list.
Not reproducible.
I still do have duplicates in my list as well. It never has been fixed,
but I don't have either a
Hello!
I did HTML export with INFOJS enabled.
Document has deeply nested nodes.
When I link to relatively major nodes, generated URL looks like:
javascript:org_html_manager.go(3)
And clicking it works well. Corresponding node will open.
But when I link to even deeper node, URL now becomes
Right now I see that =formatted= and ~formatted~ both produce
codeformatted/code when exported to html. How can I change one of these,
perhaps to a custom tag (in particular, I'm hoping to produce
kbdformatted/kbd)?
Thank you Willem,
This looks very helpful.
I am trying the code out in a scratch buffer and I am unable to gnerate
org
syntax, e.g. with this test string:
(h-2-o-insert-org-source-for-html pa
href=\http://example.org/\;hello/a
span style=\font-style:italic;\worldbr/ foo/span/p )
Am
i think I may have seen it these on the list at one point, but it's very
helpful to be reminded.
I do think that the default fonts, etc., are a bit of an acquired taste for
humanists; and I've gotten used to using custom styles in html odt for
size placing of images; but even without following
Looks like an infloop due to display or overlay strings with text
properties. Can you reproduce this in an unoptimized build?
Sure, if you can point me to such a version I can download.
https://sourceforge.net/projects/emacs-bin/files/snapshots/debug/
HTH
--
Dani Moncayo
Hello fellow Orgers,
can I find a list of special tags somewhere? By special I mean
e.g. :export:, :noexport: and :archive: - they are treated specially by
Org. Are there any others like that?
TIA,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and
On 2015-01-28, at 21:40, Tory S. Anderson torys.ander...@gmail.com wrote:
Right now I see that =formatted= and ~formatted~ both produce
codeformatted/code when exported to html. How can I change one of these,
perhaps to a custom tag (in particular, I'm hoping to produce
kbdformatted/kbd)?
All the discussion about citations has gotten me thinking. It is easy
enough to export cite links to the pandoc format, including pre and post
text. I have done a proof of concept of this in a markdown export.
I would like to do an org export to org, with the goal of the exported
org document to
With the latest version of org-ref, I can automate export from org
through markdown to docx via pandoc like this:
#+BEGIN_SRC emacs-lisp
(defun ox-export-to-docx-and-open ()
Export the current org file as a docx via markdown.
(interactive)
(let* ((bibfile (expand-file-name (car
Hi there again,
I can do
(member-ignore-case sometag (org-element-property :tags element)),
but I'd like to know whether some element has the tag, not taking
inheritance into account. Is there a simple way to do it? (If not,
I'll consider using properties instead of tags for my purpose - but
John,
this does look very powerful. Do you see a path forward that would help
add zotero support to org-ref, probably using Erik's zotxt library? Does
that seem like a worthwhile goal for you?
Matt
On Wed, Jan 28, 2015 at 6:01 PM, John Kitchin johnrkitc...@gmail.com
wrote:
With the latest
John Kitchin johnrkitc...@gmail.com writes:
All the discussion about citations has gotten me thinking. It is easy
enough to export cite links to the pandoc format, including pre and post
text. I have done a proof of concept of this in a markdown export.
I would like to do an org export to
Hey Tory,
torys.ander...@gmail.com (Tory S. Anderson) writes:
There seems to be (and has been for a while) a growing Japanese
presence online with orgmode materials, documentation, addons,
etc. Most recenlty I found this blog:
http://paper.li/highfrontier/1300501273 . I had also noticed many
in pursuit of the zotero integration I discussed in other threads, I am
trying to write one simple little function to extend Erik's code, and
failing. Since I'm flailing and going to bed soon: can anyone see what's
wrong with this function?
The results are generated perfectly well, but the
I can see how you could have a command insert links from a zotero database.
You just need some way to get a list of the keys for that. it looks like
zotxt could provide that. if not, it could be a few sqlite commands to get
it.
Lets say we have citations like: zotero:zotero-key or [@zotero-key].
Hi, when I export a full path figure,
like: [[file:c:/Users/admin/Desktop/1.png]]
to LaTex. Unfortunately I got the result of
{//c:/Users/admin/Desktop/1.png},
one more // was generated in front of c:, which is an error in LaTex.
How can I solve this problem?
With the latest version of org-ref, I can automate export from org
through markdown to docx via pandoc like this:
Great job, once again!
Vikas
Button Show Org source on page
http://orgmode.org/worg/code/org-info-js/
does not work.
When I click it, some text quickly flashes and disappears.
Tried on recent Google Chrome and Opera browsers.
Best regards,
Svjatoslav
24 matches
Mail list logo
