Re: [Texmacs-dev] Questions about drd-props.

[Karl Hegbloom]

Ok. I have a feeling that the drd-props thing is not fully thought out or at least not yet fully coded or developed. I found that changing the drd-props statements has no immediate effect. The reload styles menu must be called to make the change happen. The combinations of accessible and enable-writeability don't all seem to do what I was expecting, but that isn't the same as saying they don't work like they are supposed to or as designed. Most of the drd-props values are not documented in the manual either.

Have you had a chance to try my plugin? The master branch or the branch-v1.2a are ready for alpha testing. Please use my github issue tracker to report success or fail and to provide feedback and suggestions.

On Tue, Feb 28, 2017, 01:49 Sam Liddicott <address@hidden> wrote:

It does appear to me that an enhancement is made to TeXmacs to avoid the obstruction of the if command.

And so I am unable to answer your question, sorry.

Sam

On 27 February 2017 at 01:58, Karl Hegbloom <address@hidden> wrote:

The attached .tm has two sets of tags, one with an if inside and the other using compound and merge. There is no difference in the ability to move the cursor inside of the "body" part in either case.

Can you send me a .tm with a preamble like this one that demonstrates what you mean?

On Sun, Feb 26, 2017 at 10:46 AM Karl Hegbloom <address@hidden> wrote:

I understand what changes to make, and as soon as I'm at the library, which opens at noon today (Sunday) is the first thing I'll experiment with.

What is it about if - then that makes it do that?

On Sun, Feb 26, 2017, 00:17 Sam Liddicott <address@hidden> wrote:

The only thing I know that stops the cursor moving inside a tag is that the macro has an if-then-else clause in it. 

If so, this can be overcome by removing the if clause and replacing with compound call to a macro whose name is computed from the value of the original if clause.

If you don't understand this, then try to simplify the macro as a test case to see if you can then enter the tag.

If that works, then I can help construct an alternative macro that works too.

Sam

On 25 Feb 2017 8:52 p.m., "Karl Hegbloom" <address@hidden> wrote:

In my package, there is a tag structure that looks sort of like this (using LaTeX like syntax rather than TeXmacs):

 \zcite{zfieldID}{zfield-Data-v}{zfield-Text-t}

where the zfield-Text-t is like:

\zciteLayoutPrefix{...}\zsubCite{...}\zciteLayoutDelimiter{...}...\zciteLayoutSuffix{...}

When the cursor is just to the right of the zcite, it is highlit by a cyan box. Pressing the left arrow key causes the cursor to jump all the way over the zcite. When the cursor is just to the right of the zcite and I press Backspace, it disactivates the tag and then I can move the cursor inside of it. While I am inside of the disactivated zcite, the cursor moves in and out of the zciteLayoutPrefix, zciteLayoutDelimiter, and zciteLayoutSuffix tags.

The desired behavior is that I want to be able to cursor inside of the zcite's zfield-Text-t, but I don't want to be able to cursor inside of the zciteLayoutPrefix, zciteLayoutDelimiter, zciteLayoutSuffix, or zsubCite tags, and of those, only the zsubCite tag can usefully support being disactivated or changing mode to allow the cursor to move inside of it's contents.

I actually like the way the cursor jumps across the zcite, leaving it as a whole thing in itself... but I am implementing cutting and pasting of zsubCite's that occur within the zcite, since a zcite field contains a citeproc citation cluster that can have more than one source cited... So if I could add another flag to the zfield-Data-v that is to hold the "drd" state of the zfield... and have it support more than one "mode": (1) Normal, where the cursor jumps across it, (2) cursor can move inside of the zfield-Text-t, but the zcite is not disactivated, (3) zcite is disactivated.

In state (2), I want the cursor to jump over zsubCite's and the other elements, which are the CSL style's citation layout prefix, delimiter, and suffix strings wrapped in tags to give them handles and semantics. In state (2), I ought to be able to use Ctrl-Space to set the mark, then arrows to select zsubCite's. It does that now, and does select entire blocks, but not as neatly, plus...

When in state (2), I want to move the cursor inside of the zfield-Text-t, but have it's movement constrained to points between the zciteLayoutPrefix, zsubCite, zciteLayoutDelimiter, or zciteLayoutSuffix, while the user chooses a location at which to perform a clipboard-paste of zsubCite's taken via clipboard-cut from another zcite field.

The constrained movement could be implemented via keyboard command overloads that respect the context the way I need... but what about drd-props to allow moving the cursor inside of the zcite, without needing to disactivate it first?

Can a scheme program alter drd-props on-the-fly?

I'm having trouble even getting changes to drd-props that I put into the tm-zotero.ts to have any effect at all. From my understanding, it ought to already be allowing the cursor to move inside of the zcite, but it does not. What's the secret to it? I've seen TeXmacs dump a C++ stack trace, and then after that, I could move the cursor inside of the zcite! What changed that allowed that? Can it be set up deliberately without an accidental segv?

_______________________________________________
Texmacs-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/texmacs-dev

_______________________________________________
Texmacs-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/texmacs-dev

_______________________________________________
Texmacs-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/texmacs-dev

_______________________________________________
Texmacs-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/texmacs-dev