| Commit message (Collapse) | Author | Age |
| |
|
|\ |
|
| | |
|
| |\
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
| |\
| |/
|/| |
|
| | |
|
| |\
| |/
|/| |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Clarification about race conditions and Uzbl object
Change get <key> to print @<key> and remove TODO
|
| | | |
|
| |\ \ |
|
| | | |\
| |_|_|/
|/| | | |
|
| | | |
| | | |
| | | |
| | | | |
fixes FS#35
|
| | | |
| | | |
| | | |
| | | | |
fixes FS#44
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Additionally when XDA_DATA_HOME doesn't exist the cookie jar location
defaults to os.environ["HOME"] + '.local/share/uzbl/cookies.txt'
however when these strings are concatenated they are missing the path
seperator '/'. Problem solved by using the builtin os.path.join to join
the environ path and jar location.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Additionally when XDA_DATA_HOME doesn't exist the cookie jar location
defaults to os.environ["HOME"] + '.local/share/uzbl/cookies.txt'
however when these strings are concatenated they are missing the path
seperator '/'. Problem solved by using the builtin os.path.join to join the
environ path and jar location.
On branch experimental:
Changes to be committed:
modified: examples/data/uzbl/scripts/cookies.py
|
| | | | |
|
| | |\ \
| |_|/ /
|/| | | |
|
| | | |
| | | |
| | | |
| | | | |
This reverts commit dca2cb9ef9566618cf7c0ee16cdbe97b9034039f.
|
| | | | |
|
| | | | |
|
| | | | |
|
|/ / / |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
This reverts commit 97526404f52875d82d584f18420be72fdc300d93.
|
| | |
| | |
| | |
| | | |
This reverts commit ed39cbe56f8923407604a1306a179529521ecd26.
|
| |\ \
| |/ /
|/| |
| | |
| | | |
Conflicts solved:
uzbl.c
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |\
| | |/
| |/| |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Both "js" and "script" commands use eval_js(), which creates an instance
of the Uzbl object class (created by js_init()) which right now provides
only a run() method (handled by js_run_command()). After evaluating the
code, eval_js() removes the object so the scripts from the loaded page
can't access it.
eval_js() supports returning a string result, and you can use it with
uzblctrl to query the DOM. Uzbl.run() also returns a string, but the
only useful thing you can do right now with that is to print @uri or
other variables.
|
| | | |
|
| | | |
|
| | |\
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
That means, read config from stdin. So stdin is always disabled, except
when you tell uzbl to read from there. The default one in the xdg config
path is still loaded.
Fixes problems when sending uzbl to background.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also: Changed a few g_error to g_warning to avoid crashes on broken
socket. Flush the channel after sending, shutdown before closing.
Removed unused headers from uzblctrl.c.
The socket protocol is straightforward: you send a command terminated
with a newline, you receive a reply terminated with a newline.
If you ever need newlines inside a reply, you'll have to change this.
uzblctrl closes the connection after getting the reply, but any other
client can stay connected and send/receive other commands.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows socket (and stdio) to have a way to reply back.
Had to change all their function definitions, unfortunately.
Currently, no functions write a result. print will, at least, probably
run_js too, and some others.
When a function calling parse_command (or parse_cmd_line) is not
interested in the result, it is safe to pass NULL. Before calling the
function, parse_command creates a GString and prints the result to
stdout if verbose is enabled. You could do the same when calling most
command functions directly, but not with those that expect a GString.
Oh, additionally, I killed NOSPLIT, moved the typedef Command to uzbl.h,
and created the struct CommandInfo which replaces a Command[2] array.
That fixes FS#22, which is a warning with -pedantic. Heh.
|