Overview
| Comment: | nitpick | 
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive | 
| Timelines: | family | ancestors | descendants | both | trunk | 
| Files: | files | file ages | folders | 
| SHA3-256: | 
2a975fabe319040a3d57fe1bcc03f728 | 
| User & Date: | lexi on 2019-11-05 16:27:52 | 
| Other Links: | manifest | tags | 
Context
| 
   2019-11-05 
 | ||
| 16:41 | update readme with reference to newer projects check-in: 05677edf7f user: lexi tags: trunk | |
| 16:27 | nitpick check-in: 2a975fabe3 user: lexi tags: trunk | |
| 16:14 | add newtab check-in: 6b40270f28 user: lexi tags: trunk | |
Changes
Modified newtab.c from [bf8e7ec053] to [2cfcd5a554].
11 12 13 14 15 16 17 18 19 20 21 22 23 24 25  | 
* running and i just want a new goddamn tab. it * turns out, qutebrowser publishes an inane IPC * mechanism, in which JSON (i know!!) written to a * unix domain socket (I KNOW) can send signals to * a running qutebrowser process. newtab checks if * there's a running qutebrowser process and sends * the appropriate IPC signal if so. otherwise, it * execs a new qutebrowser instance. * * it takes a single argument, the URI of a page to * navigate to. if launched without an argument, * newtab simply opens a blank new tab. simple * enough, right? but why write it in C? to talk to * a goddammned python application, of all things? * well, i was originally going to do this in a  | 
| >  | 
11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26  | 
* running and i just want a new goddamn tab. it * turns out, qutebrowser publishes an inane IPC * mechanism, in which JSON (i know!!) written to a * unix domain socket (I KNOW) can send signals to * a running qutebrowser process. newtab checks if * there's a running qutebrowser process and sends * the appropriate IPC signal if so. otherwise, it * forks off a new qutebrowser instance and returns * an exit status of 1. * * it takes a single argument, the URI of a page to * navigate to. if launched without an argument, * newtab simply opens a blank new tab. simple * enough, right? but why write it in C? to talk to * a goddammned python application, of all things? * well, i was originally going to do this in a  |