I'm not clear on what the issue is, so let me be a little more specific about what I am proposing.

You have some contexts that are not used for filtering and that you would like to see in the task list. Let's suppose that some examples are @call, @email, @spreadsheet, @camera

You have some other contexts that are used for filtering. Some tasks have multiples of these contexts.

Lets suppose that these filterable contexts include colour names like #red #purple #blue
size like *small, *medium, *large
direction like ^North, ^Northeast, ^East

Suppose that you have a large blue Northern spreadsheet. You would define the context as @Spreadsheet and the text tag as the text string "*large, #blue, ^North".

Now, if you want to see all the blue items and no items that are not blue you would add the following filter to your view:
AND (TEXTTAG Contains 'blue')
and you should get the blue items. The fact that there are other things in the text tag do not seem troubling to me, why do you consider this to be unusable?

I can think of two issues

1. You have mentioned elsewhere that you are talking about ad-hoc and not saved views. I am guessing that you mean that you do not want to use advanced settings. (I often use advanced settings creating an ad hoc view, I just do not save the filter.) Anyhow, you can type the word blue into the "text" quickfilter box in the left sidebar and select "texttag" in the following dropdown to get the same effect. You may need to uncheck other items in the dropdown.

2. You cannot group or sort tasks according to a substring from the texttag, only by the entire texttag string. If you must have  sorting or grouping by an attribute that cannot appear on the props line then I have no solution for you.

On 7/7/2022 09:35, Radek Pilich wrote:
The following is besides the original point of the request.

I don't like how tags are implemented.

They are fine for putting a single tag on a task.

But the way it creates "combined" tag when putting more than one tag on a task renders it unusable for me.

I can't even imagine what your suggestion would mean in my system.

On Thursday, 7 July 2022 at 14:51:28 UTC+2 Dwight wrote:

If you used tags instead of contexts for the filtering would the problem go away?

On 7/7/2022 05:49, Radek Pilich wrote:
Consider adding new setting to the context items - Show in props line.

Right now, ALL assigned context appear in the props line, which makes the feature of showing contexts in the props line pretty much useless if using more than 2-3 contexts for a single task.

I use multiple context "sub-groups", but most of them are used to separate tasks into views, turning a particular view into particular context(s) configuration. 

However there are some contexts, that are not used for filtering and that I would like to see in the props line.
--
You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/dbcc9823-b1d7-4c67-9439-915a1170c4acn%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/fc68464c-bec6-4e34-b8d3-26f810d05350n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/2795f255-a73b-2f0d-3e57-05ed8e092e5d%40gmail.com.

Reply via email to