I have written the manpage, and pushed this. I have also cleaned
up who, and addedthe '-l' flag.
> Good stuff!
Except for the way that strings were handled when adding '-m'
Both ttyname and strrchr could have easily returned NULL, so
that should have been checked for. I've fixed this in the cleanu
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
>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 wr
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,
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
4
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
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 t
Thanks for feedback. I improved the url detection a bit. Now it
considers input as url if it has dot and doesnt contain spaces. It
also considers "localhost" as url. Now the search string can contain
dots if it also contains spaces. DNS search domains could be solved
with DNS query but i think that
> I'm happy to maintain this and maybe host it at suckless.org as
> we do not currently have an ml at 2f30 for easily managing patches.
Good luck, I would be terrified to start maintaining such a project.
Also, mount looks easy to implement, so I'll see if I can whip up
a linux mount for you
On Mon, Jul 29, 2013 at 6:39 AM, Paul Hoffman 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 and Bob's your
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 Tue, Aug 6, 2013 at 11:10 AM, Bastien Dejean wrote:
>
> From 23cc463e6e52d0ca975ee077c91f06bb9a2748f0 Mon Sep 17 00:00:00 2001
> From: Bastien Dejean
> Date: Wed, 24 Apr 2013 12:06:52 +0200
> Subject: [PATCH] Add an option to select non-matching files
cf. http://lists.suckless.org/dev/1202/11
> v3 of the who(1) patchset.
Good stuff! I'd rather not push until the manpage
is updated with the m option, though
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 a
Am 06.08.2013 um 10:51 schrieb Chris Down :
> 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
>From 23cc463e6e52d0ca975ee077c91f06bb9a2748f0 Mon Sep 17 00:00:00 2001
From: Bastien Dejean
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 deletions(-)
diff --git a
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 DN
v3 of the who(1) patchset.
>From 5ee1ca2d61d351d7059d27eba124b68adb957e18 Mon Sep 17 00:00:00 2001
From: sin
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 a/who.c b/wh
Am 31.07.2013 um 10:40 schrieb Ari Malinen :
> 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 then surf passes it
> 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 the
20 matches
Mail list logo
