Forum Replies Created

Viewing 25 posts - 101 through 125 (of 126 total)
  • Author
    Posts
  • in reply to: Back reference in scripts #4868
    CaptainFlint
    Participant
    in reply to: Beta8: FindBar checkboxes has wrong background #4741
    CaptainFlint
    Participant

    Still not fixed in beta 10…

    in reply to: Beta 6 triple click needs enhancement #4740
    CaptainFlint
    Participant

    2 Yutaka
    Any comments on this?

    in reply to: Beta8: Wrong color for Ruler/LineNumber background #4739
    CaptainFlint
    Participant

    Fixed in beta 10.

    in reply to: Changing multiple spaces to one space #4723
    CaptainFlint
    Participant

    JavaScript has its own Escape-character ” and uses it for its own purposes. So, when you write ‘s’ JavaScript converts it into single ‘s’, when you write ‘1’ it is converted into character with octal code 001, etc. The correct expression hence would be:
    document.selection.Replace(‘(s){2,}’, ‘1’, eeFindReplaceRegExp | eeReplaceAll);

    in reply to: Beta 9 line number and ruler color display #4721
    CaptainFlint
    Participant

    Already reported here.

    in reply to: Beta8: double-click does not select word inside quotes #4720
    CaptainFlint
    Participant

    Confirm fix in beta9. Thank you, this was very annoying. :)

    in reply to: [BUG]So good,Beta 9 Fixed– "FindBar" plug-ins button #4652
    CaptainFlint
    Participant

    Right click -> uncheck the Find Toolbar menu item.

    in reply to: [BUG]So good,Beta 9 Fixed– "FindBar" plug-ins button #4648
    CaptainFlint
    Participant

    Confirm with non-portable version too.

    in reply to: Printing sends text in wrong codepage #4467
    CaptainFlint
    Participant

    Well, I managed to fix it. In the printer settings I changed the setting True Type Font from Substitute with Device Font into Download as Softfont, and now it prints correctly.
    However, I’m not sure that it is the best solution and that the printer will not print something wrong someday…

    However, the source of the problem is still a complete mystery for me – if I change the “1252” registry key back to “c_1252.nls”, the printer prints Russian fonts correctly even with “Device Font” setting. But 1252 is not Russian codepage! It does not contain ANY Russian character! How can it affect printing Russian text then??? :-?

    in reply to: move vertical line #4465
    CaptainFlint
    Participant

    you sure it cant be done with any script?

    With some external program – maybe. Also it seems to be possible to write such a plugin… But I can’t see how EE’s script could do that.

    in reply to: move vertical line #4461
    CaptainFlint
    Participant

    If I understood you correctly, by “vertical line” you mean usual text cursor (caret), right? In this case what you asked for is impossible (AFAIK).

    in reply to: unicode #4414
    CaptainFlint
    Participant

    This message warns you that you do have Unicode characters in your file and that they will be lost when saving (replaced with other characters, mostly with question marks).
    If there ware no such message and EE just silently replaced all the unicode characters, you would risk to see some day that one (or more) of your files edited earlier became completely unreadable and unrecoverable (if you e.g. saved in wrong codepage by mistake).

    in reply to: how to easy rearrage text #4402
    CaptainFlint
    Participant

    Select the 111-222-333 text with Alt+mouse drag (rectangular selection), then copy&paste it at the position just behind the “aaa” text.

    in reply to: Return method is not shown now #4308
    CaptainFlint
    Participant

    Thank you, I’ll check it as soon as the release is out.

    in reply to: Multiple search string highlight #4302
    CaptainFlint
    Participant

    Just increase the number Search Colors in the same tab of the Configuration dialog.

    in reply to: [^xyz] always matches newline? #4287
    CaptainFlint
    Participant

    So, is this intentional that [^xyz] matches newlines? Could it be made e.g. optional, that is – if I select that the regexps work in one single line only, they really worked in one single line only? What’s the usefulness of the option that sometimes works, sometimes not?

    in reply to: [^xyz] always matches newline? #4281
    CaptainFlint
    Participant

    If this is intentional, then the option have to be renamed from “Regular Expressions Can Match New Line Characters” to e.g. “Period Can Match New Line Characters”

    in reply to: Can I create myself plugin for EmEditor? #4263
    CaptainFlint
    Participant

    Please, read help. The plugin API is completely described there.

    in reply to: EmEditor Professional 6.00.4 RC #4258
    CaptainFlint
    Participant

    Problem reported in this thread is not fixed.

    in reply to: delete spaces at the begining of the lines #4225
    CaptainFlint
    Participant

    can you tell me how to assign this with a keyboard shortcut (eg ctrl+j) ?

    Only by writing a macro and assigning the hotkey to it.

    I personally use Shift+Tab several times or plugin “Align Left”.

    CaptainFlint
    Participant

    There are many kinds of programmers’ tricks. For example, for extremely quick access to some data associated with some text, so-called hash-tables are used. They allow to find the specified line of text very quickly, without necessity of successive comparing it with every piece of text present in the table.

    Now, let’s have an example: regexps could be stored in a kind of hash-table, and hence they could be accessed very quickly, without looking each of them one-by-one. If you add the possibility of setting priorities, you will have to look each and every of them, just to know if there is some other regexp that has higher priority. If there are many highlighting rules, this would become a very long task. Would you like EmEditor to wait for 10 seconds every time it has to redraw the screen? :)

    Of course, I don’t know if Yutaka uses hash-tables for storing regexps, but anyway, it was just an illustrative example (and, besides, I won’t wonder if he really does).

    CaptainFlint
    Participant

    Yutaka has explained somewhere that for highlighting he uses a mechanism that is very fast and effective but does not allow to prioritize the rules.

    CaptainFlint
    Participant

    Just go to the Configuration dialog, Keyboard tab, specify Shift+Backspace and select the action Edit -> Delete Left Character.

    in reply to: Return method is not shown now #4146
    CaptainFlint
    Participant

    If “No Change” is preselected, return methods are mixed.

    Sorry if my report was not clear. I was talking not about saving itself, but about displaying the return methode in the Save As dialog, nothing more!

    OK, I’ll try to describe it more detailed.

    1. Preconditions:
    a) the file test_lf.txt contains LF returns only;
    b) in EmEditor the setting Configuration -> File -> Saving -> Return Method is set to “No Change”.

    2. Install EmEditor 6.00.2, run it, open the file test_lf.txt. Select File -> Save As menu command, the dialog appears. Look at the Return Method combobox: you will see LF Only (UNIX).

    3. Install EmEditor 6.00.3, run it, open the file test_lf.txt. Select File -> Save As menu command, the dialog appears. Look at the Return Method combobox: you will see No Change.

    Why in 6.00.2 the current return method is selected by default, while in 6.00.3 it is not? It was more convenient in 6.00.2.

    Besides, I support the idea of danderson with displaying the return method in the status bar. It would be very convenient too.

Viewing 25 posts - 101 through 125 (of 126 total)