2015-04-21 0:15 GMT+02:00 aparsloe:
As I understand it, you are implementing an enhancement request I made 3
years ago: #8347. I am delighted.
Nice. Didn't see that.
Jürgen
Andrew
2015-04-21 0:15 GMT+02:00 aparsloe:
> As I understand it, you are implementing an enhancement request I made 3
> years ago: #8347. I am delighted.
>
Nice. Didn't see that.
Jürgen
>
> Andrew
>
On 04/20/2015 06:15 PM, aparsloe wrote:
On 21/04/2015 12:43 a.m., Jürgen Spitzmüller wrote:
In order to implement a linguistic feature properly (support for the
forest package to generate structure trees), I need a way to pass
only selected chars verbatim (here, [ and ], since these are active
On 21/04/2015 12:43 a.m., Jürgen Spitzmüller wrote:
In order to implement a linguistic feature properly (support for the
forest package to generate structure trees), I need a way to pass only
selected chars verbatim (here, [ and ], since these are active
characters in the package and thus must
2015-04-20 14:59 GMT+02:00 Richard Heck:
Yes, this sounds generally useful.
My only thought would be: Wouldn't it be slightly easier to store the
pass_thru_chars as a vector rather than call getVectorFromString every time
we need it?
I pondered about this as well. I just think we only need
On 04/20/2015 08:43 AM, Jürgen Spitzmüller wrote:
In order to implement a linguistic feature properly (support for the
forest package to generate structure trees), I need a way to pass only
selected chars verbatim (here, [ and ], since these are active
characters in the package and thus must
In order to implement a linguistic feature properly (support for the forest
package to generate structure trees), I need a way to pass only selected
chars verbatim (here, [ and ], since these are active characters in the
package and thus must not be escaped by braces). Making the whole inset
Le 20/04/2015 14:43, Jürgen Spitzmüller a écrit :
In order to implement a linguistic feature properly (support for the
forest package to generate structure trees), I need a way to pass only
selected chars verbatim (here, [ and ], since these are active
characters in the package and thus must not
Le 20/04/2015 16:16, Jürgen Spitzmüller a écrit :
2015-04-20 15:51 GMT+02:00 Jean-Marc Lasgouttes:
If these are plain characters, why shall the list be comma separated
instead of being a plain string?
It did not occur to me to simply use a string, but you are right, it is
much easier
On 04/20/2015 10:16 AM, Jürgen Spitzmüller wrote:
2015-04-20 15:51 GMT+02:00 Jean-Marc Lasgouttes:
If these are plain characters, why shall the list be comma
separated instead of being a plain string?
It did not occur to me to simply use a string, but you are right, it
is much easier
2015-04-20 15:51 GMT+02:00 Jean-Marc Lasgouttes:
If these are plain characters, why shall the list be comma separated
instead of being a plain string?
It did not occur to me to simply use a string, but you are right, it is
much easier that way. See attached.
Jürgen
JMarc
diff --git
2015-04-20 16:57 GMT+02:00 Jean-Marc Lasgouttes:
I suspect that lex does not allow you to specify quoted strings. Does
this means that one cannot enter strings containing spaces? Are spaces
supported by the functionality, actually?
It works for me (quoted strings, that is). On the other
Le 20/04/2015 17:15, Jürgen Spitzmüller a écrit :
2015-04-20 16:57 GMT+02:00 Jean-Marc Lasgouttes:
I suspect that lex does not allow you to specify quoted strings.
Does this means that one cannot enter strings containing spaces? Are
spaces supported by the functionality, actually?
2015-04-20 17:21 GMT+02:00 Jean-Marc Lasgouttes:
We'll have to do something about FreeSpacing that implies that spaces are
output as ~. This prevent us from implementing alltt as a better version of
the horrible LyX-Code.
I just tested, and the following seems to work (consecutive spaces are
2015-04-20 17:26 GMT+02:00 Jürgen Spitzmüller:
2015-04-20 17:21 GMT+02:00 Jean-Marc Lasgouttes:
We'll have to do something about FreeSpacing that implies that spaces are
output as ~. This prevent us from implementing alltt as a better version of
the horrible LyX-Code.
I just tested, and
In order to implement a linguistic feature properly (support for the forest
package to generate structure trees), I need a way to pass only selected
chars verbatim (here, [ and ], since these are active characters in the
package and thus must not be escaped by braces). Making the whole inset
On 04/20/2015 08:43 AM, Jürgen Spitzmüller wrote:
In order to implement a linguistic feature properly (support for the
forest package to generate structure trees), I need a way to pass only
selected chars verbatim (here, [ and ], since these are active
characters in the package and thus must
2015-04-20 14:59 GMT+02:00 Richard Heck:
> Yes, this sounds generally useful.
>
> My only thought would be: Wouldn't it be slightly easier to store the
> pass_thru_chars as a vector rather than call getVectorFromString every time
> we need it?
>
I pondered about this as well. I just think we
Le 20/04/2015 14:43, Jürgen Spitzmüller a écrit :
In order to implement a linguistic feature properly (support for the
forest package to generate structure trees), I need a way to pass only
selected chars verbatim (here, [ and ], since these are active
characters in the package and thus must not
2015-04-20 15:51 GMT+02:00 Jean-Marc Lasgouttes:
> If these are plain characters, why shall the list be comma separated
> instead of being a plain string?
>
It did not occur to me to simply use a string, but you are right, it is
much easier that way. See attached.
Jürgen
>
> JMarc
>
>
diff
On 04/20/2015 10:16 AM, Jürgen Spitzmüller wrote:
2015-04-20 15:51 GMT+02:00 Jean-Marc Lasgouttes:
If these are plain characters, why shall the list be comma
separated instead of being a plain string?
It did not occur to me to simply use a string, but you are right, it
is much easier
Le 20/04/2015 16:16, Jürgen Spitzmüller a écrit :
2015-04-20 15:51 GMT+02:00 Jean-Marc Lasgouttes:
If these are plain characters, why shall the list be comma separated
instead of being a plain string?
It did not occur to me to simply use a string, but you are right, it is
much easier
2015-04-20 16:57 GMT+02:00 Jean-Marc Lasgouttes:
> I suspect that lex>> does not allow you to specify quoted strings. Does
> this means that one cannot enter strings containing spaces? Are spaces
> supported by the functionality, actually?
>
It works for me (quoted strings, that is). On the
Le 20/04/2015 17:15, Jürgen Spitzmüller a écrit :
2015-04-20 16:57 GMT+02:00 Jean-Marc Lasgouttes:
I suspect that lex>> does not allow you to specify quoted strings.
Does this means that one cannot enter strings containing spaces? Are
spaces supported by the functionality, actually?
2015-04-20 17:21 GMT+02:00 Jean-Marc Lasgouttes:
> We'll have to do something about FreeSpacing that implies that spaces are
> output as ~. This prevent us from implementing alltt as a better version of
> the horrible LyX-Code.
>
I just tested, and the following seems to work (consecutive spaces
2015-04-20 17:26 GMT+02:00 Jürgen Spitzmüller:
> 2015-04-20 17:21 GMT+02:00 Jean-Marc Lasgouttes:
>
>> We'll have to do something about FreeSpacing that implies that spaces are
>> output as ~. This prevent us from implementing alltt as a better version of
>> the horrible LyX-Code.
>>
>
> I just
On 21/04/2015 12:43 a.m., Jürgen Spitzmüller wrote:
In order to implement a linguistic feature properly (support for the
forest package to generate structure trees), I need a way to pass only
selected chars verbatim (here, [ and ], since these are active
characters in the package and thus must
On 04/20/2015 06:15 PM, aparsloe wrote:
On 21/04/2015 12:43 a.m., Jürgen Spitzmüller wrote:
In order to implement a linguistic feature properly (support for the
forest package to generate structure trees), I need a way to pass
only selected chars verbatim (here, [ and ], since these are active
28 matches
Mail list logo
