On Mon, Nov 28, 2022 at 05:40:44PM +0100, Jean-Marc Lasgouttes wrote: > Le 21/02/2022 à 15:10, Jean-Marc Lasgouttes a écrit : > > Le 21/02/2022 à 03:27, Scott Kostyshak a écrit : > > > On Sun, Feb 20, 2022 at 07:20:24PM +0100, Jean-Marc Lasgouttes wrote: > > > > I really wonder why this special behavior is by default, since > > > > it is only > > > > useful for interactive edition. > > > > > > > > I would prefer to have > > > > char-delete-forward confirm > > > > bound to the <del> key. > > > > > > That sounds reasonable to me. > > > > Here is what I came up with. Scott, please tell me whether the bit in > > release notes makes sense. > > > > What is missing here is the prefs2prefs_lfun.py part. I tried it a bit, > > but python does not like me. Could somebody help for this part? > > > > The interesting functions are (word|char)-delete-(for|back)ward > > * If there is no argument, add argument `confirm'. > > * If the argument is `force', remove it. > > * If it is another string, remove it too actually (although it should > > not happen) > > > > I really do not understand how this magic python thing works. I have not > > been able to make it match any of my regexes. > > Ping! > > Here is an updated version of the patch. I need help for the > prefs2prefs_lfun.py script, along the lines presented above. Can someone do > it or at least give directions? > > Note that the patch as it stands changes the behavior of LyX: I did not add > 'confirm' to the commands in lib/bind/, since I expect that to be done by > pref2pref. > > Just as a reminder, the goal is to have char-delete-backwards without > argument actually delete previous element, without consideration of > confirmation that are only relevant to interactive use.
Sorry, I have no experience with this. > Once sorted out, this would be candidate for 2.4.0. OK. Scott
signature.asc
Description: PGP signature
-- lyx-devel mailing list [email protected] http://lists.lyx.org/mailman/listinfo/lyx-devel
