Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [PATCH] Auto feature for minibuffer toolbar

Le 19/04/2015 00:00, Scott Kostyshak a écrit : Regarding your comment No need to keep the minibuffer open anymore can you add why to the comment? Is it because a command was just executed? Yes, exactly. Also, what if you misspelled the command you entered so that the command is disabled?

[patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [LyX/master] Document forest.

Am Montag, 20. April 2015 um 18:31:10, schrieb Juergen Spitzmueller sp...@lyx.org \author -712698321 Jürgen Spitzmüller \author -195340706 Georg Baum +\author 155139281 Jrgen Spitzmller What happened with your name? Kornel signature.asc Description: This is a digitally signed

Re: [patch] PassThruChars

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?

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [PATCH] Auto feature for minibuffer toolbar

Le 19/04/2015 00:00, Scott Kostyshak a écrit : Regarding your comment "No need to keep the minibuffer open anymore" can you add why to the comment? Is it because a command was just executed? Yes, exactly. Also, what if you misspelled the command you entered so that the command is disabled?

[patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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?

Re: [patch] PassThruChars

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

Re: [LyX/master] Document forest.

Am Montag, 20. April 2015 um 18:31:10, schrieb Juergen Spitzmueller > \author -712698321 "Jürgen Spitzmüller" > \author -195340706 "Georg Baum" > +\author 155139281 "Jrgen Spitzmller" > What happened with your name? Kornel signature.asc Description: This is a

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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

Re: [patch] PassThruChars

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