| === anthonyf is now known as Guest70961 | ||
| === sidi is now known as Guest51001 | ||
| === mthaddon` is now known as mthaddon | ||
| === sidi is now known as Guest47548 | ||
| === ciampix_away is now known as ciampix | ||
| throstur | what's the proper way to escape " inside comments in bzr commits? | 09:38 |
|---|---|---|
| throstur | is it just a standard '\'? bzr commit -m "did \"this\" thing" | 09:39 |
| vila | throstur: it depends on your shell, bzr doesn't care, it only receives a string without the quotes | 09:46 |
| throstur | thanks vila, I'll play it safe and sanitize by replacing double quotes with singles then | 09:59 |
| vila | throstur: right, I do the same when I face the issue ;) | 10:00 |
| throstur | :) | 10:00 |
| fullermd_ | You can probably use 'echo' for quick tests. | 10:41 |
| === anthonyf is now known as Guest35024 | ||
| throstur | fullermd_: I don't know anything about the shell of the invoker | 10:45 |
| throstur | (I'm integrating bzr command lines into another tool) | 10:46 |
| fullermd_ | Well, I'd expect that tool to be exec'ing bzr directly, rather than via a shell ('cuz that's Stupid And Evil), so you wouldn't really have any quoting worries anyway. | 10:47 |
| fullermd_ | As an alternate, does -F take '-' and read from stdin? And if not, why the heck not? | 10:47 |
| fullermd_ | If you're going through a shell from arbirary input, you're gonna have all sorts of escaping problems. | 10:48 |
| === fullermd_ is now known as fullermd | ||
| === sidi is now known as Guest53135 | ||
| === sidi_ is now known as Guest55217 | ||
| === sidi is now known as Guest78284 | ||
| === sidi_ is now known as Guest57893 | ||
| === sidi is now known as Guest22933 | ||
| === sidi_ is now known as Guest73040 | ||
| === anthonyf is now known as Guest16072 | ||
| === anthonyf is now known as Guest26733 | ||
| === elmo_ is now known as elmo | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!