It is just this problem that many a good time I cannot differentiate between the seed command and that part which shall be replaced .Is there any command which can color the seed command and the replacement ?
Of cours in Man I can look this up ,but alas it takes hours and hours and even then it may be outdated .
You need to provide more details on what you are trying to accomplish. I think you are asking about using the command line to modify some sort of text....is it file names, or the contents of a file, or something else?
There are multiple ways to modify text on the command line with some being better than others depending on the exact specific circumstances and on macOS with many very outdated & very limited options/behavior of the command line utilities it can be very tricky to get some of those options to work especially if you try looking for examples online where most will be for much newer & expanded Linux utilities.
AFAIK, there is no way to differentiate parts of a command within the Terminal, but if you are writing a script, then some text editors (BBEdit) may be aware of various shell syntax where it may highlight some portions of the command although I don't think it will highlight/differentiate the part you are concerned about. I know sometimes you can have the command line appear with various colors when typing a command or viewing the output (Linux for sure), but that needs to be configured through a shell profile. I have no idea what, if any such options are available with any of the macOS shells.
When I am experimenting & testing commands & options, I will make sure I limit myself to a test folder & test data....usually also making a copy of the data I want to actually use before I implement it on that actual real data. You may discover that your command & options may not be correct for all possible text combinations when searching & replacing text.
Make sure you have a good backup before doing any experimenting with the command line since the command line has no safety nets. It is very easy to accidentally destroy all your data with one incorrect character. In fact, you may even want to experiment within another macOS user account or on another boot drive/computer before trying the final command on your main system.
Hi,
You could use less or more command for your question.
$ kth get template folder | jq '.name="My First Folder"'
{
"name": "My First Folder"
}
This could be a simple example .
$ kth get template folder | jq ' .name= this is the seed command or what it can be now -God knows . This cannot be changed . But "My First Folder" this is not a seed command or the skeleton - this can be changed to "mycat" "mydog" or any . Then also after writing a name one has to press enter and you get that curly brackets .
So the author should explain it more clearly what is what - the seed command should be written in red and that which can be changed should be in green or telling overwrite - and then press enter. Or elaborate it more with a Cristal clear examples
The problem with these things is that commands are written haphazardly and unconsciously misleading people ,thinking some fancy ideas that they are a great philosophers - or some other ideas ,sorry but this takes hours to find out what is what .
On top of this not even the supports can help - as some admitted they cannot this things with the CLI - is this not a terrible news ?
What I mean is that the commands should be highlighted - or elaborated more extensively . What is the ground and what is above the ground .The ground we cannot change - but that which is on the ground we can change as we will .
The example helps, but I have no clue what language that is representing. It is not like any Bash command or utility that I have ever seen. It looks like part of some script or scripting language for some specific database. I've definitely never seen anything like it posted on the Apple forums before in the many years I've been reading & contributing here. Maybe another more knowledgeable contributor will see your example & understand it & provide some assistance.
If this is something you found online, then you should probably be asking someone from the site where it was posted for assistance.
Whenever you are working on the command line, it is imperative that you understand the commands you are using. This is even more important when you are using commands found online. Many times the commands you see posted may only apply to that one very specific user's exact system setup & circumstances. Yes, it may give you an idea & a clue to solve your own problem, but you still need to understand it enough to modify it.
I'm thinking this example you provided has nothing to do with the macOS command line, but some command line interface into some app or database where the rules are different. My personal experience has mainly been with the Bash shell & very limited experience with Zsh. I have used a few various programming languages over the years as well. However, I've never done any database programming & queries.
The only way you will get colored text to delineate the commands would most likely be the interface of whatever you are using to enter those commands (if they even have such an option), or a text editor like I mentioned if you are creating a script of some sort, but the editor must be aware of the language & usage to do so. I feel we are still missing critical information.
kacsavirag wrote:
???????
Your question was vague & confusing. I can see how @kaz-k concentrated on the "previewing text replacement" portion.
I see . Yes this is what is wery difficult to understand ideas .I wrote an example now .
How to preview text replacements in a command line ?