Ihor Radchenko writes:
> I will leave this for another week to give other people a chance to
> comment.
Applied upstream onto main via e268e4797.
Best,
Ihor
Ihor Radchenko writes:
>> From f474cb25840fdc6b24618b1452cb7fdd32545092 Mon Sep 17 00:00:00 2001
>> From: Tyler Grinn
>> Date: Mon, 9 May 2022 15:52:58 -0400
>> Subject: [PATCH] lisp/org.el: Add org-property-separators option
>
> LGTM!
>
> I will leave this for another week to give other people
Tyler Grinn writes:
> Ihor Radchenko writes:
>
>> Note that your patch is >15LOC long and you need to sign the copyright
>> agreement with FSF in order to contribute. See
>> https://orgmode.org/worg/org-contribute.html#copyright
>
> I've already submitted a copyright assignment to the FSF in ord
Ihor Radchenko writes:
> Note that your patch is >15LOC long and you need to sign the copyright
> agreement with FSF in order to contribute. See
> https://orgmode.org/worg/org-contribute.html#copyright
I've already submitted a copyright assignment to the FSF in order to
publish on ELPA. Do I nee
Tyler Grinn writes:
> OK, what I have now is that if the car of an alist item is a list, exact
> matching will be done for each list item, but if it is a string, it will
> be matched as a regular expression.
Sounds reasonable.
Note that your patch is >15LOC long and you need to sign the copyrig
Ihor Radchenko writes:
> Tyler Grinn writes:
>
>> Ihor Radchenko writes:
>>
>>> Tyler Grinn writes:
>>>
Could you provide an example of what the value of that variable would be
if, for instance, I wanted PROP_A and PROP_B to be joined with a single
space and PROP_C and PROP
Tyler Grinn writes:
> Ihor Radchenko writes:
>
>> Tyler Grinn writes:
>>
>>>
>>> Could you provide an example of what the value of that variable would be
>>> if, for instance, I wanted PROP_A and PROP_B to be joined with a single
>>> space and PROP_C and PROP_D to be concatenated? Or better yet
Ihor Radchenko writes:
> Tyler Grinn writes:
>
>>
>> Could you provide an example of what the value of that variable would be
>> if, for instance, I wanted PROP_A and PROP_B to be joined with a single
>> space and PROP_C and PROP_D to be concatenated? Or better yet, have the
>> default be to joi
Tyler Grinn writes:
>
> Could you provide an example of what the value of that variable would be
> if, for instance, I wanted PROP_A and PROP_B to be joined with a single
> space and PROP_C and PROP_D to be concatenated? Or better yet, have the
> default be to join with a single space for any pro
Ihor Radchenko writes:
> Tyler Grinn writes:
>
>> John Kitchin writes:
>>
>>> I like the variable idea. I would make it a concatenation string for
>>> joining. That way “” would concatenate the way Tyler wants, “ “ would
>>> preserve current behavior, and “,” could lead to a comma separated
>>>
Tyler Grinn writes:
> John Kitchin writes:
>
>> I like the variable idea. I would make it a concatenation string for
>> joining. That way “” would concatenate the way Tyler wants, “ “ would
>> preserve current behavior, and “,” could lead to a comma separated
>> list for example. Other things li
John Kitchin writes:
> Where did you add that?
>
> John
>
> ---
> Professor John Kitchin (he/him/his)
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.c
Where did you add that?
John
---
Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Fri, May 6, 2022 at 11:40 AM
John Kitchin writes:
> I like the variable idea. I would make it a concatenation string for
> joining. That way “” would concatenate the way Tyler wants, “ “ would
> preserve current behavior, and “,” could lead to a comma separated
> list for example. Other things like “\n” might lead to a colum
I like the variable idea. I would make it a concatenation string for
joining. That way “” would concatenate the way Tyler wants, “ “ would
preserve current behavior, and “,” could lead to a comma separated list for
example. Other things like “\n” might lead to a column, etc.
On Sat, May 7, 2022 at
Tyler Grinn writes:
> Thanks for the advice. I've added the caret symbol (:EXPORT_FILE_NAME^:
> assignment-1) to mean 'concatenate' as opposed to + for 'joining'. If
> this is something the community would want I will clean it up and send
> in a patch.
Hmm. I am not sure if it going to be a stra
John Kitchin writes:
> I believe this is hard coded in org-entry-get-with-inheritance. The
> fastest option would be an override advice with your own function that
> replaces (and value " ") with (and value ""), and maybe the two other
> " " with "".
>
> John
>
> --
I believe this is hard coded in org-entry-get-with-inheritance. The fastest
option would be an override advice with your own function that
replaces (and value " ") with (and value ""), and maybe the two other " "
with "".
John
---
Professor John Kitchin (he/him/his
I'm exporting sub-trees as pdf files for some classes I'm taking:
# -*- org-use-property-inheritance: t; -*-
* Class A
:PROPERTIES:
:EXPORT_FILE_NAME: support/Class A
:END:
** Assignment 1
:PROPERTIES:
:EXPORT_FILE_NAME+: /assignment-1
:END:
Some assignment for Class A
** Assi
19 matches
Mail list logo
