{"action":"created","issue":{"url":"https://api.github.com/repos/fesch/Structorizer.Desktop/issues/146","repository_url":"https://api.github.com/repos/fesch/Structorizer.Desktop","labels_url":"https://api.github.com/repos/fesch/Structorizer.Desktop/issues/146/labels{/name}","comments_url":"https://api.github.com/repos/fesch/Structorizer.Desktop/issues/146/comments","events_url":"https://api.github.com/repos/fesch/Structorizer.Desktop/issues/146/events","html_url":"https://github.com/fesch/Structorizer.Desktop/issues/146","id":145261073,"number":146,"title":"Syntax enhancement for bash scripting","user":{"login":"reks99","id":18035140,"avatar_url":"https://avatars.githubusercontent.com/u/18035140?v=3","gravatar_id":"","url":"https://api.github.com/users/reks99","html_url":"https://github.com/reks99","followers_url":"https://api.github.com/users/reks99/followers","following_url":"https://api.github.com/users/reks99/following{/other_user}","gists_url":"https://api.github.com/users/reks99/gists{/gist_id}","starred_url":"https://api.github.com/users/reks99/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/reks99/subscriptions","organizations_url":"https://api.github.com/users/reks99/orgs","repos_url":"https://api.github.com/users/reks99/repos","events_url":"https://api.github.com/users/reks99/events{/privacy}","received_events_url":"https://api.github.com/users/reks99/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/fesch/Structorizer.Desktop/labels/wontfix","name":"wontfix","color":"ffffff"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-04-01T19:10:33Z","updated_at":"2016-04-02T10:57:43Z","closed_at":null,"body":"Hi.\r\n\r\nI see the problem to detect uninitalised variables or shell commands. So I propose a possible syntax where the executer and the code generater can detect, that it is a shell command.\r\nA command line may look like: \r\n_returncode <- command({list of options and parameter})_\r\n\r\nSo like a function call in a computer language the command is marked with parentheses to be executable or external. The enclosed comma separated list of options and/or parameters should be surrounded by curly brackets. This make it detectable as a bash construct - which can be ignored by the executer. Function calls of a computer language have the parameter not surrounded by curly brackets.\r\nExample **ret := ls({-1, *})** or **cp({-p, a, b, 2>/dev/null})**\r\nBecause the parentheses surounds the complet set of options and parameters another command can follow as in a pipe.\r\nExample: **ls({*}) | sort({})** where as a parentheses only can be followed by | or || or &&. A semicolon is not allowed because an independend command should go in a new instuction field. If a command should go in background it should be coded in the parallel nsd element.\r\n\r\nHope this helps to better detect the elements for bash scripts and at least get a better code exported\r\nFine regards\r\nRolf"},"comment":{"url":"https://api.github.com/repos/fesch/Structorizer.Desktop/issues/comments/204694347","html_url":"https://github.com/fesch/Structorizer.Desktop/issues/146#issuecomment-204694347","issue_url":"https://api.github.com/repos/fesch/Structorizer.Desktop/issues/146","id":204694347,"user":{"login":"reks99","id":18035140,"avatar_url":"https://avatars.githubusercontent.com/u/18035140?v=3","gravatar_id":"","url":"https://api.github.com/users/reks99","html_url":"https://github.com/reks99","followers_url":"https://api.github.com/users/reks99/followers","following_url":"https://api.github.com/users/reks99/following{/other_user}","gists_url":"https://api.github.com/users/reks99/gists{/gist_id}","starred_url":"https://api.github.com/users/reks99/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/reks99/subscriptions","organizations_url":"https://api.github.com/users/reks99/orgs","repos_url":"https://api.github.com/users/reks99/repos","events_url":"https://api.github.com/users/reks99/events{/privacy}","received_events_url":"https://api.github.com/users/reks99/received_events","type":"User","site_admin":false},"created_at":"2016-04-02T10:57:43Z","updated_at":"2016-04-02T10:57:43Z","body":"@codemanyak Hi Kay.\r\n\r\nFirst of all many thanks to the new version, it is great!\r\nI see the differences. For me structorizer is a development tool, so I don't need the executer. If the exported programm has a correct structur and some goodies (like variable initialising or detecting) its good. \r\nYou have a more generally view focused on testing algorithms for example with the executer.\r\nPossibly only separate parser (not only for the bash) can solve the export problem.\r\n\r\nFine regards.\r\nRolf"}}