Christopher M. Miles writes:
> I hope `:mkdirp` header argument can also work for other related header
> arguments like `:dir`, `:file` etc not just `:tangle`. Like following
> example.
>
> #+begin_src sh :mkdirp yes :dir "data/code/mkdirp/dir" :file "test" :results
> file link
> echo "hello"
How does Org position the Tags on the Header line when it reads in an
Org file with Tags? It seems that the Tags move from time to time and
that can actually cause the file to be viewed as "changed" by the change
control system (CVS). I would've thought that the Tags are positioned
when inserted
Well, I think it’s unreasonable to ask users to reinforce manually and
continuously something they’ve already specified in their settings.
Besides, my example was intentionally trivial—imagine managing a large
tree and having to remember which tags are mutually exclusive to what,
all the time.
Hello,
Richard Stanton writes:
> Using Org mode version 9.2.1 (9.2.1-33-g029cf6-elpaplus), I get an error
> message when I run org-agenda:
>
> Debugger entered--Lisp error: (error "Wrong number of arguments")
> propertize("WAITING" nil face org-warning)
>
Using Org mode version 9.2.1 (9.2.1-33-g029cf6-elpaplus), I get an error
message when I run org-agenda:
Debugger entered--Lisp error: (error "Wrong number of arguments")
propertize("WAITING" nil face org-warning)
org-agenda-get-restriction-and-command(nil)
org-agenda(nil)
Hello,
Edmund Christian Herenz writes:
> Consider the following HTTP link:
> http://skyserver.sdss.org/dr14/en/tools/quicklook/summary.aspx?ra=11%2054%2048.85=+24%2043%2033.0
>
> I have this link in the kill-ring, mark 'some text' in an org-mode buffer
> and run org-insert-link (C-c C-l). Then
> From: Robert Pluim
> Cc: philip.w...@warwick.ac.uk, 34...@debbugs.gnu.org
> Date: Fri, 01 Mar 2019 15:25:04 +0100
>
> We are miscommunicating. I was demonstrating that in my setup,
> org-time-stamp produces the correct output => itʼs a configuration
> issue.
I'm not yet sure it's a
Eli Zaretskii writes:
>> From: Robert Pluim
>> Cc: philip.w...@warwick.ac.uk, 34...@debbugs.gnu.org
>> Date: Fri, 01 Mar 2019 14:47:21 +0100
>>
>> > That's only so if the above produces the same garbled result as in the
>> > original report. Does it?
>>
>> Didnʼt I send this yesterday?
>>
> From: Robert Pluim
> Cc: philip.w...@warwick.ac.uk, 34...@debbugs.gnu.org
> Date: Fri, 01 Mar 2019 14:47:21 +0100
>
> > That's only so if the above produces the same garbled result as in the
> > original report. Does it?
>
> Didnʼt I send this yesterday?
>
> $ LANG=zh_HK src/emacs -Q -l
Eli Zaretskii writes:
>> From: Robert Pluim
>> Cc: Eli Zaretskii , 34...@debbugs.gnu.org
>> Date: Fri, 01 Mar 2019 11:00:01 +0100
>>
>> > It could be some snafu in Org, though, e.,g. if it doesn't know how to
>> > support that value of $LANG. In any case, should be reported to Org
>> >
Robert Pluim writes:
> Eli Zaretskii writes:
>
>>> From: Robert Pluim
>>> Cc: Eli Zaretskii , 34...@debbugs.gnu.org
>>> Date: Fri, 01 Mar 2019 11:00:01 +0100
>>>
>>> > It could be some snafu in Org, though, e.,g. if it doesn't know how to
>>> > support that value of $LANG. In any case,
> From: Robert Pluim
> Cc: Eli Zaretskii , 34...@debbugs.gnu.org
> Date: Fri, 01 Mar 2019 11:00:01 +0100
>
> > It could be some snafu in Org, though, e.,g. if it doesn't know how to
> > support that value of $LANG. In any case, should be reported to Org
> > developers first.
>
>
Eli Zaretskii writes:
>> Iʼm assuming thereʼs an issue with buffer-file-coding-system or
>> similar.
>
> Unlikely: buffer-file-coding-system has no effect whatsoever on the
> text that is inserted into a buffer, it only has effect when you want
> to save the buffer or send it to some
On 2019-03-01, Nicolas Goaziou wrote:
> Jens Lechtenboerger writes:
>
>> On 2019-03-01, Nicolas Goaziou wrote:
>>
>>> 3. There will be some backward compatibility issues. We can add
>>>a checker in Org Lint to catch most of those. For example, we could
>>>look at URI where every percent
Hello,
Jens Lechtenboerger writes:
> On 2019-03-01, Nicolas Goaziou wrote:
>
>> 3. There will be some backward compatibility issues. We can add
>>a checker in Org Lint to catch most of those. For example, we could
>>look at URI where every percent is followed only by 25, 5B, and 5D.
>
>
Hi there,
I like this proposal.
On 2019-03-01, Nicolas Goaziou wrote:
> 3. There will be some backward compatibility issues. We can add
>a checker in Org Lint to catch most of those. For example, we could
>look at URI where every percent is followed only by 25, 5B, and 5D.
I do not
On Fri, Mar 1, 2019 at 9:15 AM Nicolas Goaziou wrote:
> Thinking a bit more about it, we don't need to escape /all/ square
> brackets, only "]]" and "][" constructs. Therefore, we don't need to
> escape every backslash either.
Brilliant!
Nicolas Goaziou writes:
> The regexp for bracket links could be, in its simple (!) form:
>
> \[\[\(.*?[^\\]\(?:\\\)*\)\]\(?:\[\([^\000]+?\)\]\)?\]
Small update, in its string form now:
"\\[\\[\\([^\000]*?[^\\]\\(\\)*\\)\\]\\(?:\\[\\([^\000]+?\\)\\]\\)?\\]"
Hi Robert,
* Robert Love [2019-02-28; 23:52]:
> I’m using Org mode to document some software. When I see
> Texinfo used for this, I see that you can have a subject index
> and a variable index. How do I achieve the same thing in Org
> mode? Can someone point to examples of this?
I don't know
Hello,
Neil Jerram writes:
> Do you mean Windows file names in existing Org files? I.e. the
> back-compatibility concern?
>
> If so, yes, I confess I didn't think at all about back-compatibility,
> with my suggestion above. So perhaps that rules my idea out.
>
> If we were starting from
20 matches
Mail list logo
