Hello Nicolas,
Nicolas Goaziou wrote:
> As explained in its commit message, the following patch is an attempt at
> simplifying `org-show-context' configuration by offering a set of
> 5 predefined views to choose from instead of setting 4 different
> variables (`org-show-following-heading', `org-sh
Sebastien Vauban
writes:
> Question: are the level-1 headlines always visible, all of them I mean?
> I know that's the case as of now, but wondered if it'd be good to hide
> the ones which are not significant. Not a very sharp advice on this,
> though.
I have no strong opinion about this, but
Rasmus writes:
> + ;; cdlatex-environment always return nil. Therefore, capture output
> + ;; first and determine if an environment was selected.
> + (let* ((beg (point-marker))
> + (end (copy-marker (point) t))
> + (env (org-trim
> +(or (progn (ignore-errors (cdlatex-en
On 2015-02-17T00:17:59+1100, Tory S. Anderson said:
TSA> In my efforts to improve my elisp, can anyone tell me why
the code TSA> doesn't work, and what might have changed to cause
it to break?
TSA> Error: completion-in-region: Wrong type argument: listp,
#("NAME TSA> , NAME , NAME
TSA> , N
Hello,
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, meetings A and B are not counted...
On the other hand, the dyna
Nicolas Goaziou wrote:
> Sebastien Vauban writes:
>
>> Question: are the level-1 headlines always visible, all of them
>> I mean? I know that's the case as of now, but wondered if it'd be
>> good to hide the ones which are not significant. Not a very sharp
>> advice on this, though.
>
> I have no
Sebastien Vauban
writes:
> Nicolas Goaziou wrote:
>> Sebastien Vauban writes:
>>
>>> Question: are the level-1 headlines always visible, all of them
>>> I mean? I know that's the case as of now, but wondered if it'd be
>>> good to hide the ones which are not significant. Not a very sharp
>>> ad
Eric Abrahamsen wrote:
> Sebastien Vauban writes:
>> Nicolas Goaziou wrote:
>>> Sebastien Vauban writes:
>>>
Question: are the level-1 headlines always visible, all of them
I mean? I know that's the case as of now, but wondered if it'd be
good to hide the ones which are not signific
* Thorsten Grothe wrote:
> Dear Org-users,
>
> I got this table:
>
>| Menge (x) | P(x) | E(x) | K(x) | Gewinn |
>|---+--+++-|
>| 0 | 20 | 0.00 | 140.00 | -140.00 |
>|10 | 18 | 180.00 | 180.00 | 0.00|
>|20 | 16 | 320.00 |
Hello Nicolas,
Nicolas Goaziou wrote:
> Sebastien Vauban writes:
>
>> I guess it's directly linked to a problem I reported last
>> September. This is indeed annoying...
>>
>> See issue #29 on http://orgmode.org/worg/org-issues.html (and see the
>> pointed thread).
>
> This isssue seems fixed. Can
Actually, the first patch didn't pay attention to children, if any, of
the current headline. Here is a new patch, including feedback from Kyle
and Sébastien.
Considering the following buffer, "Text" being the matched location
* Grandmother
** Uncle
*** Heir
** Father
*** Siste
Sebastien Vauban
writes:
> PS- If there was just one other issue I'd like to see resolved from that
> list, it's #27, but (IIRC) it will be part of a change you'll make to
> fontify the Org buffer from the parser info, right?
I'm not sure it would solve anything. You may want to change the ord
Navigating through the labyrinth of org commands and wrappers, I've not been
able to find out if there's already a way to open a link (particularly a
footnote link) in a new window, so that I could retain my in-line location and
context while reading the linked/footnoted text. I realize this fun
torys.ander...@gmail.com (Tory S. Anderson) writes:
> Presumably this is related to my having upgraded to:
> Org-mode version 8.2.10 (8.2.10-33-g880a2b-elpa)
> GNU Emacs 25.0.50.6 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.9) of
> 2015-02-10 on localhost.localdomain
>
> I use org-contacts[1] to
Thanks Nick for the tip; I've recently learned about debug-on-entry, which I
attempted to use to no avail last night, but the functions listed in the info
manual you cited are useful. Following them I have found that the problem seems
to be a conflict bewteen Org-Contacts and Helm; loading witho
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
> I want a syntax that recognizes arbitrary citation commands because I
> write in Org mode for publication. You want a syntax that recognizes a
> few commands that it might be possible to support in Org mode backends,
> some of which are tied loose
Hi,
Rasmus writes:
>>> and *why* is orgmode.org hosting it? Privacy?
>>
>> I don't think CDN service was available at the time mathjax support was
>> implemented. IMO, it hardly makes sense to host it now.
>
> This patch switches the cdn to upstream and removes a lot of stuff that I
> believe ma
Richard Lawrence writes:
> Basically, I think you could ignore the distinctions that the [cite:
> ...] syntax is capable of expressing, and just write all your citations
> like:
>
> [cite: See @Doe99 for more on this point.] %%(:type footnoted)
>
> or, in the syntax Nicolas proposed, something
Hello,
i am using the following in my .emacs:
(setq org-refile-use-outline-path 'file)
(setq org-refile-targets '((org-agenda-files :level . 4)))
i would now like to drop a certain headline when pressing C-c C-w anywhere:
maybe directly in:
work.org as first headline
work.org/routine/custom
On Monday, 16 Feb 2015 at 21:20, Nicolas Goaziou wrote:
> Hello,
>
> Eric S Fraga writes:
>
>> At this point, I get very long data structures dumped to
>> *Messages*... difficult to figure out what is wrong. It's often my
>> mistake but tracking it down is difficult.
>
> You're using an internal
i use maint, but looks good. i'd use canonical most of the time.
it would be good to also have semi-canonical [i.e.
canonical-without-ancestor-body-text], where ancestor nodes do not
show body text. text can obscure structure. i use this view for
blogs. otherwise i'd have to make fake headline
Michael Ziems wrote:
[...]
> (setq org-refile-use-outline-path 'file)
> (setq org-refile-targets '((org-agenda-files :level . 4)))
[...]
> but ord mode is only allowing me to go exactly to one level deep (i
> assume level 4)
> but when i leave:
[...]
> Do you have any idea, what could be the rea
Good afternoon,
Just read [this] question. It is interesting. We always want to optimize
our documents. Re-use reduces errors. Defining `:header-args:foo:
:session *bar*' is a great example. Rather than having to type it 100
times all over, just do it once. It never occurred to be that we might
wa
Grant Rettke writes:
> Just read [this] question. It is interesting. We always want to optimize
> our documents. Re-use reduces errors. Defining `:header-args:foo:
> :session *bar*' is a great example. Rather than having to type it 100
> times all over, just do it once. It never occurred to be th
Awesome :)
Thank you so much, that was the solution!
(setq org-refile-use-outline-path 'file)
(setq org-refile-targets '((org-agenda-files :maxlevel . 24)))
the command ist taking quite a while during "Getting targets" can i
speed this actualy up?
Am 17.02.2015 um 20:34 schrieb Kyle Meyer:
Michael Ziems wrote:
> Awesome :)
>
> Thank you so much, that was the solution!
>
> (setq org-refile-use-outline-path 'file)
> (setq org-refile-targets '((org-agenda-files :maxlevel . 24)))
>
> the command ist taking quite a while during "Getting targets" can i
> speed this actualy up?
You coul
Hi, Grant.
Grant Rettke writes:
It would be simpler to say "this whole document will be R source
blocks, unless I specify other wise". I looked at [the spec]. I
wanted to obtain this behavior. I couldn't figure out how. Is it
possible?
The problem is that if there is nothing after #+BEGIN_S
Rasmus writes:
>> Hi! I noticed that the refactored org-get-property-block no longer
>> allows for any text (aside from the SCHEDULED / DEADLINE / CLOSED) text
>> between the heading and the property drawer, which gave me problems when
> Did you see this discussion? I think it's a feature.
>
Samuel Wales writes:
> it would be good to also have semi-canonical [i.e.
> canonical-without-ancestor-body-text], where ancestor nodes do not
> show body text. text can obscure structure. i use this view for
> blogs. otherwise i'd have to make fake headlines just to hide text.
I don't unders
Sacha Chua writes:
> Ah, that makes perfect sense. I'll try to train myself out of adding
> stuff everywhere, then. Thank you!
If you the keybind it will do the right thing.
In ORG-NEWS there's a script to fix old files. Worst case use it as a
save-hook...
–Rasmus
--
And I faced endless str
Eric S Fraga writes:
> I have many internal references; in this document, all are to named
> tables and figures.
The error comes from a figure, not a table, if that helps.
> I have tried but haven't managed to track down which one is causing
> problems in this case.
>
> I have tried extracting
Hello,
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, meetings A and B are not co
Nicolas Goaziou writes:
> I don't think you need `org-element-at-point' at all. You already have
> BEG and END markers available. I didn't test it, but this should be
> enough to indent the environment.
Perhaps there are clever ways to figure it out. I say there are too many
dynamics and "fixes
hi nicolas,
On 2/17/15, Nicolas Goaziou wrote:
> I don't understand. Body text is not shown in ancestors. Considering the
> following buffer:
>
> * Grandmother
> ** Uncle
> *** Heir
> ** Father
>Ancestor text
> *** Sister
> Sibling text
> *** Self
>
Samuel Wales writes:
> that is not canonical. i thought we were working from my previous
> posts over the years where i used the term "canonical".
>
> you cannot create the visibility state you show from a fully-folded
> buffer using only arrow keys and tab.
You are right. Time for a third roun
On 2015-02-18T06:25:57+1100, Glenn Morris said:
GM> 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
Rasmus 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 reinserted, but before inden
On Feb 17, 2015 1:12 PM, "Rasmus" wrote:
>
> Richard Lawrence writes:
>
> > Basically, I think you could ignore the distinctions that the [cite:
> > ...] syntax is capable of expressing, and just write all your citations
> > like:
> >
> > [cite: See @Doe99 for more on this point.] %%(:type foot
looks good.
thanks for your effort on making a single variable.
Nicolas Goaziou writes:
> Rasmus 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
Hello,
Alexis writes:
> On 2015-02-18T06:25:57+1100, Glenn Morris said:
>
> GM> 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
Hi Richard,
Thanks for your thoughtful responses and your work on the citation
syntax. My "author" concerns have been addressed in this thread and I
look forward to development now. I'm +1 and optimistic about the switch
from home-brew links to citations in my Org mode work.
Thanks for your pat
Rasmus: Thanks
Jorge: Yes probably
On Tue, Feb 17, 2015 at 2:09 PM, Jorge A. Alfaro-Murillo
wrote:
> Hi, Grant.
>
> Grant Rettke writes:
>
>> It would be simpler to say "this whole document will be R source blocks,
>> unless I specify other wise". I looked at [the spec]. I wanted to obtain
>> th
Hi Rasmus,
Rasmus writes:
> Richard Lawrence writes:
>
>> Basically, I think you could ignore the distinctions that the [cite:
>> ...] syntax is capable of expressing, and just write all your citations
>> like:
>>
>> [cite: See @Doe99 for more on this point.] %%(:type footnoted)
>>
>> You wou
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
> Thanks for your thoughtful responses and your work on the citation
> syntax. My "author" concerns have been addressed in this thread and I
> look forward to development now. I'm +1 and optimistic about the switch
> from home-brew links to citatio
Hi,
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.
Problem with all cloud storages is they don't work with relative links
inside HTML (links to external images, CSS, and JS resources).
Hello,
When working with links in Org documents, I noticed that I often kill
surrounding text to bring it into the description, or vice versa. At
some point, this made me think that it'd be nice to be able to add and
remove description words like Paredit lets you do with S-expressions.
I've put t
Hi,
The `#+TOC: tables` construct does export nicely to HTML. Just wondering
if `#+TOC: figures` and maybe `#+TOC: equations` is on the roadmap, or
could anyone provide a hook to make this work in the meantime?
Thanks, --Mel.
--
Melanie BACOU
International Food Policy Research Institute
Snr.
48 matches
Mail list logo
