Hi,
I have been using a link containing elisp:(org-beamer-export-to-pdf nil t) to
export the subtree as a beamer pdf. It used to work well, but after a certain
update a couple of months ago (I'm using 8.3beta and I regularly update it), it
stopped working properly. For example, when I click on t
thanks. that also works for me.
Samuel Wales writes:
> i always put inactive timestamps in headlines, and sort both the
> outline and agenda using them. for example:
>
> * CONVERSATION [2015-08-31 Mon 14:41] john
> * CONVERSATION [2015-09-01 Tue 15:02] rms
>
> or newest first. they are
Thanks. org-ref has been pretty stable lately, and given my fall
schedule it is likely to stay that way ;)
It might be ready for MELPA. I don't have a lot of experience packaging
for MELPA. Is there a set of instructions on how to do that somewhere?
Erik Hetzner writes:
> Thanks, John.
>
> I was
I think there's some misunderstanding here regarding my initial question.
I do NOT want the subheading to go between the first one and the logbook.
When I hit Ctrl-Enter at the end of the line, that's where it goes. I
didn't choose to do that, and I would like it not to. To get what I want
now, I
On 4 September 2015 at 13:35 PDT, Josiah Schwab wrote:
> I think there's a "-" missing. The variable name is
>
> org-agenda-custom-commands
> ^
This is also now fixed on the website (worg commit 60c0b12).
Best,
Josiah
Keith M Swartz writes:
> Step-by-step -- after step 1 [note: the logbook is collapsed initially, but
> I expanded it here to show the contents. Expanding the logbook before
> creating a sub-item may alter the results; I haven't tried that.]
>
> * TODO First item
> :LOGBOOK:
> - State "TODO"
M-x 'org-mobile-push', with the latest org-mode leaves the files
incompatible with MobileOrg Android application. There have been no changes
in MobileOrg for over a year.
I bisected the latest org-mobile related changes and noticed that reverting
this one line below "fixes" the issue (at least for
Hello Tobias,
On 4 September 2015 at 12:49 PDT, Tobias Frischholz wrote:
> I have a small problem with a key binding for the agenda, which should import
> my iCal.app appointments into the diary.
>
> I have the following code from this page:
>
> (setq org-agenda custom-commands
> '(("I" "
I was creating the sub-heading from the exact same spot where I stopped
typing and hit C-c C-t. Didn't move the cursor, just went straight from one
step to the next.
After step
Here is what that set of steps created for me:
* PEND First item
:LOGBOOK:
- State "PEND" from "TODO" [2015
Indirect buffers are of immense help but I had the same issue.
Can confirm that the hack referring to spec instead to the
buffer-file-name and getting the buffer-base-buffer respectively, does
the trick.
Great!
On 2015-09-04 Fri 17:49, Kyle Meyer wrote:
> Rainer M Krug writes:
>
>> Hi
>>
>> it
I have a small problem with a key binding for the agenda, which should import
my iCal.app appointments into the diary.
I have the following code from this page:
(setq org-agenda custom-commands
'(("I" "Import diary from iCal" agenda ""
((org-agenda-mode-hook
(lambda ()
Keith M Swartz writes:
> Here is an example to reproduce some questionable results:
>
> 0. Create a set of TODO labels, like so:
> #+SEQ_TODO: TODO(!) PEND(!) DONE(!)
>
> 1. Create an item, make it a todo. (Creates a logbook.)
OK.
> 2. Create a subheading. (Alt-Enter, shift-right)
>From where?
On Sat, Aug 8, 2015 at 8:54 AM, Ista Zahn wrote:
> Unfortunately I now can't reproduce the problem, so I can't check if
> my suggestion to byte compile ob-R.el works or not.
For those still having this issue.
I do confirm this solves the problem that occurred upon upgrading Org
via ELPA on 64-
Thank you, Nicolas.
I think this behavior is wrong, then, or else I have some configuration
setting that's messing things up. Problem is, if you create sub-level
todos, and change their state, the updates all get muddled, and you can't
tell which one's state changed. It also creates multiple logbo
Nicolas Goaziou writes:
> Jon Miller writes:
>
>> At this point, I'm not sure if there is any further hacking left to be done
>> to the original patch I sent? Are we okay with just leaving the two options
>> of 'ascii and 'org?
>
> I don't think we're at a conclusion yet. In addition to providin
Jon Miller writes:
> At this point, I'm not sure if there is any further hacking left to be done
> to the original patch I sent? Are we okay with just leaving the two options
> of 'ascii and 'org?
I don't think we're at a conclusion yet. In addition to providing ascii
and org, we might also
-
Hello,
Keith M Swartz writes:
> I often want to add a subheading (sub-task) to this todo item, so I'll hit
> Alt-Enter to do this. When I do, it creates the subheading /between/ the
> original todo and the drawer. Is that correct?
It is.
> My preference - and what I would have assumed to be th
Fernando Varesi writes:
> Given the documentation in
> http://orgmode.org/manual/Structure-editing.html#Structure-editing, I would
> expect it to still use org-move-subtree-down.
This is bound to M-down, isn't it? It probably is a documentation bug.
Regards,
Dear Thomas.
> you could revert to your working org installation (if you did not delete
> that folder) by deleting / moving the folder with the faulty
> installation (say "org-201508XX") from your .emacs.d/elpa directory.
> If this solves your problems, then I would recommend starting a "bare"
Hi, Nicolas. Thanks for replying
Given the documentation in
http://orgmode.org/manual/Structure-editing.html#Structure-editing, I would
expect it to still use org-move-subtree-down.
Anyway, my desired behavior can be easily achieved with hooks so I don't
mind it keeping it as is, but I thought t
Hello,
Fernando Varesi writes:
> Steps to reproduce:
> 1. Create an outline with 2 headlines, each of them having their own drawers.
> 2. Move the pointer to the headline.
> 3. Hit M-S-down.
>
> Expected Behavior:
> M-S-up/down should move the subtree/item up/down when pointer is in a
> headlin
Hi,
Martin Kaffanke writes:
> Hi there,
>
> I can see now, that (org-entry-get (point) "foo") is nil, if
> :PROPERTIES: follows the CLOCK: entry. Has it changed to be that
> :PROPERTIES: now must be the first thing of the entry?
Yes.
> If so, how can I
> change all my entries at once instead
Hi there,
I can see now, that (org-entry-get (point) "foo") is nil, if
:PROPERTIES: follows the CLOCK: entry. Has it changed to be that
:PROPERTIES: now must be the first thing of the entry? If so, how can I
change all my entries at once instead of going through all my items and
do it by hand?
Hi Nicolas
On Thu, Sep 3, 2015 at 4:06 PM, Nicolas Goaziou wrote:
> Can't you simply do
>
> (org-link-search ":file local circular link:" (point))
>
> ?
In my previous example the
(org-link-search "[[:file local circular link:]]" (point))
to get enough from the org-link-search argument AVO
Ah, thanks! So it was configuration then...
I initially figured it was language-dependant, which was why I tried it in
Ruby, since "$" is a valid character in that language... What I didn't
anticipate was that the boxes came from intelligent-syntax checking--I
figured that it was just some sort of
you could revert to your working org installation (if you did not delete
that folder) by deleting / moving the folder with the faulty
installation (say "org-201508XX") from your .emacs.d/elpa directory.
If this solves your problems, then I would recommend starting a "bare"
emacs
emacs -q
Hello everbody.
I'm an emacs/org-mode newbie but I'm learning, so please forgive me if
this is obvious for you.
A couple days ago I updated org from the packages-list.
Now, when I'm trying to use a simple org table (typing TAB, for
example), I get:
"org-get-limited-outline-regexp: Variable bi
Rainer M Krug writes:
> Hi
>
> it seems that tangling from an indirect buffer does not work. Is this by
> design or a bug?
I don't think that's by design.
> Would it be possible to make this possible?
Does the below patch work for you? If so, I can test it more thoroughly
and send a proper pa
Nicolas Goaziou writes:
> Andreas Leha writes:
>
>> Seems to work fine!
>>
>> Just note, that it works for me only after exporting
>> (when tested under emacs -Q).
>
> `org-export-current-backend' is set when exporting a document, much like
> `backend'.
>
The same protection as in the previous
This is kind of close:
#+BEGIN_SRC emacs-lisp
(yas-global-mode)
(with-temp-buffer
(insert "# name : my-fortune
# key: myf
# expand-env: ((yas-indent-line nil)
# --
#+BEGIN_QUOTE:
${1:`(shell-command-to-string \"fortune\")`}
#END_QUOTE
$0
")
(yas-load-snippet-buffer-and-close 'org-mode))
#+EN
Andreas Leha writes:
> Seems to work fine!
>
> Just note, that it works for me only after exporting
> (when tested under emacs -Q).
`org-export-current-backend' is set when exporting a document, much like
`backend'.
> What about including that into org?
Wrong namespace. It should be prefixed
Hi. First of all I apologize if this report does not comply in any way to the
standards, since it's my first report.
Steps to reproduce:
1. Create an outline with 2 headlines, each of them having their own drawers.
2. Move the pointer to the headline.
3. Hit M-S-down.
Expected Behavior:
M-S-up/d
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> This macro is from Eric Schulte initially. And I guess I would be out
>> of luck adapting it to new Org mode versions as well.
>
> What about
>
> (defmacro by-backend (&rest body)
> `(case org-export-current-backen
(Still catching up on orgmode mail … sorry if you already found a way to
address the issue)
On 2015-08-18 18:13, Matthew MacLean writes:
> When working with Org Babel source code blocks, if I have a dollar sign in my
> code and export it to PDF using LaTeX, it appears to parse as an internal
> l
Hi
it seems that tangling from an indirect buffer does not work. Is this by
design or a bug?
Would it be possible to make this possible? I am working a lot in
indirect buffers (one subfolder R packages, another analysis of data, a
third one results) and would very much like to tangle from them in
The problem is that tangling in an indirect buffer does not work.
I'll post another email concerning this.
Thanks,
Rainer
Rainer M Krug writes:
> Hi
>
> I get an error #(wrong-type-argument stringp nil)# when I tangle a
> subtree, but tangling the whole document works.
>
> ,
> | GNU Emacs
Christian Wittern writes:
> $> pip --freeze > requirements and
> $> pip install -r
> might provide both a flexible and extensible way to maintain meta packages.
> Or is there already a better way in the Emacs universe?
Why make it so hard? Just use the facilities built into Emacs, namely
in
Hi,
I prefer ESS not to wait for results of evaluating R code, especially if
it takes a longer time (eg estimating a model in RStan, 1-2 minutes), so
I have
(setq ess-eval-visibly 'nowait)
But I find that ob-R ignores this, eg evaluating
#+BEGIN_SRC R :results none
Sys.sleep(10)
#+END_SRC
I
Thanks to everyone, I now have this working. Here is the final version.
--8<---cut here---start->8---
#+LATEX_HEADER: \usepackage{tikz}
First execute the second code block, to define the convenience macro
and to set the required new variables in ob-latex.el. T
On Friday, 4 Sep 2015 at 15:23, Haochen Xie wrote:
> Hi Eric,
>
> It's very likely due to this problem as both Andreas and I mentioned in
> earlier mails:
Thanks. I did notice the bits about htlatex but didn't pay much
attention. I don't actually need svg as I use png for my web pages!
--
: E
40 matches
Mail list logo
