For the ,, failing to find placeholder may I recommend a message to log "Failed to find abbreviation placeholder" ? This way people really will be able to discover it and it will at least give them a starting point on where to look for help.
On Saturday, November 14, 2015 at 12:29:10 PM UTC-5, Terry Brown wrote: > > On Sat, 14 Nov 2015 07:48:31 -0600 > Kent Tenney <[email protected] <javascript:>> wrote: > > > declaring > > @string next-placeholder-abbrev = ,, > > > > with scripting turned off didn't work for me > > Could be a temporal sequencing error, i.e. using features before > they're implemented doesn't always work :-) > > I've just pushed with abbreviations on by default, Edward can decide if > that goes too far... > > - you can't type ,, now, it selects the next <|placeholder|> or just > gets replaced with nothing. I guess failing to find a placeholder > should yield ",,", although that would be less convenient for > placeholder use > - typing html;; gives an html template with a selected placeholder > - typing date;; gives {|{x=time.asctime()}|} unless > @bool scripting-abbreviations = True > or > @bool scripting-at-script-nodes = True > > To type ",," you have to type ", ," and delete the space. But maybe > that's ok, it's a way to let people find abbreviations :-) > > Alternatively, we could have a different default "next placeholder" > abbreviation. Really, does it even need to be an abbreviation? If it > was a command, you could bind it to any non-inserting key. > > Kent - I went with > @string abbreviations-next-placeholder = ,, > for consistency with other settings names. > > Cheers -Terry > -- You received this message because you are subscribed to the Google Groups "leo-editor" 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
