Mastering Line Removal with EmEditor’s Custom CurText Parsing Feature

Tagged: bug , CurText , external tool , selection

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

• Author
  Posts
• May 18, 2016 at 6:12 am #20858
  LifeTimer
  Participant
  If I have defined an External Tool that takes “Custom” input, and then define this custom input as “$(CurText)”, there is a bug that sends also any filtered-out lines inside the selectiong as input to this External Tool when multiple lines are selected.
  For example, if you have the following lines in your document:

  111
  222
  333
  444
  And then I create a filter that removes all lines containing “222” and “333”, resulting in the following appearance in the editor:
  111
  444
  If I now select both these lines, and then execute my External Tool, it will still get all the four lines as input (i.e. “111”, “222”, “333” and “444”), which seems like an obvious bug to me, right?
  May 18, 2016 at 11:23 am #20862
  Yutaka Emura
  Keymaster
  Hello,
  I will fix this on the next beta version.
  Thank you!
  May 18, 2016 at 11:29 am #20864
  LifeTimer
  Participant
  Excellent, thanks!

• Author
  Posts

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

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

Also read: