9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Daniel Moch <daniel@danielmoch.com>
To: 9front@9front.org
Subject: Re: [9front] [~orib/Nail PATCH] Add thread links to bottom of message
Date: Mon, 23 Nov 2020 04:25:27 -0500	[thread overview]
Message-ID: <4E862BC2A959CC01FEF2F588B49BA67D@ranger.org> (raw)
In-Reply-To: <8361BE0C6E3181161AF3DD8396C3AFC9@eigenstate.org>

Quoth ori@eigenstate.org:
> Quoth Daniel Moch <daniel@danielmoch.com>:
> > This usability patch places thread links at the bottom of displayed
> > messages in addition to the beginning to allow for easier thread
> > navigation.
> > 
> > diff -urN a/mesg.c b/mesg.c
> > --- a/mesg.c	Sat Nov 21 14:21:15 2020
> > +++ b/mesg.c	Sat Nov 21 19:19:21 2020
> > @@ -262,6 +262,15 @@
> >  	}
> >  
> >  	home = getenv("home");
> > +	if(m->parent != nil || m->nchild != 0) {
> > +		Bprint(wfd, "\n");
> > +		Bprint(wfd, "===> Thread:");
> > +		if(m->parent && !(m->parent->state & Sdummy))
> > +			Bprint(wfd, " ↑ %s", m->parent->name);
> > +		for(i = 0; i < m->nchild; i++)
> > +			Bprint(wfd, " ↓ %s", m->child[i]->name);
> > +		Bprint(wfd, "\n");
> > +	}
> >  	if(m->nparts != 0)
> >  		Bprint(wfd, "\n");
> >  	for(i = 0; i < m->nparts; i++){
> > 
> 
> Not sure on this -- but you may be interested in a patch
> that phil9 is working on, to do a full conversation view,
> instead of one message at a time.
> 
> It's still a work in progress.

After using it for a day I'm not wild about it either.  It's helpful
for longer messages, but there could easily be a better way to manage
that.

Is phil9's patch available somewhere?


      reply	other threads:[~2020-11-23  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22  0:30 Daniel Moch
2020-11-23  1:06 ` [9front] " ori
2020-11-23  9:25   ` Daniel Moch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E862BC2A959CC01FEF2F588B49BA67D@ranger.org \
    --to=daniel@danielmoch.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).