comparison: pidgin/gtknotify.c
pidgin/gtknotify.c
- branch
- uri-escape-unit-test-2
- changeset 38737
- d85c241e3183
- parent 38722
- ff057bdbe66e
- child 38748
- 17f8a2a8ccba
- child 38789
- ad3e9caa955b
equal
deleted
inserted
replaced
| 38730:859b15b1c817 | 38737:d85c241e3183 |
|---|---|
| 1282 int place; | 1282 int place; |
| 1283 gchar *uri_escaped, *uri_custom = NULL; | 1283 gchar *uri_escaped, *uri_custom = NULL; |
| 1284 GSList *argv = NULL, *argv_remote = NULL; | 1284 GSList *argv = NULL, *argv_remote = NULL; |
| 1285 gchar **usercmd_argv = NULL; | 1285 gchar **usercmd_argv = NULL; |
| 1286 | 1286 |
| 1287 /* Replace some special characters like $ with their percent-encoded | 1287 uri_escaped = purple_uri_escape_for_open(uri); |
| 1288 value. This shouldn't be necessary because we shell-escape the entire | |
| 1289 arg before exec'ing the browser, however, we had a report that a URL | |
| 1290 containing $(xterm) was causing xterm to start on his system. This is | |
| 1291 obviously a bug on his system, but it's pretty easy for us to protect | |
| 1292 against it. */ | |
| 1293 uri_escaped = g_uri_escape_string(uri, "[]:;/%#,+?=&@", FALSE); | |
| 1294 | 1288 |
| 1295 web_browser = purple_prefs_get_string(PIDGIN_PREFS_ROOT | 1289 web_browser = purple_prefs_get_string(PIDGIN_PREFS_ROOT |
| 1296 "/browsers/browser"); | 1290 "/browsers/browser"); |
| 1297 place = purple_prefs_get_int(PIDGIN_PREFS_ROOT "/browsers/place"); | 1291 place = purple_prefs_get_int(PIDGIN_PREFS_ROOT "/browsers/place"); |
| 1298 | 1292 |
