Thanks,
For your small example (exporting to latex) I get
\begin{itemize}
\item H1 :private:
\item H2
\end{itemize}
(apart from the preamble etc). What is also weird: If I add the
``standard'' vanilla template (via C-c C-e # beamer), then
- 1) some option settings like H:2 vs H:3 /are/
I just encountered following behaviour:
*foo bar*[fn:1] will export as *foo bar*1 (not bold, with stars)
*foo bar* [fn:2] will export as foo bar 1 (bold, but you've to use a space
between bold text and marker)
I may be wrong, but I thought a footnote marker will follow immediately
after the word
Hi
I actually find it annoying in ESS to keep pressing C-c ' each time i want
to eval a single line of code in a code block. if this could work for R
code this would be fantastic for me
thx
Z
On Tue, Nov 10, 2015 at 8:19 PM, Carlos Henrique Machado S Esteves <
ch.machado.este...@gmail.com> wrot
Hi Kosyrev,
2015ko azaroak 10an, Kosyrev Serge-ek idatzi zuen:
> Perhaps I was unclear in this message -- it's not the Org's priority
> mechanism that is broken, it's the way ox-taskjuggler uses it that is.
>
> Org specifies priorities via a list of enums, whereas TJ expects an
> integer in the r
Hi Kosyrev,
2015ko azaroak 10an, Kosyrev Serge-ek idatzi zuen:
>
> Generally speaking, TaskJuggler own "attributes" and "properties" are
> very numerous. Suffice to point to the documentation:
>
> http://taskjuggler.org/tj3/manual/
>
> Org is only able to provide a very limited amount of tho
Hello,
Carlos Henrique Machado S Esteves writes:
> You are right, I've updated the patch.
Thank you. Some comments follow.
> * ob-core.el (org-babel-execute-src-block-region): Execute only active region
> of
> the current source block. Same as `org-babel-execute-src-block', but
> use only th
Hello,
Karl Voit writes:
> | | 20 | 21 | 22 | 23 | 24 |
> | | :=vsum(@3..@>) |||||
> |-+++++|
> | ||||||
> |-+++++|
> | | 1 | 1 ||
Hello,
Karl Voit writes:
> Independent to your resolved issue: on my Org-mode files with 30,000
> to 40,000 lines of Org-mode my computer took up to 12 hours to
> finish org-lint.
>
> Interesting fact: after finishing and saving the results, GNU/Emacs
> runs into an endless-loop when I try to ex
Hello,
Martin Steffen writes:
> Now: when I want to /customize/ that in the org-file itself, it seems that's
> done by doing something like
>
>
> #+EXCLUDE_TAGS: private
[...]
> Anyhow: having such a specification in the org-file seems to have /no
> effect/, even if I "refresh" the org-file, n
Hello,
Michael Welle writes:
> I added '#+FILETAGS: noexport' (I tried :noexport: as well) to the top
> of an org file. The intention is that nothing from this file should get
> exported. But that doesn't work. An agenda query for the noexport tag
> finds all headlines of this file, so the taggi
> Achim Gratz writes:
> So isn't your request rather to hide the properties drawer better by
> default? You were _only_ talking about the UX in this whole thread and that
> might be a lot easier to adapt while not changing the way Org syntax is
> defined.
Good call, Achim! I became too focus
John Wiegley writes:
>> Nicolas Goaziou writes:
>
>> I really don't like the idea of making Org /syntax/ customizable, would it
>> be with the help of a hook or a variable.
>
> From what I've seen so far, several users want regularity of syntax to
> decide formatting, and several users want
Matt Lundin writes:
> John Wiegley writes:
>
>>> Nicolas Goaziou writes:
>>
>>> I really don't like the idea of making Org /syntax/ customizable, would it
>>> be with the help of a hook or a variable.
>>
>> From what I've seen so far, several users want regularity of syntax to
>> decide for
John Wiegley writes:
> In my regimen, every single entry has a PROPERTIES drawer, since I tag each
> one with ID and CREATED, for future reference. Most items are SCHEDULED as
> well. So when I open up a headline to look at the contents, I see:
>
> * Head
> SCHEDULED
> text
> :PROPE
> Achim Gratz writes:
> If you don't use properties then it doesn't affect you at all. If you do,
> then… well, I personally simply don't care. Just like there's several style
> guides for writing C; as long as these are applied consistently I can live
> with most of them and put the braces a
> Nicolas Goaziou writes:
> I really don't like the idea of making Org /syntax/ customizable, would it
> be with the help of a hook or a variable.
>From what I've seen so far, several users want regularity of syntax to decide
formatting, and several users want user preference to decide forma
John Wiegley writes:
> If the answer from the maintainers is "It's more work than we want to do",
> that's completely acceptable. I've been operating under the premise that it
> wouldn't be difficult to add such an option (just the hook, mind you, not the
> functionality behind it).
To answer your
Nicolas Goaziou writes:
> Hello,
>
> Thomas S. Dye writes:
>
>> Is the hook he is requesting a difficult thing to implement? Would it
>> be possible to describe the customization variable in a "Super User"
>> section that is clearly not for the faint at heart?
>>
>> I'm not suggesting anyone s
Hello Chuck,
Thank you for the feedback.
> You might want to check that point and mark are both inside the src
block. Otherwise, the results are unpredictable.
You are right, I've updated the patch.
> ess-mode, python-mode, sh-mode and octave-mode already provide this
capability (and a lot more)
John Wiegley writes:
> There is another vector to consider, and a far more nebulous one: How does it
> impact Org's "luft"? That is, the feeling of ease and comfort Org conveys in
> its use.
FWIW, I personally have found org both faster and much more reliable
thanks to Nicolas' heroic work to ti
AW writes:
> Background: I'm using orgmode on different platforms, Windows and Linux. So I
> (being very proud of that!) wrote an if-clause:
>
> (setq org-link-abbrev-alist
>(if (eq system-type 'windows-nt)
> '(("foopath" . "//Sbs2011/ra2000/Bilder/2010/271-2011/%s")
> )
> '(("fo
Hello,
Thomas S. Dye writes:
> Is the hook he is requesting a difficult thing to implement? Would it
> be possible to describe the customization variable in a "Super User"
> section that is clearly not for the faint at heart?
>
> I'm not suggesting anyone should implement a hook or create a
> c
John Wiegley writes:
>> Aaron Ecay writes:
>
>> Adding knobs to this parser increases the burden of those who have to build
>> and maintain it.
>
> Thank you for your reply, Aaron, I found it most illuminating.
>
> If the answer from the maintainers is "It's more work than we want to
> do",
Hi Sebastian,
Thanks for the patch. In addition to Kyle’s comments:
2015ko urriak 9an, Sebastian Christ-ek idatzi zuen:
>
> Hi group,
>
> I'd like to provide a patch to
> ox-extra.el. `org-latex-header-blocks-filter' still calls
> `org-edit-src-find-region-and-lang' and raises therefore an und
On Tue, Nov 10, 2015 at 11:16 AM, Nick Dokos wrote:
>
> > Pass the level as a parameter?
> >
> > Can I pass the level of the current heading as a parameter, e.g.:
> >
> > where obviously CURRENT-ORG-LEVEL is some function I don't know how to
> access?
> >
>
> You can at the very least set the
Matt Price writes:
> > also, (c): I'd rather set the level of the org heading based on
> context. Can I do that when I call
> from
> > a source block? Should I maybe be doing this some other way (e.g., jsut
> write an interactive
> function
> > and call it with M-x? But I li
* Gregor Zattler wrote:
>
> I run org-lint on one of my org-mode buffers -- 13015 lines with
> ~2000 CLOCK: lines -- and it did not finish within 1 1/2 hours.
Independent to your resolved issue: on my Org-mode files with 30,000
to 40,000 lines of Org-mode my computer took up to 12 hours to
finish
Sebastian Christ writes:
[...]
> >> + (let* ((beg (third pos))
> >> + (end (second pos))
> >> + (post-affiliated (first pos))
> Kyle>
> Kyle> Hmm, the pos items are constructed as
> Kyle>
> Kyle> (list (org-element-property :
On Mon, Nov 9, 2015 at 4:57 PM, Nick Dokos wrote:
> Matt Price writes:
>
> > I would like to be able to insert into an org-buffer the text extracted
> from a pdf file. PDF-Tools (
> > https://github.com/politza/pdf-tools/) provides some excellent tools
> for doing this. I've written
> > (well,
On 10/11/15 02:40, Aaron Ecay wrote:
I think it’s more illuminating to think of it in terms of org as a tool:
have the changes made it more difficult for you to accomplish your goals
with org? Has something that was previously possible become impossible?
Has something that was previously easy g
Hi Jonas,
Jonas Bernoulli writes:
> Well currently I am just using `org-cycle' + `outline-minor-mode', which
> works well enough for now. But eventually I would like to also start
> using Org's navigational commands. Unfortunately `orgstruct-mode' only
> supports org-like headings (;; * headin
> On Mon, 09 Nov 2015 01:30:23 -0500, Kyle Meyer said:
>> * ox-extra.el (org-latex-header-blocks-filter): Use `org-element' API to
>> find begin and end of latex header blocks.
Kyle>
Kyle> s|ox-extra.el|contrib/lisp/ox-extra.el|
Kyle> s/begin/beginning/
Kyle>
Thanks. I'll change
Aaron Ecay writes:
> 2015ko azaroak 8an, Kosyrev Serge-ek idatzi zuen:
>>
>> * ox-taskjuggler.el (org-taskjuggler--build-task): fix priority
>> specification
>> by allowing it to be directly passed down, in case it parses as an integer.
>> ---
>> contrib/lisp/ox-taskjuggler.el | 12 +--
Aaron Ecay writes:
> Hi Kosyrev,
>> @@ -301,7 +301,7 @@ but before any resource and task declarations."
>>:type '(string :tag "Preamble"))
>>
>> (defcustom org-taskjuggler-valid-task-attributes
>
> Is this an open-ended list that an average user could meaningfully add
> to? If not, perhaps
34 matches
Mail list logo
