ConEmu opens always original process - problem with wrapping

[trzecieu]

Hi!
I would like to ask about 8c4dbfa (perhaps some other form v15.07.16...master )
After this version in task bar I see always origin process of conemu instead process of Cmder (I use this wrapper in day by day work )

I believe that fighting with software like cmder is not accurate because everybody knows that conemu is the main application thus I believe that it was not your intention.

Will it be possible to make software like cmder work with conemu like it used to worked?

[Maximus5]

1. Your question is not clear. Without exact explanation of your problem (with screenshots most probably) nobody can answer you.
2. ConEmu do not fight with cmder at all.

[trzecieu]

Steps to reproduce:

• download cmder (portable version: https://github.com/bliker/cmder/releases/tag/v1.2 / cmder.7z)
• unpack to some folder
• pin to taskbar by moving Cmder.exe onto window start bar
• run (by click on pinned link, or directly on program. Do not do auto update.
• // everything is OK, only one icon of cmder / conemu is available
• replace content of folder vendor/conemu-maximus5 with conemu at least 150716
• run cmder by click on created link, or directly
• in taskbar you will see two icons. One belongs to cmder link, other is conemu process (with icon of cmder). Pinning newly created icon to taskbar will create direct link to conemu.exe.

Before 150716:
(conemu process will be under cmder icon)

After 150716:
(conemu will create new process (icon on taskbar) not related with cmder)

Hopefully this explains a little bit problem.

[Maximus5]

That is because of weird architecture selected by cmder. WHY it stores xml file in place which ConEmu do not support by default? I have no idea. Ask cmder author to eliminate -loadcfgfile switch. It's not a ConEmu problem!

And obviously, mentioned commit does not relate to your problem at all.

[trzecieu]

I see, sorry for confusing. I investigated problem first and I found that problem exists only with specific version of conemu. That's why I deduced it could be new (unwanted) behaviour.

[Maximus5]

BTW, you aren't right saying "everybody knows that ConEmu is main application".
In fact, there are reports that user realizes this fact only when they accidentally execute ConEmu.exe itself.

Anyway, regardless of some displeasure of hiding ConEmu name and icon (yep, I'm aware of forks and derivatives, and they are not restricted by license), ConEmu has nothing in its code to fight with cmder. On the other hand, I'm not going to provide additional code to support cmder, because all required abilities are implemented already.

[trzecieu]

I understand perfectly you statement. You did amazing job for conemu and I appreciate this. Thank you for clarification.

[Maximus5]

Few more statements.

1. Placing xml file in the unusual location restricts or limits users from
   • using "ConEmu here" feature;
   • using "DefTerm" feature.
2. cmder.exe (at least last time I checked it) do not pass rest of command line to ConEmu.exe. This restricts users from running some specific command at once.

I believe that has to be fixed, don't you?

[Stanzilla]

What would be the correct way to ship a config file then? Replace the xml in the vendor dir probably?

[Maximus5]

All in docs: https://conemu.github.io/en/ConEmuXml.html#search-sequence

[Stanzilla]

Ok but you said -loadcfgfile is a problem, yet the docs say it's fine?

[Maximus5]

It's fine. Really. Unless you start ConEmu from wrapper pinned to TaskBar.
What? ConEmu must not know anything about them.
And they still may be used if you pin proper shortcut. So that is not an issue at all.

[Stanzilla]

I guess the problem is that people pin the cmder launcher then?

[Maximus5]

Certanly. But ConEmu docs do not promote third-party bundles, at least yet. That's why there are no warnings about cmder.