Notepad mode | independent settings | MultiUser mode

[Stefan]

I want to use HippoEDIT as notepad replacement (sometimes)
 f.ex. to open quickly an file when i need more features then notepad provide

But my main HippoEDIT config is set up with more options then i need for an notepad replacement.


So i create an new workspace Notepad.hewsp
and launch HippoEDIT with command line arguments  as an notepad replacement.

e:\a\HippoEDIT\HippoEdit.exe --new-instance --portable --no-recent --workspace Notepad --config e:\a\HippoEDIT\dat2\


Here i have two questions/suggestions:

1.)  --config   expects to have an full data -folder with all syntax files.
But  i want only  an own "HippoEdit.config"  and  "settings.xml"
to costumize my HippoEDIT as i like it.
The syntax files  HAVE to be the same as i would start HippoEDIT normal.

So i want f.ex. to close file explorer and bookmark pane for my notepad replacement.
How can i do this?
Can there be an option like --settings C:\notepad.xml ?

2.)  maybe there could be an default --notepad switch  which do this all above for the user?
HippoEDIT.exe --notepad %1


I don't know if i could make myself clear?


EDIT:
another try to make myself clear.

I want to run HippoEDIT with independent workspace and settings.
--workspace Notepad     is OK, i think.
--config e:\a\HippoEDIT\dat2\    is to much for my need
--settings second.xml   is what i expect  (analog zu 'workspace'  without path)

I want to share my syntax files,
but i want to customize the view/pane  settings
i want different recent files list, search history and like this.

I want to have ONE HippoEDIT main folder, but start HE with different settings.
(maybe this is multi user mode too?   --settings %userProfil%\user.xml)

[alex]

Hello Stefan,

ok. more or less clear but do not think that this would be easy to implement for me...
So, mostly you need also "workspace" dependent settings for text editor, which are stored in settings.xml.
hippoedit.config is application oriented settings, which should be same for all instances, I have moved all that user would like to change to workspace.

But different settings.xml is chnages in core functions and for this HE is not prepared I would think about this (same problem as reloading of the synatx after synatx file change) and maybe this would come some when

Best regards,
Alex.

[Stefan]

Sorry, i didn't have thought that is that work intensive.

> "workspace" dependent settings
Not really, because we want different workspaces with same settings, i think, too.
I think i suggest different settings.xml to chose from, like we have different workspaces right now.
But without menu-item, command line switch would be enough.

[alex]

What I meant under workspace dependent is that in settings of the workspace you can select which settings file to use.
Something like this. But in both cases it is really big efforts (and I do not know which new bugs it can create).
I would think about it, but probably would give priority to more required function as Scripting and plugins, for now. But if I would do some redesign in settings handling I would keep your suggestion in mind

Best regards,
Alex.

[Scott Bilas]

Just a quick note about sharing syntax files: you could use junction points for this. Selectively map folders over that you want to share, such as data\syntax or data\colors.