You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can generated with find()->file()->ext(['mp3', 'flac'])->print()
In this way Amber can generate a command that works like everywhere (some GNU commands on OSX are different like sed) and the user write more amber then bash, otherwise there is no useful reason to use Amber.
I can call it like a ORM or CliRM.
The text was updated successfully, but these errors were encountered:
So you propose to create a query parser inside of Amber? I think we could implement macros to Amber so this would be easily programmable. We could also create the whole query language as well but I'm not sure if that's a good idea since it's better to give the programmer building blocks and let them build a library that can do some ORM-like queries as a separate project.
Probably can simplified with some functions to avoid to repeat them but bash scripts are full of this commands so a way to write more easily is not bad.
User can create kind of libraries as wrapper to most common commands and many of them can be shipped by Amber natively.
As example ffmpeg, youtube-dl or find to be able to generate commands automatically without using pure Bash.
An example:
find "$1" -type f ( -iname *.mp3 -o -iname *.flac ) -print0
This can generated with
find()->file()->ext(['mp3', 'flac'])->print()
In this way Amber can generate a command that works like everywhere (some GNU commands on OSX are different like
sed
) and the user write more amber then bash, otherwise there is no useful reason to use Amber.I can call it like a ORM or CliRM.
The text was updated successfully, but these errors were encountered: