Troubleshooting Continuous Glitches in EmEditor: A Comprehensive Guide

Viewing 8 posts - 1 through 8 (of 8 total)

• Author
  Posts
• January 13, 2009 at 11:30 am #6817
  jugaor
  Participant
  Hola, amigo Yutaka.
  EM is a great product, but at your request (“earlier rather than later”) I want to report here several issues (all versions). I numbered’em to facilitate your answers :-D
  Sorry for my bad English, I’ll try to be as clear as possible.
  1. The OR operator with ‘Search Only Word’ got confused if an including word goes first at the expression (two or more):
  (siempre|sintagma|si) OK, matches ‘siempre’/’sintagma’/’si’
  (si|siempre|sintagma) BAD, matches ‘si’ but not ‘siempre’/’sintagma’
  (If this is the expected behavior, please say it at “Regular Expression Syntax” section inside Help)
  2. “Find and Replace in Files” operations treat the special chars (‘ñ’, ‘ç’, accented vowels) as word boundaries. For example: “aca” with ‘Search Only Word’ matches the first part of “acañar” or the last parts of “austríaca”, “ilíaca” and so………
  BUT if “Use Regular Expressions” is enabled too, EM works well (!!!). (F&R at open files never have any problem).
  3. Please stop the “Escape sequence” auto triggering in F&R dialog (I already said it in a previous post :-(). Besides the additional click to deactivate it, it always duplicates / and chars at Find Line. A nicer behavior could be remember the last user selection of switches.
  4. The dialog “Treat the following characters as alphanumerics” (Customize) is working…? (i.e., it applies to what operations?)
  If I add any alien char (for example @) EM still treats it as non-letter (using ‘Search Only Word’ or the w operator).
  5: (Helpfile) Please include two clarifications (for regexp newbies as I… was ;-)):
  a) The ordinals (º,ª) are always treated as alphanumeric, not word boundaries, so l and w includes’em.
  b) The “(?” subexpressions allow several strings with I (OR operator), but the lookbehind ones must be lenght fixed.
  Thank you very much for your time, attention and talent!
  Saludos desde Perú,
  jugaor
  January 13, 2009 at 11:09 pm #6818
  Yutaka Emura
  Keymaster
  I will try to address these issue in the future major version. If v9 beta still has these issues, please let me know. Thank you!
  January 15, 2009 at 6:39 pm #6821
  Yutaka Emura
  Keymaster
  (4.) “Treat the following characters as alphanumeric” option applys only when editing. For instance, when you double-click a word, these characters are treated as a part of the word. However, this setting does not apply to the regular expression w operator nor the Search Only Word option in the Find dialog box. I will clarify the Help description.
  (5.) I will add a description the lookbehind patterns must be of fixed length .
  .
  May 19, 2009 at 5:07 am #7303
  Yutaka Emura
  Keymaster

  jugaor wrote:
  Hola, amigo Yutaka.
  EM is a great product, but at your request (“earlier rather than later”) I want to report here several issues (all versions). I numbered’em to facilitate your answers :-D
  Sorry for my bad English, I’ll try to be as clear as possible.

  1. The OR operator with ‘Search Only Word’ got confused if an including word goes first at the expression (two or more):
  (siempre|sintagma|si) OK, matches ‘siempre’/’sintagma’/’si’
  (si|siempre|sintagma) BAD, matches ‘si’ but not ‘siempre’/’sintagma’
  (If this is the expected behavior, please say it at “Regular Expression Syntax” section inside Help)

  2. “Find and Replace in Files” operations treat the special chars (‘ñ’, ‘ç’, accented vowels) as word boundaries. For example: “aca” with ‘Search Only Word’ matches the first part of “acañar” or the last parts of “austríaca”, “ilíaca” and so………
  BUT if “Use Regular Expressions” is enabled too, EM works well (!!!). (F&R at open files never have any problem).

  3. Please stop the “Escape sequence” auto triggering in F&R dialog (I already said it in a previous post :-(). Besides the additional click to deactivate it, it always duplicates / and chars at Find Line. A nicer behavior could be remember the last user selection of switches.

  4. The dialog “Treat the following characters as alphanumerics” (Customize) is working…? (i.e., it applies to what operations?)
  If I add any alien char (for example @) EM still treats it as non-letter (using ‘Search Only Word’ or the w operator).

  5: (Helpfile) Please include two clarifications (for regexp newbies as I… was ;-)):
  a) The ordinals (º,ª) are always treated as alphanumeric, not word boundaries, so l and w includes’em.
  b) The “(?” subexpressions allow several strings with I (OR operator), but the lookbehind ones must be lenght fixed.

  Thank you very much for your time, attention and talent!
  Saludos desde Perú,
  jugaor
  “Search Only Word” will not work well with Regular Expressions. Instead, you should use Word Boundaries:
  The following escape sequences match the boundaries of words:
  < Matches the start of a word.
  > Matches the end of a word.
  b Matches a word boundary (the start or end of a word).
  B Matches only when not at a word boundary.
  I will add thse expressions to the Help.
  “Treat the following characters as alphanumeric” did not work when searching. This will be fixed in the next alpha version (alpha 19).
  In order to stop the “Escape sequence” auto trigerring in F&R dialog, you can now uncheck both “Use Selected Text in Find/Replace dialog box” and “Use Word at Cursor in Find/Replace dialog box” in the “Search” tab of the Customize dialog box.
  Thanks so much for your input!
  May 20, 2009 at 3:14 am #7305
  jugaor
  Participant
  Thank you for your answers!
  “Search Only Word” will not work well with Regular Expressions. Instead, you should use Word Boundaries:
  Please, clarify if this behavior is only at the current version or will be permanent… to begin editing my macros now… :-o
  Cheers,
  jugaor
  May 20, 2009 at 5:02 am #7306
  Yutaka Emura
  Keymaster
  jugaor wrote:
  Thank you for your answers!

  “Search Only Word” will not work well with Regular Expressions. Instead, you should use Word Boundaries:

  Please, clarify if this behavior is only at the current version or will be permanent… to begin editing my macros now… :-o

  Cheers,
  jugaor
  All versions. The word boundary regular expressions are available both on v8 and v9. So you shouldn’t use “Search Only Word” checkbox with regular expressions.
  May 20, 2009 at 7:20 am #7307
  jugaor
  Participant
  OK, thank you!
  If there are more “hidden” escape sequences ;-) (i.e, not included at the current Help), please, inform here.
  The additions are always welcome to improve scripting proficiency.
  In order to stop the “Escape sequence” auto trigerring in F&R dialog, you can now uncheck both “Use Selected Text in Find/Replace dialog box” and “Use Word at Cursor in Find/Replace dialog box” in the “Search” tab of the Customize dialog box.
  BTW, I didn’t find the first option, only the latest… It changed of dialog box? (v8.05)
  Un abrazo desde Perú!
  May 20, 2009 at 9:11 am #7308
  jugaor
  Participant
  UPDATE:
  I began to change my scripts and I must say that the results now are more accurate! :-D
  But, there’s a severe speed penalization, too :-(
  Not the biggest problem in Earth… but If you can optimize this issue, I’ll thank you very much!
  Thanks again for make this marvelous app better and better with each version!
  Un abrazo!

• Author
  Posts

Viewing 8 posts - 1 through 8 (of 8 total)

• You must be logged in to reply to this topic.

Also read: