Forum Replies Created
- Posts
I second Yutaka!
Please keep EE:
* Stable and robust
* lean and fast loading
(In this order of priority…)IMHO, and I assume that users of EE are programmers, any complex text processing is better done with some scripting language such as Perl, Pyton or Ruby. In particular processing done day-in, day-out.
Please don’t bloat it!
I also vote for such an enhancement!
My model is the browser’s ALT-Left/Right arrow to go backward and forward to previous positions. Exact column positions is less, or not at all important. In fact, I would rather not “waste” edit points on “micro” positions, say on the same line. What I need is “macro” jumps to code segments “under construction”.
As for edited out positions, a line above the original (or below) is fine with me.
Did you consider using Perl and its XML package? If this type of processing is your day-in-day-out activity, I would have opted for that.
You most probably have the following situation:
1) Your file has either Tab/Comma/Whatever-Separated-values
2) You have a checked “Detect CSV” and/or “Detect TSV” of the “File” tab in the “properties” pane of your “configuration” (C++, Perl, etc.)
Good luck!It is already implemented.
Make sure the “Move to Start/End of Document” check box in the “Find” pane is checked.
Sorry ArthurZ,
I vote against!
Reason: too much; too much to develope, too much to test, and do regression testing, too much to learn, too much!
If one key stroke is too much for you, why don’t you write what to me seems like the simplest macro and assign it a shortcut key (my recommendation: SHIFT-CTRL-A,or SHIFT-CTRL-C – the combination of CTRL-A and CTRL-C.)
I am absolutely sure that Asian words cannot be displayed in a Western European encoding!
You must first “Save as…” your edited document as a Unicode one. I would strongly recommend UTF-8 (with or without “signature”). The “encoding” drop-down list is to the left of the “Save” button.
There are many excellent Unicode introductory pages. My favorite is Joel on Software: About Unicode and Character Sets
I hope it helps. Good Luck!
1) What do you mean by “… directly dropped into…”?
2) What encoding is the open document into which you paste? Is it any of the Unicode encodings (e.g. UTF-8)?
3) What was the encoding of the source from where you copied the text? Was it Unicode? Was it of the same or a different encoding than the one you pasted into?
Oh no! Please no!
EE is a lightning fast, full featured great editor. Why do you need such a “feature”? It requires learning, remembering, a shortcut, configuring GUI, etc., etc. Why can’t you select a line and drag it up one line?
Even as it is, there are numerous functions people, including me, are not aware of. These forums are replete with questions about this and that and poor Yutaka has so much work just pointing people in the right direction (meaning the right menus path.)
Please do not burden EE and make it a big footprint, slow monster. We have those and I hate them!
Thumbs down, absolutely, totally!!!
In “Tools” -> “Properties for Current/All Configuration” select the “Display” tab, roll down the “Specify part” (the largest) pane and select the “Matched Parenthesis/Brackets”. Then modify the “Text color” and “Background Color” using the “custom color” choice and palette, and modify “style” (e.g. “Bold”), all to your heart contents…
(I use bold red on yellow)
Good luck!
Thanks Arthur,
OK…
Hmmm! IMHO, the most desirable functionality is a single, toggle command which can be assigned a keyboard shortcut, working on the current line if none is selected or on all selected lines is. If any of these are already commented out, uncomment it!
Toggle, because obviously if it is already commented out, why would you want to comment it out again? Also in the opposite direction.
Yes I am sure Yutaka is listening. He always does, and that is not the least reason that I am using EE :-)
Dear Arthur,
I agree with you, but when one or more lines are SELECTED, nothing happens! No commenting-out!
Is this last behavior planned? If so, what should I add to have it comment out a bunch of selected lines?
Hi!
IMHO this macro just UN-comments an already commented-out text. It didn’t comment out any un-commented one, or am I missing something?
To whoever can understand this ancient language, written in ASCII graphems:
Mit eitzes binech bazorgt shoin!
Oh my God! Yes, yes, yes!!! By all means!
It is unbelievable how much grief I suffered because I didn’t understand this feature…
May I suggest something which is somewhat related: The “Tip-of-the-Day”.
* It should be ON by default;
* It should have a check-box titled “Do not show…”;
* The Help sub-menu should have a setting “Turn ON the ‘Tip-of-the-Day'”;
* It should preferably explain tricks not that obvious;
* It should NOT duplicate help items. These are searched for anyway…
* On the release of a new version, the tips should be about the new features;I am sure that these forums provide a wealth of non-obvious usage of EE!
May I suggest:
* Always turn-on a new feature by default,
* on first usage of it, pop up a mini help window…
* … explaining what this feature is all about (may be pointing to its help topic)
* … how to turn it OFF
* … and how to turn it ON again
* … with a check-box that turns-off this mini-help window from ever popping up againPlease folks, your opinions!
How in heavens name do you wrap a view intended to represent columns???
And relating to another topic/thread, if you ever implement such a “feature”, please turn it off by default… :-)
Thank you JohnQSmith for the tip. I never bothered to try out all these myriad options and whatnot!
Hey folks, why not start a thread named “Feature-of-the-day” and invite everyone to post one or more of his/her favorite features.
Why not start with a category: “This-and-this feature is my most treasured one”…
What say you?
(I am too tired now so I’ll not start it now, but if nobody else will I’ll do it tomorrow. OK?)
Dear User,
As far as I know (and I use a LOT of TSVs) that’s the default behavior, in case ALL lines, no exception, has the same number of columns.
If it doesn’t happen with you, check that in your file this is indeed the case. May be a title line? Or a column headings one?
This whole discussion about beta versions brought to my mind a feature request.
The reason I never tested beta versions of EE was the possibility of the new version crashing when the EE was run in a different environment(s) than what Yutaka tested it on. I resent the hassle brought on by the requirement to reinstall older versions.
However, if beta versions could be installed side-by-side with the production one I would gladly test each and every one of them! The reason why I would do it dear Salabim is that this way I might prevent future hassles when I do install the so called “production” version. You see, surprise surprise, “production” versions contain bugs too :-(.
So, it is in your best interest to thoroughly test a new version in your environment!
And now for Yutaka: Is that a major change???
