I'm the author of the port. I'm not sure how the suckless community
feels about Wayland, but it seems like the core protocol is fairly
lightweight, depends only on libffi, and is refreshing to work with
compared to X. Weston's goals are perhaps more orthogonal to suckless,
but I think there
Am 31.07.2013 um 10:40 schrieb Ari Malinen ari.mali...@gmail.com:
https://github.com/defer-/my-projects/blob/master/surf-0.6-searchengine.diff
I wrote patch which adds search engine integration. If you dont
provide any arguments surf loads homepage. If you provide url which is
not valid
v3 of the who(1) patchset.
From 5ee1ca2d61d351d7059d27eba124b68adb957e18 Mon Sep 17 00:00:00 2001
From: sin s...@2f30.org
Date: Mon, 5 Aug 2013 15:59:49 +0100
Subject: [PATCH 1/3] Implement -m for who
---
who.c | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git
On 2013-08-06 10:31, Joerg Jung wrote:
In you patch not valid means contains no dot, this makes it impossible
to search for something with a dot, e.g.: e.g. :)
Maybe look for a (starting) space instead?
If that's true, it also makes it impossible to go to URLs that are covered by
your DNS
From 23cc463e6e52d0ca975ee077c91f06bb9a2748f0 Mon Sep 17 00:00:00 2001
From: Bastien Dejean nihilh...@gmail.com
Date: Wed, 24 Apr 2013 12:06:52 +0200
Subject: [PATCH] Add an option to select non-matching files
---
stest.1 | 3 +++
stest.c | 8 +---
2 files changed, 8 insertions(+), 3
Am 06.08.2013 um 10:51 schrieb Chris Down ch...@chrisdown.name:
On 2013-08-06 10:31, Joerg Jung wrote:
In you patch not valid means contains no dot, this makes it impossible
to search for something with a dot, e.g.: e.g. :)
Maybe look for a (starting) space instead?
If that's true, it
Hi all,
After a recent discussion about including things like df(1)
in sbase we agreed that sbase should be free of unportable code.
I've quickly hacked together ubase[1]. I've taken sbase, stripped
it out and added an $(OS) var in config.mk.
Have a look at the code and let me know if there is
v3 of the who(1) patchset.
Good stuff! I'd rather not push until the manpage
is updated with the m option, though
On Tue, Aug 6, 2013 at 11:10 AM, Bastien Dejean nihilh...@gmail.com wrote:
From 23cc463e6e52d0ca975ee077c91f06bb9a2748f0 Mon Sep 17 00:00:00 2001
From: Bastien Dejean nihilh...@gmail.com
Date: Wed, 24 Apr 2013 12:06:52 +0200
Subject: [PATCH] Add an option to select non-matching files
cf.
mar77i@asus77i:~$ 0+445
-bash: 0+445: command not found
mar77i@asus77i:~$ a=(0+445)
mar77i@asus77i:~$ echo $a
0+445
holy crap, that's what happens. Weren't you looking for this instead:
mar77i@asus77i:~$ a=$(( 5554 - 1000 ))
mar77i@asus77i:~$ echo $a
4554
so, you're misusing bash's array syntax
On Mon, Jul 29, 2013 at 6:39 AM, Paul Hoffman nkui...@nkuitse.com wrote:
I just read something about using LD_PRELOAD for this. Write a library
that implements open(2), munging the file path and then calling the
real open(2). Then you just set LD_PRELOAD in the environment of the
scripts
On 2013-07-31, at 10:40, Ari Malinen wrote:
I wrote patch which adds search engine integration. If you
provide url which is not valid then surf passes it to search
engine. I see this as better approach than the searchengines
patch from surf.suckless.org.
The advantage of the approach on the
On 2013-08-06 21:27, Truls Becken wrote:
The advantage of the approach on the wiki is that you can have multiple
search engines configured, or really, URL shortcuts with optional string
substitution. Firefox has the same thing.
I, for one, only really use one search engine, but I agree that
Am 2013-08-06 15:52, schrieb Martti Kühne:
mar77i@asus77i:~$ 0+445
-bash: 0+445: command not found
mar77i@asus77i:~$ a=(0+445)
mar77i@asus77i:~$ echo $a
0+445
holy crap, that's what happens. Weren't you looking for this instead:
mar77i@asus77i:~$ a=$(( 5554 - 1000 ))
mar77i@asus77i:~$ echo $a
On 2013-08-06, at 21:35, Chris Down wrote:
On 2013-08-06 21:27, Truls Becken wrote:
The advantage of the approach on the wiki is that you can have multiple
search engines configured, or really, URL shortcuts with optional string
substitution. Firefox has the same thing.
I, for one, only
The way I always get around this search vs. URI schema dilemma for URLs in
my DNS search domain is by appending a slash to the end, which at least makes
Chromium behave as expected.
I added detection of url if there is slash at the end of line.
On Tue, Aug 6, 2013 at 11:01 PM, Truls Becken
Am 2013-08-07 00:04, schrieb Ari Malinen:
The way I always get around this search vs. URI schema dilemma for
URLs in
my DNS search domain is by appending a slash to the end, which at
least makes
Chromium behave as expected.
I added detection of url if there is slash at the end of line.
You
17 matches
Mail list logo
