Hello,
Colin Baxter writes:
> I think there may be an issue with commit
> b886ebbc8924916c1e36df00639b3208a1c155a2. Using tables, I now get an error:
>
> org--string-from-props: Un-handled `display' value: (space :width 1)
>
> which goes away when I revert the commit.
Oops. Fixed. Thank you.
Le 26/10/2018 à 17h35, Nicolas Goaziou a écrit :
> "Garreau, Alexandre" writes:
>> Why so?
>
> See `org-email-link-description-format'.
Thank you!
>> It shouldn’t be this way by default.
>
> Truncating subject doesn't seem unreasonable to me. In any case, you can
> just set the variable above
Say I have a calendar file which is in the following format:
* description of deadline:client1:
DEADLINE: <2018-10-28 Tue>
* a meeting :client1:
<2018-11-1 Thu 10:00>
I would like to be able to view all headlines and time entries associated
with a particular tag, and to have that
Hello,
stardiviner writes:
> I did a search of "font-lock-add-keywords", "begin_src", "src_" etc in
> Org Mode source code, but have not found exact place where fontify
> function are. So I don't know where to modify the source code. Now I put
> my current config here:
[...]
>
Hello,
stardiviner writes:
> Thanks for this hint, I added a new entry in org-src--babel-info list to
> pass the original parent file path.
Thank you. Some comments follow.
> - (language body arguments switches name start coderef)"
> + (language body arguments switches name start coderef
Hello,
"Garreau, Alexandre" writes:
> Why so?
See `org-email-link-description-format'.
> It shouldn’t be this way by default.
Truncating subject doesn't seem unreasonable to me. In any case, you can
just set the variable above to suit your needs.
Regards,
--
Nicolas Goaziou
Hello,
First of all, thank you for org-mode. Without it, I literally would find
it much more difficult to do my job.
I am having a problem with group tags. I reproduced it using the latest
org-mode from the org package archive, 20181022. The minimal example is
this: say I have a group tag
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> I did a search of "font-lock-add-keywords", "begin_src", "src_" etc in
>> Org Mode source code, but have not found exact place where fontify
>> function are. So I don't know where to modify the source code. Now I put
>> my current
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> Thanks for this hint, I added a new entry in org-src--babel-info list to
>> pass the original parent file path.
>
> Thank you. Some comments follow.
>
>> - (language body arguments switches name start coderef)"
>> + (language body
"Garreau, Alexandre" writes:
> How’s that?
I think limiting the number of characters in the description is to be on
the safe side. 30 characters are usually enough to understand what the
mail is about.
> it just feels wrong: if it’s to long, users can truncate themselves,
> it’s
Nicolas Goaziou writes:
> I think limiting the number of characters in the description is to be on
> the safe side. 30 characters are usually enough to understand what the
> mail is about.
Can you please elaborate on what you mean by being on the safe
side in this context? What problems could
Garreau, Alexandre writes:
> Sorry, just found out that interesting (to me) thread I shouldn’t have
> let go:
>
> On 2018-10-25 at 08:00, Tim Cross wrote:
>> Kaushal Modi writes:
>>> […]
>>> - b and i are not deprecated
>>> - b and strong are both valid but their use depends on the writer's
Samuel Wales writes:
> can either of you give examples of code or settings that you had that
> made behavior of new modes unpredictable because emacs started
> supporting the behavior you made the code or settings for?
>
It is difficult to remember now as it was some time ago that I cleaned
I tried to eval the following block, and my point was on the last line,
of course, but since it begins with a “|”, it was interpreted as a
table, and block was not evaled: I believe this is a bug. Why would a
org table be inside a non-org source block? it’s not even inside a
comment!
#+BEGIN_SRC
I think there may be an issue with commit
b886ebbc8924916c1e36df00639b3208a1c155a2. Using tables, I now get an error:
org--string-from-props: Un-handled `display' value: (space :width 1)
which goes away when I revert the commit.
Best wishes,
On Thursday, 25 Oct 2018 at 15:57, Samuel Wales wrote:
> can either of you give examples of code or settings that you had that
> made behavior of new modes unpredictable because emacs started
> supporting the behavior you made the code or settings for?
In my case, mostly incompatible bindings of
On Friday, 26 Oct 2018 at 08:45, Garreau, Alexandre wrote:
> I tried to eval the following block, and my point was on the last line,
> of course, but since it begins with a “|”, it was interpreted as a
> table, and block was not evaled: I believe this is a bug. Why would a
> org table be inside a
Hello,
"Garreau, Alexandre" writes:
> I tried to eval the following block, and my point was on the last line,
> of course, but since it begins with a “|”, it was interpreted as a
> table, and block was not evaled: I believe this is a bug. Why would a
> org table be inside a non-org source
On 2018/10/26 at 11:34, Nicolas Goaziou wrote:
> "Garreau, Alexandre" writes:
>
>> I tried to eval the following block, and my point was on the last line,
>> of course, but since it begins with a “|”, it was interpreted as a
>> table, and block was not evaled: I believe this is a bug. Why would
On 2018/10/26 at 10:29, Eric S Fraga wrote:
> On Friday, 26 Oct 2018 at 08:45, Garreau, Alexandre wrote:
>> I tried to eval the following block, and my point was on the last line,
>> of course, but since it begins with a “|”, it was interpreted as a
>> table, and block was not evaled: I believe
20 matches
Mail list logo
