Forum Replies Created
-
Posts
-
Yutaka,
I’m afraid not. I’m not referring to a macro being added to the Macro List. I mean that when I run a macro, that macro is automatically added to the Macro’s Run command (2nd from the top; right below the Start/Stop Record menu item; EEID_QUICK_MACRO_RUN (4217)), and assigned the hot key Ctrl+Shift+P. That auto-assignment is something I’d like to selectively avoid as a significant number of macros don’t need repeating for a while after I run them, and are generally assigned their own hot key. For example, opening a defined set of files, compiling a set of files, or copying the current file to another directory for other people to use. While the auto-assignment of the just executed macro to that menu item works great for developing, when using the macro in production, it’s not as useful, and at times gets in the way.
As an aside, on my list of hoped for solutions, the script directive is looking more handy then trying to determine if the macro was run from a hot key.
Paul
Yutaka,
I understand, but I would argue effective Plugin management is a core feature. Also, there are at least 5 plugins that require a side, and only 4 sides to the editor :). While it has not yet, at some point that will become a more serious limit to EmEditor, so please leave on the list for a future version.
Thanks,
PaulI wasn’t sure if it was a bug, but that window appears to be unique in that it relates to screen position, instead of EmEditor main window. From my perspective, there is some variation in where the dialog boxes appear and I couldn’t quite figure out the logic. Search and Define Encodings appear to remember relative position from the main window, while Customize and Input/Export appear to be main window center. I didn’t find any that operated like Quick Launch, but that’s not exactly definitive.
To answer your question, yes. More accurately, I think Quick Launch should operate the same way as other dialog boxes like the Search or Find in Files.
Thanks,
PaulYutaka,
I don’t see how. The search plug in provides me the file name and line position, but that the actual text of the line. In my task, I needed to search for a certain word that was used in variety of ways, and then edit only a particular usage. Looking at the context of the usage was the only way to determine which matches where the ones I wanted. The Search plugin only gives me the filename, and I see no options to change that output.
The Find Dialog box Extract gave me the text, but not the file name. Find in Files provides both of values, and allows me to quickly scan all the possible matches, click on the ones that need changed, and go directly to that line. That is the functionality I was looking for, but Find in Files casts too broad a net. It is not possible, as far as I could see, to only look in the Open Documents.
Thanks,
PaulMeir,
I’m guessing you never opened a Visual Studio Solution? When I do that, the Project Plug-in also allows me
to- generate and view a list of symbols,
- change the default configuration of the Solution,
- change the default platform,
- Build/Clean/Rebuild the solution
- Check files in and out of Source Safe
in its Visual Studio configuration ( which is installed along side the EmEditor template – I certainly never set that up).
The plug-in itself It also lets me to create new solution templates (similar to EmEditor’s configuration) that contain tools, set up new keyboard shortcuts for that template, and set up new configurations and platforms with their own macros. There might be more, but that’s all I see on the menu.
It also has its own toolbar that allows access to all that.
That’s why I say the plug-in is more heavy weight.
Meir,
My hesitation, after playing with the workspaces and projects plug-in this morning, is the Groups integration. Groups, to me, are a way to get EmEditor to dynamically set up related files and not worry about how the file set was generated or having to save the file set. Combining the groups into the project arena may negatively affect this capability.
Combining the Project and Workspace I don’t have as much problem since I don’t use either one. I do like that workspaces are integrated into the core and appear on the tray icon menu and have their files auto-open when the workspace is open. If other open groups could be (optionally) left open when a workspace is opened then I would be far more likely to use it. Projects are too heavy weight for me, and with all the different menu options appear to be bloat if added to the core, but others may have different opinions/needs.
First, I have some sympathy for this idea.
However, I’m not certain I support moving this into the core, unless it’s the only way to make it happen. I don’t use Projects normally. In my use, EmEditor is a super powerful, hyper-fast, syntax highlighting text editor, not an IDE. The editor’s speed is the thing that keeps me coming back. When files open at the speed of thought, it’s hard to use one that makes you wait, even if for only a couple of seconds. The more built-in functionality, the slower the editor will be, and the less attractive for my usage. If the idea would work as a plug-in (and I confess that I don’t know what the limitations of a plug-in are in this area), I would prefer that.
That said, I admit to not using these features much, but I might use them if they worked better together. Having the workspace global across all open instances of EmEditor makes it not terribly useful for me, so I have to use scripts to support a similar, not as useful, functionality. Having used Atom and Visual Studio Code before dumping them in favor of EmEditor does make the concept of a Project Folder attractive, although not as the central file management feature, and I hesitate to ask for the complexity needed to make something like that optional.
Not exactly what you’re looking for, I know. But I’m not sure that merging all of those together into the core will be useful for those of us who don’t mainly use EmEditor in the “project” aspect.
On the MSDN page listed above is this:
To use the complete language feature set of version 5.8, the Windows Script interface host has to invoke IActiveScriptProperty::SetProperty.
Is this something on the drawing board? Or is it a setting already in EmEditor and I missed it?
It adds a small bar on at the top of the vertical scroll bar and on the right of the horizontal scrollbar. If you grab it with the mouse, you can slide a splitter bar down in that tab and see two views of the same document. The scrollbars must be visible.
You can edit in independent areas, the changes will be visible in both sections. It is editor-tab specific. Splitting one file in a tab has no affect on other tabs. As far as I can tell, you can not use it to see two files on the same tab – the same file is visible on each side of the split, but sometimes it really helps to be able to see two separate areas of the same file.
Other editers have similiar features. For example, MS Word (http://techwelkin.com/ms-word-how-to-split-a-document-in-two-windows), Excel, and Ultraedit.
HTH,
PaulDear Rien van Ham,
If you mean the Sticky Vertical Mode, I added the ‘sticky vertical mode’ toolbar icon to the toolbar. It’s depressed when vertical selection is enabled.
If you meant something else, sorry!
HTH
PaulGo to Tools | Plug-ins | Customize Plug-ins
On the Customize Plug-ins dialog box, select the Snippets plug-in, and then click the Properties button.
Check the Run Backgroud checkbox.
You should be all set.
The Prompt when End of Document is Reached check box was added to the Search tab of the Customize dialog box.
I was surprised to see this, as it was a minor issue and there’s a whole bunch of other stuff in this beta already.
Thanks! Works great.
Paul
On the bottom of the replace dialog box is a checkbox reading “In the Selection Only”. Is that checked?
Oops!
The last time I tried that (several years ago), I thought it just jumped to the top of the document and started down on the first call to Serach. I didn’t realize it looped.
One minor complaint is that it loops quietly and if I happen to miss the status bar message, I don’t know that.
