On Thu, Jun 17, 2021 at 09:14:41AM +0200, Matthias Beyer wrote: 
> I agree, although a mechanism to add these links manually wouldn't hurt right?

I've got a homemade solution for this that might be interesting for
you? I know, not perfect at all, but I think it is helpful.

If you take a look at my own hub,[1] I take advantage from Markdown
support in profile descriptions. I've included two navigation links 
that I think are what I need. Anyhow, maybe you could use this to 
create a navigation menu tailored to your needs.

And yes, sometimes we forget sourcehut is still in alpha...

Cheers!

> I think getting syntax down is probably an important step to figuring
> out a roadmap. Without knowing much about how languages like Forth
> handle this, it seems like having two modes of operation would make
> sense. You could have the existing operations mode and then the : prefix
> switches to a command mode. This mode could then provide the following:
> 
> :4d
> 
> Drop 4 times
> 
> :2swp(3,4)d
> 
> Does (swap index 3/4 then drop) twice
> 

> stack_peek is something I noticed, but it doesn't seem sufficient for
> this purpose. How would I loop through all of the values on the stack
> instead of just the tip?

That's right. My mistake. Then iterating over the stack is the only
way to go.

-- 
Ariadna Vigo
Web: <https://ariadnavigo.xyz>
PGP: 0xA3B1324836A669BD

> > 2. Don't declare+initialize, initialize when needed. This helps
> > detecting some nasty bugs... maybe not in this context, but it's a
> > really good rule of thumb.
> 
> Is there a particular reason why explicity assigning a default is so
> frowned upon?
> 
> I would prefer to say that this variable has a value of NULL instead of
> leaving that up to the compiler.
> 
> Though, sometimes it's useful, for example when that variable is
> assigned right afterwards to access later from a higher scope (what I
> used when writing lexers or parsers that ignore whitespace).

I can't apply this patch set either, and I think I know what's going on 
here...

I have the feeling that you're sending diffs against commits that are
local to you. What I need on my end is patches that have their origin
in the master branch. The error I get is that the commit hashes are
unknown on my end.

The way to solve this is doing a rebase -i using **my** last commit and
'squash' everything into one single commit that directly modifies my
last commit.

-- 
Ariadna Vigo

> diff --git a/minitimer.c b/minitimer.c
> index aaa7b1d..7401729 100644
> --- a/minitimer.c
> +++ b/minitimer.c
> @@ -69,7 +69,7 @@ file_cleanup(void)
>  static void
>  usage(void)
>  {
> -	die("usage: minitimer [-lsv] [-L label] [HH:MM:SS]");
> +	die("usage: minitimer [-lsv] [-L label] [-T timeout_command] [HH:MM:SS]");
>  }
> 
>  static void
> @@ -204,6 +204,7 @@ main(int argc, char *argv[])

> My vis config automatically fixed this on save :)

The thing is that this breaks this and your other patch...

Two alternatives:
1) Removing trailing ws from 'master', not your current branch and send
that patch... (may break, though)
2) Recommended: do this in the other patch, in a separate commit... 
that would include it into the same patch set and 'git am' can do
more clever stuff in that case.

-- 
Ariadna Vigo
Web: <https://ariadnavigo.xyz>

Hi!

> I think it would be nice to add parameters to commands to allow some
> additional functionality. For example, :d could have a parameter for how
> many elements to drop, the WIP :s command could be used to limit how
> many elements are printed, and (maybe) the :swp command could allow
> specifying two indices to swap. These would be optional and have
> (the currennt) functionalities as defaults.

I definitely would consider this a goal for 1.x. This would make scalc
very Forth-like and I love that idea. Moreover, if we could combine
commands in one single expression, to do stuff... wow, that would be
awesome... almost driving scalc to DSL-territory (not sure if I'd like
to see this becoming a proper programming language... tbh, it's

Hi!

> diff --git a/stack.c b/stack.c
> index c9fa9da..9dac957 100644
> --- a/stack.c
> +++ b/stack.c
> @@ -114,6 +115,19 @@ stack_swap(Stack *stack)
>  	return 0;
>  }
>  
> +int
> +stack_show(Stack *stack)
> +{
> +	if (stack->sp < 0) {

Thanks for the patch. Just a very simple fix: your patch removes 
*trailing* spaces, not leading spaces. Could you change the commit
message to reflect that? If I did it using --amend, I'd be generating 
an entirely new commit and that would break your history.

-- 
Ariadna Vigo
Web: <https://ariadnavigo.xyz>
PGP: 0xA3B1324836A669BD