ENG: Small talk / Geplauder / Forum Moderation / Spam-Report / Off-Topic

[Fla$her]

2Horst.Epp
And what is there to understand? Updating the help doesn't depend on the testing stage in any way, especially considering how long this stage lasts.
I don't need to believe in the obvious. Who reads what there has nothing to do with the case. I asked about the author's approach, not your personal opinion. I suggest that we end here, especially since the answers in the form of overquoting are only annoying...

[tuska]

Below are help pages recently announced (Point 1.-5.) by the author on the 'Everything' forum:

1. Options
2. Everything 1.4 advanced settings
3. Everything 1.5 new advanced settings
4. Everything 1.5 help (F1 in Everything)
5. about:config - "... show all settings in your text editor"
6. Everything 1.4 User Guide / Manual as HTML/PDF -
   The current plan is to do the same for Everything 1.5."

But I don't want to discuss this topic...

[white]

Moderator message from: white » 2024-07-22, 22:37 UTC

Moved previous 7 off-topic posts from this location.

[Fla$her]

I searched a bit in Help and couldn't find anything

See the bottom of the page Dialog box: Choose command

Code: Select all

hh.exe %COMMANDER_PATH%\TOTALCMD.CHM::dlg_choosecommand.htm

The following internal commands support 3 states: 0 or no parameter=toggle, 1=set, -1 or 2=reset.
...
cm_SyncChangeDir

Why not also have a command-line switch to turn on cm_SyncChangeDir?

cm_SyncChangeDir 1 - set
cm_SyncChangeDir 2 - reset

[Hacker]

Fla$her,
The request was about command-line parameters.

Roman

[Fla$her]

2Hacker
Aren't 0/1/2 command-line parameters?

[Hacker]

Fla$her,
Of Total Commander? No. I think the request is about what can be found in Help 4.a).

Roman

[Fla$her]

Of Total Commander? No.

Are you serious?

I think the request is about what can be found in Help 4.a).

What is 4.a?

[Hacker]

Fla$her,

What is 4.a?

It's the section of Total Commander's help describing TC's command line parameters.

Roman

[Fla$her]

2Hacker
And where is "4.a"? In short, I don't see a connection between the topic title and this page. The command line is part of the TC interface. See "User interface" in the Help.

Here the author created a topic of the same name, but there it was about TC launch.

[wanderer]

2Hacker
And where is "4.a"? In short, I don't see a connection between the topic title and this page. The command line is part of the TC interface. See "User interface" in the Help.

Here the author created a topic of the same name, but there it was about TC launch.

Well, i can understand the confusion after checking section 3a of help. Fla$her understandably points that out, but indeed Hacker got what i was talking about, which was section 4.a of help, "command line parameters".

Didn't cross my mind at all that this could be confusing. I've changed the title of the thread and the OP to be more precise. Also, i didn't remember i had requested this again in the past. In any case, i still hope it can be implemented in TC.

[AntonyD]

I think it would be more convenient to use the "command prompt" for the built-in 'editbox' that supports typing and executing printed commands.
And the "command line" for the way how Total interacts with the operating system and other programs.
it's there - how are external parameters transferred to the Total, how are some of its internal tools called, etc.

[wanderer]

I think it would be more convenient to use the "command prompt" for the built-in 'editbox' that supports typing and executing printed commands.
And the "command line" for the way how Total interacts with the operating system and other programs.

Well, it's an idea. It would certainly make things more clear. In almost all cases, "command line" are the parameters you pass in an executable when you run it, so using it with a different meaning in TC, creates confusion...

[Fla$her]

In almost all cases, "command line" are the parameters you pass in an executable when you run it

In what kind of "almost all"? I see the exact opposite picture.
The problem of naming this topic is not so much in the command line as in specifying an internal command that has nothing to do with exe.
There is no ambiguity in such a title: TOTALCMD.EXE parameter for disabling synchronous directory change

Also, i didn't remember i had requested this again in the past.

Getting rid of crossposting is the task of moderators.

In any case, i still hope it can be implemented in TC.

Instead of hoping, you could have used the solution I suggested for a whole year.

[wanderer]

In what kind of "almost all"? I see the exact opposite picture.

If you post in a support forum of any application something about "command line", almost everybody will understand you are talking about parameters passed to an executable file. This is what i mean by "almost all". There may be some cases (like TC) in which this may mean something else but in general, it means "parameters passed when executing a file".

Instead of hoping, you could have used the solution I suggested for a whole year.

Well, that's true but i'm not 18 any more, so sometimes it may not be that easy to try such workarounds (no time, too much pressure @ work or a few other reasons). I do appreciate the proposed solutions and the time others spend to post them, but i'm at an age in which i expect some things to just work in a simple and built-in way to the tools i use. Thanks for it, i'll try to check your proposal but it's not a real solution to me, it's just a workaround, since i will have to use yet another plugin and spend more time implementing it to some additional machines i use.