Whoops, I withdraw my complaint. Should have checked the basics before I
talked.
This is a packaging error. Sorry to waste your time and mine.
Regards,
spaceman
> Hi,
Hi Spaceman,
> When compiled with musl-gcc (latest) on Slackware 14.2 this:
>
> static void
> dowrite(const char *fname, int trunc)
> {
> …
> printf("%zu\n", bytecount);
> }
>
> does not work for me (it outputs a blank line). Given my rudimentary
> knowledge of C and looking up
Hi,
When compiled with musl-gcc (latest) on Slackware 14.2 this:
static void
dowrite(const char *fname, int trunc)
{
…
printf("%zu\n", bytecount);
}
does not work for me (it outputs a blank line). Given my rudimentary
knowledge of C and looking up on stackoverflow this does work.
On 2020-03-22, Hiltjo Posthuma wrote:
> Maybe it's an idea to just place issues in a TODO file in the repository?
That's a good idea, thanks.
I added a section with the issues reported by Cág, some existing items
from ed.c, and a few others I have noticed.
Hi,
As the original author of ed I have to apologize about this kind
of errors. I didn;t have so much time to finalize it, and there is
a list of known bugs in the header of the file. I would recomend to
add new known bugs to the the list and them let to new people to
fix them. I think the code
Michael Forney wrote:
> Sometimes people just don't have the time to investigate the issue and
> come up with a fix. It could even be that the fix involves more
> complex restructuring of the rest of the code.
Hello Michael,
Thanks for understanding. There's definitely a lack of time on my
On Sat, Mar 21, 2020 at 05:01:05PM -0700, Michael Forney wrote:
> On 2020-03-21, Hiltjo Posthuma wrote:
> > What kind of tracker?
>
> Did you see my other reply?
> https://lists.suckless.org/dev/2003/33827.html
>
I didn't see it.
> >I think discussions of suckless projects should stay
> > on
On Sat, Mar 21, 2020 at 02:59:12PM -0700, Michael Forney wrote:
> On 2020-03-17, Hiltjo Posthuma wrote:
> > Where is the patch?
>
> I know it's contrary to the opinion of a lot of people here, but
> personally, I have no issue with bug reports without a patch.
> Sometimes people just don't have
On Sat, 21 Mar 2020 14:59:12 -0700
Michael Forney wrote:
Dear Michael,
> I know it's contrary to the opinion of a lot of people here, but
> personally, I have no issue with bug reports without a patch.
> Sometimes people just don't have the time to investigate the issue and
> come up with a
On 2020-03-21, Hiltjo Posthuma wrote:
> What kind of tracker?
Did you see my other reply?
https://lists.suckless.org/dev/2003/33827.html
>I think discussions of suckless projects should stay
> on the mailinglist and/or IRC, not an external bugtracker or something.
Would suckless.org consider
On 2020-03-17, Hiltjo Posthuma wrote:
> Where is the patch?
I know it's contrary to the opinion of a lot of people here, but
personally, I have no issue with bug reports without a patch.
Sometimes people just don't have the time to investigate the issue and
come up with a fix. It could even be
On Sat, Mar 21, 2020 at 03:02:04PM -0700, Michael Forney wrote:
> On 2020-03-17, Cág wrote:
> > There are a couple things I've come across the
> > sbase's version of ed:
> > 1. w doesn't print the byte count. Suppose a sample
> > ed session (using P to distinguish my input from ed's
> > output):
On 2020-03-17, Cág wrote:
> There are a couple things I've come across the
> sbase's version of ed:
> 1. w doesn't print the byte count. Suppose a sample
> ed session (using P to distinguish my input from ed's
> output):
> % ed
> P
> *a
> milk
> bread
> eggs
> meat
> veggies
> bananas
> apples
>
On Tue, Mar 17, 2020 at 11:25:25AM -0400, Cág wrote:
> I must admit I only use ed(1) (of sbase) these days.
> It has been like this for a year or so.
>
> There are a couple things I've come across the
> sbase's version of ed:
> 1. w doesn't print the byte count. Suppose a sample
> ed session
I must admit I only use ed(1) (of sbase) these days.
It has been like this for a year or so.
There are a couple things I've come across the
sbase's version of ed:
1. w doesn't print the byte count. Suppose a sample
ed session (using P to distinguish my input from ed's
output):
% ed
P
*a
milk
15 matches
Mail list logo
