clicompanion-devs team mailing list archive

[David Caro <783900@xxxxxxxxxxxxxxxxxx>]

Yes, it's the same problem, now marked as duplicate, maybe we should use
the user input field as the tag to replace?

For example:
command: ls -l filename
User Input: filename

So when executing the command filename gets replaced by the user input
filename. So the User Input field now is used as a parameter
specification instead of being a description.

Or maybe using user input column like this:
User Input: filename1: name of the first file, filename2: name of the second file

using a comma separated, semicolon separated tag: description tuples.
(It's just a first approach).

This way we could also replace only the first occurrence of the key, so:

command: cat filename > filename
user input: filename: origin file, filename: destination file

can reuse the key words. That will make impossible to reuse the same
keyword (like in sed -e 's/s_tosearch/prefix-s_tochange/g' filename), so
maybe it isn't such a good idea.

-- 
You received this bug notification because you are a member of CLI
Companion Development Team, which is subscribed to CLI Companion.
https://bugs.launchpad.net/bugs/783900

Title:
  no backslash as first letter of an entry

Status in CLI Companion:
  Incomplete

Bug description:
  As far as I see, inputs into the variable-?-template should not start with a backslash, which might be possible e.g. when it is asked for a path. 
  This is because in python and in  '\n' the escape function of the backslash affects even a backslash itself and deletes it.

  If I am right - and i am not quite sure of it - this should be at
  least be in the documentation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/clicompanion/+bug/783900/+subscriptions