Hello Tony, Hi all
to explain the problem a little wider:
I am working on a screewriting tool a part of which should of course be autoformating the text according to the necessities of o screenplay. I think I already described the standarts above. A part of the idea is to use the standard TW markup for lists an headings (: and !) in this formating (Which interestingly is also compatible with the fountain syntax) This makes sense because it is usefull to have a syntax which just needs a marker at the start of the line and does not have to be closed (like <dialog> </dialog>). The problem with this syntax in TW is that the whole formatting might be broken if you forget the blank line in between. This is why I seek a parser which does not need the blank line before headings and lists.

Thanks for your interest and help.
Jan


Am 17.09.2017 um 02:18 schrieb TonyM:
Jan,

I hope someone can help you get what you are asking for but I can't help but think you are somewhat partially dictating a solution and not describing the problem. I understand why Josiah was trying to open up discussion. I support his approach.

One reason I wanted a clear understanding of what was needed, what was the root problem to be solved, is because I am confident there are already solutions that will address these effectively. In TWC there are a number of opportunities to effect something similar, but I have seen them appearing in TW5 in different guises. But I am not so sure, because more specific questions are being asked.

Less specific questions may elicit answers that are more broadly applicable to others.

For one, I am keen to develop a number of "shorthand" methods while taking notes in class to enter text with Questions. Answers, Actions, Personal areas to explore, key knowledge item etc. CSS, Auto Replace, Editor Tools and more can solve these problems along with a parser.

Also digression into Auto-hot key becomes applicable in notepad, word and outside TWC/TW5, I have not looked but I am quite sure Autohotkey workes on other platforms as well, or at least has equivalents.

Lets see if someone can answer your question, but please consider why the discussion diverged.

Regards
Tony

Regards
Tony



On Sunday, September 17, 2017 at 5:30:37 AM UTC+10, Jan wrote:

    Hi Josiah,
    I wrote it this general here, because Jeremy mentioned the
    idea/intention somewhat above.

    My desires are quite simple:
    I would like to have something which can transform the parsing of
    a set of tiddlers which are defined by a listfilter according to a
    replacePragma defined by reg-Expressions:

    Transform: [tag[Scene]]

    In Skeeves Pragma the desired changes would be this:
    \replace /\n!/\n\n!/
    \replace /\n:/\n\n:/
    \replace /\n{{/\n\n:{{/
    \replace /}}/}} /

    Yours Jan







    Am 16.09.2017 um 11:43 schrieb @TiddlyTweeter:
    Ciao Jan

        Is there anyone working on or willing to work on adjustible
        parsers?


    I feel, as I look at this more, that we have to get precise about
    what we asking help for---otherwise its maybe TOO open-ended and
    would be a burden for others to cope with?

    I'm working on breaking the issue down into PARTS--as far as I'm
    able--so that a more limited question (hopefully) someone might
    have interest in and be able to answer without burden.

    Its tricky, in that the underlying issue with "auto-markup" is
    quite close to the central way TW works--so there are a lot of
    implications to deal with---and no sane helper will want to deal
    with all that :-).

    Best wishes
    Josiah
-- You received this message because you are subscribed to the
    Google Groups "TiddlyWiki" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to [email protected] <javascript:>.
    To post to this group, send email to [email protected]
    <javascript:>.
    Visit this group at https://groups.google.com/group/tiddlywiki
    <https://groups.google.com/group/tiddlywiki>.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/tiddlywiki/744d7001-c127-4830-9a4a-7bda014c5e92%40googlegroups.com
    
<https://groups.google.com/d/msgid/tiddlywiki/744d7001-c127-4830-9a4a-7bda014c5e92%40googlegroups.com?utm_medium=email&utm_source=footer>.
    For more options, visit https://groups.google.com/d/optout
    <https://groups.google.com/d/optout>.

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/fbe06126-de10-4472-a52e-b3484316bb93%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/fbe06126-de10-4472-a52e-b3484316bb93%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/59BE4A43.4070007%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to