Forum Replies Created
- Posts
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?
Because the code I’m editing already has comments that I want to keep. For example,
...
for(int i=0;i<10;i++) {
// the following line prints incremented variable
printf("\%d",i);
}
...Using your idea, if I wanted to comment out that loop, I’d end up with
...
//for(int i=0;i<10;i++) {
the following line prints incremented variable
// printf("\%d",i);
//}
...which would be wrong. :-(
If I comment out that block, it should add additional comments on previously commented lines like
...
//for(int i=0;i<10;i++) {
//// the following line prints incremented variable
// printf("\%d",i);
//}
...that way when I later uncomment it, it will be back the way it was when I started.
Actually, never mind.
I found out that the other editors I use have the same functionality. The difference was that I had tab indenting turned on in them whereas I was using space indenting in EmEditor.
Thanks for a great product.
Skinning is when you change the look of an application by applying different icons for buttons or the color of bars or gradients to the menus. That kind of thing. Like in Windows XP, you can change the color scheme and the style of the windows and buttons to make it look like XP with the rounded edges or like Win2k with the more blocky look. Basically so the user can tweak it to look different.
If you decide to implement something like this, it should be put way down at the bottom of the list of things to do since it’s just eye candy. Any usability and functionality enhancements should be given top priority.
Yutaka,
The macro buttons will work great. I pulled up the Macro Reference and also found the #title directive so I can show the icon without the name of the macro.
A suggestion for a future version might be to allow “skinning” EmEditor.
JohnQSmith
“Current line” highlight already exists and can be set on the Display tab of Configuration properties.
Since you’re keeping the first one and then appending the others separated by “-“, just replace all “t” with “-“.
Update. Problem is not with Chrome. The problem is with the way the NEWBB module for XOOPS is storing the viewed topics. Viewed topics are stored at the client in a cookie called “newbb_topics_viewed”. After viewing a lot of topics, the cookie reaches maximum size and can’t store any more history.
Edit: I ran the cookie test at http://myownplayground.atspace.com/cookietest.html and these are the results for Google Chrome 18.0.1025.142.
12:24:7.64: Starting
12:24:7.316: Max Cookies with Character Length 3 and character “1”: 180
12:24:9.488: Max Cookie Character Length using character “1”: 4096
12:24:14.238: Max Cookies with Character Length 4096 and character “1”: 180
12:24:15.222: Max Cookie Character Length using character “ÿ”: 2049
12:24:18.878: Max Cookies with Character Length 2049 and character “ÿ”: 180
12:24:18.972: Guessing Max Cookie Count Per Domain: 180
12:24:18.972: Guessing Max Cookie Size Per Cookie: 4096 bytes
12:24:18.972: Guessing Max Cookie Size Per Domain: NAResults for Mozilla Firefox 11.0
12:27:33.584: Starting
12:27:33.695: Max Cookies with Character Length 3 and character “1”: 150
12:27:34.560: Max Cookie Character Length using character “1”: 4097
12:27:35.255: Max Cookies with Character Length 4097 and character “1”: 150
12:27:36.248: Max Cookie Character Length using character “ÿ”: 4097
12:27:36.927: Max Cookies with Character Length 4097 and character “ÿ”: 150
12:27:37.39: Guessing Max Cookie Count Per Domain: 150
12:27:37.39: Guessing Max Cookie Size Per Cookie: 4097 characters
12:27:37.39: Guessing Max Cookie Size Per Domain: NAMy understanding right now:
You have to set up the FIND RegEx with an alternation so that it has both a success and a failure point.
As the REPLACE have too possibilities too: (?n:true_expression:false_expression)Absolutely correct. I like your FIND RegEx better. It will be much easier to use than mine. Just adding the zero or more switch makes it much simpler than a non-matching alternation grouping.
What helped me the most in figuring out how it works was how EmEditor highlights all matches when you do a search. When I tried your first search, only the first “Test Price” line was highlighted, but when I removed the final “(d)”, all the lines were marked. This showed me that the problem was with the RegEx.
The first and foremost thing to remember is that the WHOLE RegEx expression must match before you can do any further matching and testing with a SUBexpression.
BTW, good idea :lol: of you:
Replace: (?4:too expensive:affordable)Thanks! :-D
I see the problem with both of your tests. It’s the same thing that took me so long to figure out how it works.
Here’s the key…
The whole RegEx must match in order for it to work. In other words, you have to set up the RegEx with an alternation so that it has both a success and a failure point.In your first test, only the first line matched your RegEx (I’m using underscores as filler to demonstrate).
Test Price 100______0
(.+) (.+) (d{3}) (d) <-- this matches
Test Price 100________
(.+) (.+) (d{3}) (d) <-- this doesn't match, there is no final (d)
Test Price 800________
(.+) (.+) (d{3}) (d) <-- also doesn't match
Here’s how I changed your RegEx to work.
Note the success ----. and failure points
| |
v v
Find: ^(.+) (.+) (d{3})(?:(d)|$)
Replace: (?4:too expensive:affordable)Your second example is the same thing.
Color_ 1__ green
(Color d) (.+) <-- match
Color_ 2__ blue
(Color d) (.+) <-- match
Color_ 3__ red
(Color d) (.+) <-- match
The available colors are either green, blue or red.
(Color d) (.+) <-- no match anywhere on line
Hope this helps.
I played with it a while and finally figured it out. Here’s an example.
Input document
TheGreenAile TheGreenBile TheGreenCile TheGreenDile
TheGreenEile TheGreenFile TheGreenGile TheGreenHile
TheGreenIile TheGreenJile TheGreenKile TheGreenLile
TheGreenNile TheGreenOile TheGreenPile TheGreenQile
TheGreenRile TheGreenSile TheGreenUile TheGreenVile
TheGreenWile TheGreenXile TheGreenYile TheGreenZile
Search string
(?:([BFNPR])|([^BFNPR]))(ile)
Replace string
(?1:M:T)3
Replace all and output is
TheGreenTile TheGreenMile TheGreenTile TheGreenTile
TheGreenTile TheGreenMile TheGreenTile TheGreenTile
TheGreenTile TheGreenTile TheGreenTile TheGreenTile
TheGreenMile TheGreenTile TheGreenMile TheGreenTile
TheGreenMile TheGreenTile TheGreenTile TheGreenTile
TheGreenTile TheGreenTile TheGreenTile TheGreenTileI color coded it to help you see what’s happening.
Oh yeah, the Boost regex docs helped me figure it out.
