Output #<Command> in Copy Cheat Sheat

[ugus]

Can you make it possible to get
the #<Command> as well when performing
Options | Copy Cheat Sheat in Customize Keyboard Shortcuts
dialog.

or have I missed something...

[admin]

Can you make it possible to get
the #<Command> as well when performing
Options | Copy Cheat Sheat in Customize Keyboard Shortcuts
dialog.

or have I missed something...

Yes, this wish is currently accumulating... In what format? Should I attach it to the Command caption in brackets like:

Edit / Cut [#200] Ctrl+X

?

[ugus]

Can you make it possible to get
the #<Command> as well when performing
Options | Copy Cheat Sheat in Customize Keyboard Shortcuts
dialog.

or have I missed something...

Yes, this wish is currently accumulating... In what format? Should I attach it to the Command caption in brackets like:

Edit / Cut [#200] Ctrl+X

?

I think putting a tab between the command caption and #<Command> will do best, (if you want to import it into Excel or similar...)

[jacky]

I think putting a tab between the command caption and #<Command> will do best, (if you want to import it into Excel or similar...)

Yes, a new "column" would definitely be the way to go IMO

[ugus]

+ CKS | Options button context menu: added toggle command "Include
Command IDs".

Super, that was fast!

[infimum]

Is the character "|" or "#" used in the context menu? It's not showing up correctly in my environment Only that character is displayed messed up.

[admin]

Is the character "|" or "#" used in the context menu? It's not showing up correctly in my environment Only that character is displayed messed up.

No, only "/" (forward slash) and "»" (french open quote?).

[j_c_hallgren]

I think putting a tab between the command caption and #<Command> will do best, (if you want to import it into Excel or similar...)

Yes, a new "column" would definitely be the way to go IMO

A new column is what I'd suggested in the other thread at http://www.xyplorer.com/xyfc/viewtopic.php?t=2082
That would lend itself to Excel and such...

Update: This post was for benefit of ugus and others, as Don already knew about it

[admin]

I think putting a tab between the command caption and #<Command> will do best, (if you want to import it into Excel or similar...)

Yes, a new "column" would definitely be the way to go IMO

A new column is what I'd suggested in the other thread at http://www.xyplorer.com/xyfc/viewtopic.php?t=2082
That would lend itself to Excel and such...

I've heard you, but the implications are many... still in pre-decision mode...

Hint: the call by ID scripting is considered absolute hardcore by me, and I'm hesitating to make it too visible. It's just too dangerous for newbies.

[j_c_hallgren]

Hint: the call by ID scripting is considered absolute hardcore by me, and I'm hesitating to make it too visible. It's just too dangerous for newbies.

I don't disagree with that...just that for us who can use it, having it visible is very valuable...so if this display needs to be triggered and set on thereafter via INI tweak, or some other similar less visible method, I'd be happy with that!

Maybe within 'Options' on CKS panel as done would ok...I'd have it at the Option level though...and that should then also cause display within CKS itself as 3rd col, and unless done, even the existing single CID display wouldn't be visible...but this setting should be retained in INI, for sure!

[admin]

Hint: the call by ID scripting is considered absolute hardcore by me, and I'm hesitating to make it too visible. It's just too dangerous for newbies.

I don't disagree with that...just that for us who can use it, having it visible is very valuable...so if this display needs to be triggered and set on thereafter via INI tweak, or some other similar less visible method, I'd be happy with that!

Maybe within 'Options' on CKS panel as done would ok...I'd have it at the Option level though...and that should then also cause display within CKS itself as 3rd col, and unless done, even the existing single CID display wouldn't be visible...but this setting should be retained in INI, for sure!

I won't add a 3rd col without adding column headers. But I have currently no time to add column headers to my little list. You should see my desktop...

[j_c_hallgren]

I won't add a 3rd col without adding column headers. But I have currently no time to add column headers to my little list. You should see my desktop...

AFAIK, the existing columns don't have headers either, right?
...and we who would use it certainly don't need a heading! We just need those magic nbrs!

BTW, the existing "Command #xxxx" above Desc would thus be a column 'title', but as a footnote!

[infimum]

No, only "/" (forward slash) and "»" (french open quote?).

OK, "»" isn't displayed correctly in my environment.

[admin]

No, only "/" (forward slash) and "»" (french open quote?).

OK, "»" isn't displayed correctly in my environment.

So I guess I better take my hands off all upper ASCII chars...pity! I will use comma or semicolon instead...

[infimum]

So I guess I better take my hands off all upper ASCII chars...pity! I will use comma or semicolon instead...

Or full-fledged unicode support