Forum Replies Created
- Posts
Thank you Yutaka for the attempt to recover, unfortunately the refresh does not help.
On the bright side, I now know why this option is there :-).Now, since me, silly, assigned Shift-S to the swap lines, and I cannot un-do this assignment I am stuck being unable to type capital Ss :-(
I am at despair, please tell me there is one more trick before the complete removal . :-o
Silly on my side to assign Shift-S, true, but it is not to deceive me. It is just a test that ended badly :-( .
Yet, the key combination must not be important John.
So no mistake on my side, the keyboard command assigned must adhere to the configuration setting.
Therefore this is a bug.
Oh yeah Tommy,
Agree with you.
I think I asked about this a long time ago, anyways, this would be a very welcome addition.
My +1
This is an excellent idea and the Macros, too; thank you for supplying them!
Besides, are you the same Stefan who is the moderator on the HippoEdit forum?
I would disagree with you on this comment Meir,
Such functionality exists in many editors EE has to compete against.
For example Sublime Text can swap lines with Ctrl-Shift-ArrowUp.
And it is one of its most used features: http://bit.ly/VYn8xWDoes it add slowness? I doubt that. Yet, people who shell $50 for an editor probably are on a 2-3 year hardware refresh cycle. For the rest, slowness is in each app.
On the contrary, it adds productivity.
Dragging is not going to do that in one hit, and for example not possible if you want to position a line at the top.
I think most EE users work on platforms as say Unix and use Windows as merely a window into their OS editing files quickly on the Win side. For them using keyboard is more natural and unintuitive than the mouse and they pick new commands naturally.
Oh, OK, I am on the No Wrap setting and thus this does not apply, was not immediately apparent.
Thank You! … But I would love to have it enabled to be at par with the “Remove New Lines” please.
This then makes the functionality toggle and work in conjunction with the No Wrap mode.
PS: A better name for “Remove New Lines” IMHO would be “Remove New Line Endings“/”Insert New Line Endings“.
My both thumbs are up for the proposed!
By the way your rephrase Meir: “Toggle” is the word and the way to go.
Hello Meir,
Yes, the macro is designed to work on a single line of unselected text.
This is because in the rest of the situations we have the right-click -> Convert Selection > Comment/Uncomment functionality or you can pull these two buttons onto the toolbar.
Agin, the latter just does not work for a single un-highlighted line of code – hence the macro.I must add, this creates some uncomfort for me – split, non-unified functionality :hammer: .
Hope Yutaka is listening: I suggest a change to allow commenting code regardless of whether a line is highlighted/selected.
Hello Meir,
It highlights and comments out a line of code (even if it was commented out already). You need to just position the cursor within the line.
While the cursor is still on the same (just commented) line it un-comments it.
Not quite there, but the following variation is almost what I need, how to un-select a line?
if( document.selection.IsEmpty )
{
// highlight select and comment
editor.ExecuteCommandByID(4154); editor.ExecuteCommandByID(4371);
}
else
{
// uncomment
editor.ExecuteCommandByID(4372);
}
Probably you meant it will comment in either case. At least the code does this. And I think it would be nice to enhance the functionality so if the comment is already there – uncomment – thus toggling the comments on/off.
I see, but in my case I placed the Comment-Uncomment pair onto the toolbar.
Therefore IMHO, this limitation should not be in this case.
PS: This useful command (I use very often) is buried too deep in the menus, I suggest to elevate it.
Yeah, that made the trick, thanks.
Also thinking it probably be should off by default.
Another related nuance, looks like the Markers work (position the cursor at a marker) only if I am at the beginning of a document. To me, this is a deficiency.
Awesome, thank you.
One suggestion, since it is language specific, I suggest this feature shall reside in the configuration properties section.
I am also curious if there is a complete listing of all the IDs for the editor.ExecuteCommandByID command?
Thank you!
This works but I am curious if I can get rid of the multiple messages when printing
—————————
EmEditor
—————————
Portions of lines may continue beyond the right edge of the page. Would you like to wrap lines according to the page width?
—————————
Yes No Cancel
—————————
?May I suggest to improve the Display tab functionality in the Tools -> Properties for … Configuration(s)?
I guess it may be a lot more informative by providing a comprehensive view on how the formatted code looks like as the result of applying all the config settings, not just [like now] showing an individual setting on a single line below (obviously the view must then become larger and/or span an additional window/pre-view).
By the way, frankly, I think this may alleviate the pain of missing some important mishaps in config as for example string highlights not spanning over multiple lines (see thread http://goo.gl/xEBNk).
I say yes.
But in what languages keeping the “Continue to Next Line” setting does not make sense I am curious?
Let’s apply the laws of democracy, if in most languages this setting does not make sense then let’s keep it as is, but I doubt this is the case.
I think Meir’s suggestion makes a lot of sense, at least to me.
My concern is I never learn/pick up new changes otherwise.
Thank you for your thoughts.PS: I think it makes sense to also pop up a release notes page (e.g. bug fixes) optionally at the end of the installation.
Thank you. This now works well for me.
One small item: the page margin settings got reverted back to 1″ (from 0.25″ that I defined to use).
So, is it possible to preserve this setting between editor upgrades?Thank you,
Yes, this is exactly the issue. I used a brand new Cannon printer with an uptodate driver. I at the moment have no access to any other printer, but I trust it is editor related 100\% because SSMS prints correctly. And your printer exibits the issue, too. I was not too eloquent describing the issue.
One other small sugesstion I gave: the file name should be aligned with the text body and the footer info as page X out of Y text.
