I'll do this tonight, sorry I've been gone so long, a new job and a
2-hour-each-way commute kills a lot of time.
On Thu, Oct 17, 2013 at 12:16:19PM -0500, Galos, David wrote:
> I'll do this tonight, sorry I've been gone so long, a new job and a
> 2-hour-each-way commute kills a lot of time.
I've been maintaining sbase for some time now and we've pushed all these
patches already.
Hi all,
I've been thinking, besides the commands that are already listed in TODO
and all the unimplemented options for existing commands, what other commands
do we want to include in sbase?
The current TODO list includes:
diff, expr, printf, tr, unexpand
What about:
od, logname, uuencode, uude
Ok. I'm happy to go back to writing patches; I'm glad all the changes got in.
On Thu, Oct 17, 2013 at 12:30 PM, sin wrote:
> On Thu, Oct 17, 2013 at 12:16:19PM -0500, Galos, David wrote:
>> I'll do this tonight, sorry I've been gone so long, a new job and a
>> 2-hour-each-way commute kills a lot
> What about:
>
> od, logname, uuencode, uudecode, mktemp, passwd, su, sed, patch
>
ed and awk are also missed (yeah, I know they are bigger and
more difficult programs, but they are basic for a system).
--
Roberto E. Vargas Caballero
__
On Thu, Oct 17, 2013 at 08:38:54PM +0300, sin wrote:
> I've been thinking, besides the commands that are already listed in TODO
> and all the unimplemented options for existing commands, what other commands
> do we want to include in sbase?
>
> […]
>
> What about:
>
> od, logname, uuencode, uudec
Alex Pilon dixit:
>Don't od's and hexdump's functionality overlap?
Yes, they (and hd) are normally one binary.
>Do we still really need uuencode and uudecode?
Yes!
I often use them, in combination with GNU screen, to
copy/paste files(!) from one tab to the other, when
using other methods (such
> Alex Pilon dixit:
> > Do we still really need uuencode and uudecode?
>
On Thu, Oct 17, 2013 at 07:46:35PM +, Thorsten Glaser wrote:
> Yes!
>
> I often use them, in combination with GNU screen, to
> copy/paste files(!) from one tab to the other, when
> using other methods (such as rsync or s
Alex Pilon dixit:
>I know the trick. I used base64 for that, not uuencode. Don't they
>both have the same overhead, other than uuencode's header?
Yes but uuencode is more portable… e.g. the Linux “base64” tool is
rarely installed anywhere and is extremely picky about the formatting
of its input;
I am trying to use st, but it fails with the message "XOpenIM failed.
Could not open input device."
I checked the XOpenIM man page, which said that it opens an input
method, so I checked the man page, the X11 header files, the Arch
Linux package repos, and Google hits for "XIM", "X Input Method",
Hi,
thank you for the patch. It works nice! Are you going to add it to
wiki for users which are not subscribed to mailing list?
Branislav Blaškovič
On Wed, Oct 16, 2013 at 11:42 AM, Jochen Sprickerhof
wrote:
> Hi,
>
> I've implemented a (limited) scrollback buffer for st. Thanks to v4hn
> for
11 matches
Mail list logo
