On Tue, Jul 27, 2021 at 06:24:49PM -0700, alex wennerberg wrote:
> I'm trying to replace my usage of the mastodon web interface with toot,
> and there's a few features I think I'd need -- let me know what you
> think. I can get started on these if you think they make sense.
> 
> For notifications, add a parameter to only filter mentions
> 
> For notifications, timelines, and a few other commands, add a parameter
> for one-line output, so the output can be easily grep'd
> 
> For the TUI, add a tab for notifications/mentions
> 
> Let me know what you think!

Thanks!

-- Ivan

On Tue, Jul 27, 2021 at 07:01:27PM -0700, alex wennerberg wrote:
> Note that I could also see an argument for all lowercase. Let me know
> what you think

I would prefer starting with lower case, that seems to be standard for
linux command line utils. And --help which is added automatically by
argsparse is lower cased so we're still not fully consistent even with
this patch.

-- Ivan

By default order tickets by last updated, if not otherwise defined.
---
 tests/test_search.py           | 115 ++++++++++++++++++++++-----------
 todosrht/blueprints/tracker.py |   3 +-
 todosrht/search.py             |  32 ++++++++-
 3 files changed, 109 insertions(+), 41 deletions(-)

diff --git a/tests/test_search.py b/tests/test_search.py
index 5f87887..624abf5 100644
--- a/tests/test_search.py
+++ b/tests/test_search.py
@@ -1,5 +1,6 @@
 import pytest
 
[message trimmed]

This adds ordering by id and updated, using ! for reversing, similar to
negation of terms. E.g. sort:updated, !sort:updated.

I wanted to add ordering by number of comments, but it required changing
the base query to include the comment count, which was a pain to get to
work correctly using sqlalchemy so leaving it for later.

Ivan Habunek (1):
  Implement ticket ordering

 tests/test_search.py           | 115 ++++++++++++++++++++++-----------
 todosrht/blueprints/tracker.py |   3 +-
 todosrht/search.py             |  32 ++++++++-
 3 files changed, 109 insertions(+), 41 deletions(-)

Thanks, applied. Sorry for the longish wait.

Ivan

Thanks, applied.

-- Ivan

On Fri, 28 Aug 2020, at 21:23, Denis Laxalde wrote:
> It might also be nice to support more than one parameter. E.g.
> "sort=-creation_date,title", meaning sort by creation_date reversed,
> then title.

It might be simpler to specify sort multiple times, e.g. 
`sort=-creation_date sort=title`, or whatever syntax is agreed upon.

I actually have a WIP patch for sorting, could finish it up.

Ivan

On Sun, May 24, 2020 at 07:26:18AM +0000, Simon Ser wrote:
> IMHO rendering as checkboxes is already a step forward. I don't mind
> having to edit the Markdown source to update the checkbox status.

I agree with Simon. Having read-only checkboxes is better than not
having them at all.

-- Ivan

On Sun, May 24, 2020 at 07:25:01AM +0000, Simon Ser wrote:
> There's a "readonly" attribute that makes it look like regular
> checkboxes while being immutable.

The readonly attribute does not apply to checkboxes unfortunately.

MDN says:
"Note: Only text controls can be made read-only, since for other
controls (such as checkboxes and buttons) there is no useful distinction
between being read-only and being disabled, so the readonly attribute
does not apply."

I would argue that visuals are a useful distinction, but hey.