** Changed in: chromium-browser (Ubuntu)
Assignee: Chad Miller (cmiller) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514484
Title:
Chromium start-up script doesn't accept
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514484
Title:
Chromium start-up script doesn't accept argument values with
Space characters in chromium flags seem to be always parsed even if
they are escaped. (Of course, it must be a bug.)
When splitting all flags in $CHROMIUM_FLAGS by newline and running chromium
after IFS=$'\n' , it works.
(And do not escape spaces. like --user-agent=foo bar , not
Uh, I've tried that, but it keeps splitting the argument values no
matter how many slashes I add (they end up interpreted as part of the
URL -- for instance, instead of "B" chromium gives me "B/" in the
address bar). I've been trying to understand what bash is doing, but
it's really eluding me.
I agree that it's tricky.
The two solutions I can think of is your idea of an array, and assumption
that the variable should go through two levels of interpretation.
The way that makes current scripts and files still work is the latter. It
would go like this:
If there is a special character in
I noticed that last night =( so sad how often I seem to be surprised by
how shell expansion works.
Best I could come up with was transform CHROMIUM_FLAGS into an array and
use "${CHROMIUM_FLAGS[@]}" in the calls instead. Sorry for the failed
patch attempt.
--
You received this bug notification
The attachment "Patch adding quotes to /usr/bin/chromium-browser" seems
to be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
I don' think this patch does what you expect.
Try with more than one value in the variable.
CHROMIUM_FLAGS='--user-data-dir=/tmp/cr --user-agent="A B C"'
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Chad Miller (cmiller)
** Changed in: chromium-browser (Ubuntu)