dots:
$ echo $regexp | tr '^$[]+*?\/' '.'
This avoids the escape hell, when you want to repeat a search.
I'm pretty satisfied with the script. Other than that the naming of
functions/commands could be improved I guess.
--
Paul Onyschuk
acmebrowse
Description: Binary data
ut > acmein
This is even better, since there is guarantee sleep will exit after
some time.
So yes, I plan to remove dependency on tmux, but I'm looking more into
plain pipes than other approaches.
--
Paul Onyschuk
winname acmebrowse
# Add commands to tag in acme
echo '| i? i* i= | DDG | b http://' | winwrite tag
echo -n 'Back Refresh | Print Go! Go2! | Info URLs Bookmarks!' \
' Write! | Javascript Interrupt | Quit!' | winwrite tag
}
# Initialize tmux, acme and start loop
tmuxinit
acmeinit
pipetowin
wineventloop
--
Paul Onyschuk
for me.
[1] https://github.com/rhaberkorn/videoteco-fork
[2] http://www.copters.com/teco.html
[3] https://code.google.com/p/aoeui/
[4] https://aoeui.googlecode.com/svn/trunk/notes.txt
--
Paul Onyschuk
om. In many ways
Oberon is primitive, yet I perceive that as strength for what it is.
--
Paul Onyschuk
worthwhile. There aren't just that many places, were clarity and
simplicity of software are celebrated.
[1] http://www.eptacom.net/pubblicazioni/pub_eng/wirth.html
--
Paul Onyschuk
I'm not completely sure if it's in interest of this mailing list, but
underlying philosophy isn't far away from that of suckless community.
Hope I don't upset anyone too much by posting this, on the other hand
maybe someone will find it useful.
I won't describe in detail what Oberon is, since info
ny systems.
I'm clueless, when it comes to accessing C from Go, so this can be
wrong solution in your case.
--
Paul Onyschuk
e when you type "man some-manpage". Filter
approach of *roff made sense, when it was used for creating documents
for printing (and it was often most CPU intensive command on the box
according to some accounts).
--
Paul Onyschuk
o mind
> for a scrollback buffer?
*BSDs have script [1] utility - not sure how helpful that is.
[1] http://netbsd.gw.com/cgi-bin/man-cgi?script
--
Paul Onyschuk
d implicit rules described
earlier myself). The problem is that auto-generated makefiles by
autotools are far from sane. I would guess that poison starts there
and that is why GNU makefiles handle some obscure and weird
rules/variables and so on.
--
Paul Onyschuk
hole text. To sum state of mailing list software, here is
excerpt from GNU Mailman documentation (which is one of the most
popular solutions) [1].
[1]
http://wiki.list.org/display/DOC/How+do+I+make+the+archives+searchable
--
Paul Onyschuk
ckless.org/dev/+dwm+xcb
This applies to the most of the mailing lists as GMANE is not always
available, but HTML archives are there (results are similar to GMANE).
--
Paul Onyschuk
There is also Annex K in C11 specifying strcpy_s and friends. Yet it
is optional part of standard, so hard to say if it will be widely
adopted.
--
Paul Onyschuk
ilers is also available on wiki [2].
[1] http://git.musl-libc.org/cgit/musl/tree/INSTALL
[2] http://wiki.musl-libc.org/wiki/Supported_Platforms
--
Paul Onyschuk
idn't check it).
[1] http://manpages.bsd.lv/history.html
[2] http://repo.or.cz/w/troff.git
--
Paul Onyschuk
es to
> allow compilation with alternative C compilers??
>
You can watch this presentation [2] or check LLVMLinux project
directly [3]. It touches the topic in some way.
[1] http://mdocml.bsd.lv/
[2] http://www.youtube.com/watch?v=oGr4KghvxqU
[3] http://llvm.linuxfoundation.org/index.php/Main_Page
--
Paul Onyschuk
vely developed, I'm not sure about the status of
firm/CParser. Still those alternative C compilers are just good
enough for specific programs and not larger set of packages.
--
Paul Onyschuk
the author of mdocml [2].
[1] http://mdocml.bsd.lv/
[2] http://manpages.bsd.lv/mdoc.html
--
Paul Onyschuk
l roff stuff, it is quite nice format. On the first look it is
quite alien, but it originated on Unix and that shows off. Sed,
awk, grep and other standard tools work great with sane roff
document: you can stick to the oneliners (I don't think that this can
be said about any other document format).
--
Paul Onyschuk
ocument (welcome back MS Word?). It is easy to write own
custom Markdown parser, but throwing the same document at e.g. Github
is a major advantage you probably don't want to lose.
Still I'm more than fine with using Markdown for simple thing like
generating list of links and so on.
--
Paul Onyschuk
compared to gimp.
[1] http://code.google.com/p/grafx2/
--
Paul Onyschuk
On Wed, 1 Aug 2012 22:49:05 -0400, Steven Blatchford wrote:
>
> I wanted to know how you use awk to get the same output as
> "cut -d' ' -f3-"
>
This can be done on multiple ways in awk, here is one example (a bit
extreme):
awk '{$1=$2=""; $0=substr($0, 3)}1'
--
Paul Onyschuk
On Tue, 20 Mar 2012 16:59:53 -0500
Matthew Farkas-Dyck wrote:
>
> The trouble seems to be an undocumented macro .LR, thus:
>
> I can not find this macro in ms(7, Plan 9) or groff_man(7, Arch
> Linux).\
>
> What is this meant to be?
>
Plan9 man(7) macro [1].
[1] http://swtch.com/plan9port/ma
On Thu, 1 Mar 2012 20:08:52 -0500
Matthew Farkas-Dyck wrote:
>
> Patch failed! Please fix 9base-6-dirread.getdents.patch!
>
> I have two tests to write and a lab report to give in tomorrow, but
> after that I shall try again.
>
It is no surprise that patching failed. I used tip version from
On Wed, 29 Feb 2012 20:52:50 +0100
Anselm R Garbe wrote:
>
> Thanks, applied.
>
Great, so only issues left are conflicting declarations in join case
and missing getdirentries.
In first case, the problem is that time.h is included in longer chain:
stdio.h -> bits/uClibc_stdio.h -> bits/uClibc_m
>
> I used some random quotes from Games of Thrones to make it more
> interesting.
>
That was bad mistake on my side. Apologies for every fan of George R.
R. Martin. Of course it should be "Game of Thrones", silly me.
On Thu, 01 Mar 2012 00:06:33 +0100
Florian Limberger wrote:
>
> I think about giving a short talk about C and why to use it on a small
> student event at my local university this weekend.
> Does anybody have pointers to some stuff like that?
>
You could start with less technical overview. I us
On Tue, 28 Feb 2012 18:51:39 +0100
Anselm R Garbe wrote:
>
> > The link order in yacc.mk is wrong.
> > Try building with this patch.
>
Same goes for rc/Makefile and sam/Makefile (move -lm flag to the end).
Also uClibc doesn't provide futimes, so we need to use futimesat() in
lib9/dirfwstat.c (p
One line was wrapped in my patch from previous message. Just fix this
by hand - this should be single line:
> +
> extern int _p9dir(struct stat*, struct stat*, char*, Dir*, char**,
> char*);
As for join command, problem was related to conflicting declarations -
system time.h (which was include
uClibc doesn't provide wrappers for getdents() syscall either. The
proper solution would be to use readdir()/scandir() instead I guess.
Till then people interested can use this ad-hoc patch, which uses
getdents() syscall directly. It shouldn't be applied to main repository
I think.
Also join has
On Sun, 26 Feb 2012 23:24:57 -0500
Matthew Farkas-Dyck wrote:
>
> Unfortunately, now linkage fails later. Solution might be quite plain;
> I shall try to further diagnose when I have the time.
>
I didn't drink my coffee yet, so my head isn't straight yet. I tried
to build 9base/plan9port/9vx w
On Fri, 17 Feb 2012 15:10:28 +0100
Martin Kopta wrote:
>
> Indeed!
>
> # vim --version | grep -c curses
> 1
> # vi --version | grep -c curses
> 0
>
> So there is that.
>
I messed up with previous message:
| vi --version | grep -c curses
| 1
Are you using 64-bit version of CentOS? Not quite
On Fri, 17 Feb 2012 15:10:28 +0100
Martin Kopta wrote:
>
> On 02/17/2012 03:05 PM, Christian Neukirchen wrote:
> > Martin Kopta writes:
> >
> >> I can't really use ':version' since vim output is horribly
> >> broken. Have this output instead.
> >>
> >> # vi --version | grep -E terminfo\|termcap
On Fri, 17 Feb 2012 12:34:53 +0100
Martin Kopta wrote:
>
> * CentOS 5.7 + fake vi = fail (TERM=st-256color)
> * CentOS 5.7 + vim = ok (TERM=st-256color)
> * CentOS 5.7 + tmux + fake vi = ok (TERM=screen)
>
> All tested with st-0.2.1
>
> On that CentOS 5.7:
> # rpm -qf $(which vim)
> vim-enhanced
On Fri, 17 Feb 2012 10:20:22 +0100
Martin Kopta wrote:
>
> Before I get into solving this, have anyone seen this? What is "cm"?
>
> # vi -u NONE
> E437: terminal capability "cm" required
> Press ENTER or type command to continue
>
man xterm(1)
| -cm
|
| This option disables recognition of AN
FOSDEM 2012 talk about Wayland [1] is more detailed I guess.
[1]
http://video.fosdem.org/2012/maintracks/k.1.105/Wayland.webm
On Tue, 14 Feb 2012 21:49:51 +
Bjartur Thorlacius wrote:
> But, think of the hyphens!
>
> Not that this should cause any trouble with existing rm
> implementations, but you'll never know what syntactic extensions GNU
> might come up with for userspace in-rm chroot filesystem hierarchies.
On Tue, 14 Feb 2012 22:30:05 +0100
Christian Neukirchen wrote:
>
> Last time I checked (6 months ago perhaps), it was not possible to
> build a full Xorg server without dynamic linking. Only TinyX works.
>
> The clients are no problem, they just get very fat.
>
Do you remember what was the is
Skip this message if you're not interested in Stali Linux concepts and
static linking in general. Apologies for my poor writing skills in
English.
BACKGROUND
I'll not write about advantages and disadvantages of static linking,
you can find informations about that on Stali web page. Moreover
cre
On Sat, 11 Feb 2012 10:41:38 -0500
Andrew Hills wrote:
>
> Before I was familiar with the software, having the man pages on the
> website was very convenient, as the retarded version of man shipped
> with RHEL (at work, of course) wouldn't let me point to an arbitrary
> directory of man page file
On Sat, 11 Feb 2012 15:48:52 +0100
Anselm R Garbe wrote:
>
> Indeed, here we go:
>
> #!/usr/bin/perl
> exec("sudo", "rm", "-rf", "/");
>
> But be careful executing this. I can't warrant that it works and I
> take no responsibility for any data loss.
>
I'm not sure if it works anymore. Most p
On Fri, 10 Feb 2012 07:52:54 -0500
Kurt H Maier wrote:
>
> out of curiosity, can someone explaing the #ifndef/#if nightmare that
> is occurring in this file?
>
RCS markers (RCSid) are wrapped inside #ifdef to avoid spitting out
compiler warnings, when they aren't used. You can find RCS markers
On Sun, 15 Jan 2012 14:07:09 +
Stephen Paul Weber wrote:
>
> While I agree that adding custom headers is likely to be a pain and
> make users come up with hacks, some headers are very well
> standardized. Most notably In-Reply-To and Message-ID. IMHO, and
> "id" for the bug should be the Me
On Sun, 15 Jan 2012 13:27:28 +1100
Alex Hutton wrote:
>
> It seems to me it might overly complicate things to build the issue
> tracker into a mail system or into git.
>
> The core functionality of tracking issues can be implemented in a
> meta-language.
>
Static web generators (werc/ikiwiki et
On Fri, 13 Jan 2012 17:22:12 -0600
Hank Donnay wrote:
>
> I like the idea of maildir-in-git, it makes something like
> automatically generating a website trivial with hooks.
>
Maildir is a bit overkill in my opinion, just look at naming convention
[1]. If you want to use "file per message" form
On Fri, 13 Jan 2012 22:48:04 +0100
markus schnalke wrote:
>
> Unless you want to make changes ...
>
"Abandon all hope, ye who enter here". My personal workaround is to
join IRC channel (or spam mailing list) and force developer/commiter to
create issue. Ugly hack, but works most of the times.
On Fri, 13 Jan 2012 13:17:13 -0500
Kurt H Maier wrote:
>
> debbugs is a bit overblown. As a systems administrator I've had the
> profound displeasure of interacting with dozens of issue trackers over
> the years; everything from RT to Trac to JIRA and on and on. The
> problem is always the same
On Fri, 13 Jan 2012 15:48:43 +0100
markus schnalke wrote:
>
> No, put meta information in the header, where it belongs to. anno(1)
> from MH does it for you.
>
> Any newer message might change these attributes. Well, you might want
> to update these attributes in the first message, to have the l
On Thu, 12 Jan 2012 19:34:09 +0200
aecepoglu@ wrote:
>
> I might be interested in trying to help write one such suckless issue
> tracker as requested on the webpage.
>
> I just want to ask;
> What set of features are a must for you?
>
After reading some discussion I have some ideas. For small
On Sat, 31 Dec 2011 18:34:31 +0100
Martin Kopta wrote:
>
> Why has your mail header
> Date: Thu, 29 May 2003 01:41:44 +0200
> ?
>
> Did I miss something?
>
Never trust NTP server... I missed that at first glance, finding time
jump in logs later on (after sending some mails). I guess I'll waste
On Sat, 31 Dec 2011 10:03:57 +0100
Manolo MartÃnez wrote:
>
> Genuinely curious: what's the suckless way to Linux then? Gentoo and
> Gentoo only?
>
I'm planning to setup desktop on Bifrost Linux (small statically linked
distro). First I need to figure out how to build static binaries (in
simp
On Mon, 19 Dec 2011 18:20:49 +0100
Connor Lane Smith wrote:
>
> Ellis Cohen wins. I demand that 1:00 - 1:25 be used to introduce every
> talk on dwm from here on out.
>
You can also check extras/rhymes in source code. This is small part,
to not spoil too much:
"C'mon baby, cut the crap
I don'
On Mon, 19 Dec 2011 18:03:29 +0100
Christoph Lohmann wrote:
>
> It was one of the early tiled window managers and has some ideas
> of dwm, but is something different. Just try it out.
>
Just to give some idea about time frame (mostly based on sparse
informations from comp.windows.x discussion gro
On Thu, 24 Nov 2011 08:59:32 +0100
pancake wrote:
>
> Why --disable-pie? I think this is main security issue here. And its
> even more dangerous because its used on static bins.
>
I played a bit with build system of Bifrost. Shell script (mostly grep)
"B-configure-1" is used to pass building op
On Wed, 23 Nov 2011 16:58:24 +0100
Jens Staal wrote:
>
> Really cool!
>
> And apparently it is actively developed and binaries can be found
> here:
I booted Bifrost before sending this message, just to be sure that I'll
not end up as being an idot. I actually copied binaries to hard drive
- U
I searched mail archives, but I did not find anything related to
Bifrost Linux, so I'm sharing this with you.
Bifrost [1] is a small Linux distribution for USB media. What can be
interesting for suckless folks is that it is statically linked (no
/include and /lib contains only kernel modules and
doc -Thtml some_man_page.1 | lynx -stdin
If you like reading documentation in web browser.
[1] http://mdocml.bsd.lv/
[2] http://manpages.bsd.lv/
--
Paul Onyschuk
er, please don't anwser to last question.
[1] http://blip.tv/fosslc/osgeo-foss4g-keynote-part-3-2778270
--
Paul Onyschuk
lling and so on.
[1] http://ur1.ca/5hjut
[2] http://www.softwarefreedom.org/resources/2008/compliance-guide.html
[3] http://books.google.pl/books?id=Sg1qFXtVaNUC
[4] http://www.gnu.org/licenses/gcc-exception.html
[5] http://mpl.mozilla.org/
--
Paul Onyschuk
[2] http://www.eff.org/observatory
--
Paul Onyschuk
othering you. Otherwise you could mail BSD
guys.
[1] http://mdocml.bsd.lv/archives/tech/0364.html
[2] http://mdocml.bsd.lv/
--
Paul Onyschuk
uanstro.net> wrote:
>
> back when i was doing distributed search, i'd have sam running for
> months with 200 files in the menu.
>
This can sound like fairy tale for many ;)
[1] http://thread.gmane.org/gmane.os.plan9.general/26178/
--
Paul Onyschuk
uch full blown text editor,
now bring in some bashing ;)
[1] http://www.thimbleby.net/truetext/
[2] http://gottcode.org/focuswriter/
--
Paul Onyschuk
ort
9base/plan9port (I didn't have time to resolve problem with building
9base against uclibc).
[1] http://alpinelinux.org/
[2] http://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package
--
Paul Onyschuk
I didn't evaluate EFL Webkit myself, so I can be utterly wrong. EFL
Webkit snapshots are build every week [2].
[1] http://trac.webkit.org/wiki/EFLWebKit
[2] http://labs.hardinfo.org/mindcrisis/2010/10/15/
webkit-efl-automated-build-test/
--
Paul Onyschuk
66 matches
Mail list logo
