Daniele Nicolodi writes:
> Hello,
>
> I don't think this is what is holding up review of these patches, but, I
> recently completed the paperwork for copyright assignment to the FSF.
Thanks for this series (and thanks to Eric for the feedback in the
previous thread). I'm sorry for the slow
Vladimir Nikishkin writes:
> So what is the status of this story?
>
> I believe that if one exports an org file with sufficiently many empty
> TODO headings (to me, it seems a perfectly valid use case of org,
> printing lists of TODOs), they won't fit on a single page, and latex
> will drop
Lennart Borgman writes:
> On Sun, Nov 28, 2010 at 8:01 PM, Stefan Monnier
> wrote:
>>> Could we please add a replacement for 'htmlize-region-for-past using
>>> htmlfontify?
>>
>> I don't know what is "htmlize-region-for-past(e?)". Care to give us
>> some context?
>
> I have never used it, but
Hi all,
I've just caught up with this conversation after feeling similar
friction to others since the 'electric-indent' change.
When it happened, I spent time trying to figure out how to revert the
change (thinking I had introduced the bug myself in my configuration
somehow) and ended up setting
Greg Minshall writes:
> hi. this adds the minimal mention of transpose. cheers.
Thanks. Could you add a commit message to the patch (using
git-format-patch)?
> diff --git a/doc/org-manual.org b/doc/org-manual.org
> index 040fccc21..33d32b8f5 100644
> --- a/doc/org-manual.org
> +++
Greg Minshall writes:
> hi, Robert,
>
> thanks. given that the docstring already talks about nil, t,
> 'headline-data ...
Not related to your main point, but if you're improving the docstring
anyway: 'headline-data (which is a relatively recent addition) should
instead be written as
Kyle Meyer writes:
> All these look good to me except this unrelated whitespace change, which
> actually touches the change ported from your 61dca6e92a (Don't quote
> lambdas in several places, 2020-11-14) in the Emacs repo.
I must have included that part by mistake, sorry about that.
> Org
So what is the status of this story?
I believe that if one exports an org file with sufficiently many empty
TODO headings (to me, it seems a perfectly valid use case of org,
printing lists of TODOs), they won't fit on a single page, and latex
will drop them. Would the latex snippet in this thread
Stefan Kangas writes:
> I've been working on removing redundant `function' around `lambda' in
> Emacs core, so here is a patch which does the same for Org-mode.
Thanks.
> Subject: [PATCH] Remove redundant 'function's around lambda
[...]
> diff --git a/lisp/ox-odt.el b/lisp/ox-odt.el
> index
joa...@verona.se writes:
> Kyle Meyer writes:
>
>> The change in behavior you describe came with 4f98694bf (Allow numeric
>> values for priorities, 2020-01-30). Based on quickly skimming that
>> commit, I think the issue boils down to intentionally not supporting a
>> mix of numbers and
Kyle Meyer writes:
> joa...@verona.se writes:
>
>> This used to work:
>> (defun jv-org-priorities ()
>> (setq org-highest-priority ?0 ;; 64 @ 48 0, bugs start happening if you
>> have higher prios tnan 0, like '!'
>> org-lowest-priority ?E ;; E
>> org-default-priority
On 11/18/20 2:42 PM, TEC wrote:
I have 2c on the use of "interpolated".
1. I tend to think of "interpolated" in terms of it's mathematical
meaning
2. The other denotations relate to insertion and renewing, which simply
doesn't fit.
I appreciate that other people may have used this too,
I have 2c on the use of "interpolated".
1. I tend to think of "interpolated" in terms of it's mathematical
meaning
2. The other denotations relate to insertion and renewing, which
simply
doesn't fit.
I appreciate that other people may have used this too, but as I
see it
that just means
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Hi,
in OrgMode 9.5 it seems that the variables during the tangling of sh
aren't set/initialized.
For example the block below:
#+begin_src sh :var str="Hello World" :tangle helloworld.sh
echo $str
#+end_src
Gets tangled into:
echo $str
Which means the str="Hello World" line is missing.
I
hi, Robert,
thanks. given that the docstring already talks about nil, t,
'headline-data ...
should i eliminate those, just leaving "three" choices?
> "Adapt indentation for all lines"
> "Adapt indentation for headline data lines"
> "Do not adapt indentation at all"
or, leave mention
Greg Minshall writes:
> Robert,
>
>> The whole point of customize is that you shouldn't have to worry about
>> what the actual lisp value is. The actual lisp value only matters if
>> you directly set the value without using customize.
>
> thanks for the response. i've included the documentation
Indeed. I will try to work on it in my spare time, it will take maybe up to
a year, but as soon as I have it, I will let the maillist know in case it's
of interest.
Again, thanks for all your help.
GM
El mié., 18 nov. 2020 a las 7:37, Ihor Radchenko ()
escribió:
> > So from now on, all the DONE
18 matches
Mail list logo