From: forkosh@panix.com   
      
   Javier  wrote:   
   > John Forkosh  wrote:   
   >> And the result is ... no blinking. So any differences   
   >> in the elisp stuff between 27.2 and 28.2 is apparently   
   >> not responsible for the behavior.   
   >   
   > Very clever. You have demonstrated that the bug is harcoded in C.   
      
   Yeah, and I apparently posted the question in the wrong newsgroup   
   to begin with. I'd originally figured any such source code bug   
   would have quickly been detected (I'd thought lots of people would   
   notice they couldn't disable blinking) and then quickly fixed.   
   So I naively guessed the problem's some kind of slackware   
   configuration issue. That did seem a bit odd, but so did   
   everything else I could think of -- a possible elisp issue only   
   occurred to me after googling mentioned it, which was after I'd   
   already posted the question here.   
      
   > This disables the feature for me in emacs 28.0   
   >    (setq blink-matching-paren-distance 0)   
      
   Thanks so much, Javier. That immediately stopped the blinking.   
   Don't know emacs internals all that well, and never would have   
   thought of that myself.   
      
   > Also see:   
   >    M-: (info "(emacs) Matching")   
      
   And thanks for the pointer to additional documentation.   
      
   > Also:   
   >    The blinking paren feature is useful. It prevents syntax errors.   
   >    I keep the feature enabled myself.   
      
   Yeah, and sometimes my own C code has lots of nested {{{...}}}'s   
   which I sometimes have to stop and stare at to keep straight.   
   But the blinking is just way too distracting for me, personally.   
   And that inconvenience is way worse that the offsetting convenience,   
   at least for me.   
      
   > BTW I don't recomend gtk3 toolkit.  Use lucid instead, it matches   
   > better the Slackware philosophy.  gtk3 toolkit changes appearance too   
   > offen and has more bugs.  But that is unrelated to blinking parens.   
   >    ./configure --with-x-toolkit=lucid  --prefix=${HOME}/local ;   
   >     make ; make install   
      
   Haven't (yet) noticed any other problems, but I'll give it   
   a try, building it that way. Then I'll have three targets   
   for my emacs-with-x11 symlink: -27.2, -28.2, and -28.2-lucid :   
     "You can never be too rich or too thin, or have too many   
      versions of emacs."   
   --   
   John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)