Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tag hierarchy support #145

Open
maxchaos opened this issue Nov 8, 2020 · 13 comments · May be fixed by #146
Open

Tag hierarchy support #145

maxchaos opened this issue Nov 8, 2020 · 13 comments · May be fixed by #146
Assignees

Comments

@maxchaos
Copy link

maxchaos commented Nov 8, 2020

Firstly, I would like to thank you for your great work with this package. I have been using it for a while now and I sincerely find the query syntax to be very intuitive.
Regarding the issue at hand, I have noticed that org-ql's tag search mechanism (particularly org-ql--tags-at) does not take hierarchies (i.e., tag groups) into considerations. I understand that tag hierarchies are not that common and their syntax may be unnecessarily complicated (e.g., regular expressions) but, nevertheless, I think they are a useful thing to have.

@maxchaos maxchaos linked a pull request Nov 8, 2020 that will close this issue
@alphapapa alphapapa added this to the 0.5 milestone Nov 9, 2020
@alphapapa
Copy link
Owner

Hi,

Thanks for the kind words. I'm glad it's useful to you.

I thought I had an issue or note about tag groups somewhere, but apparently not. As you may have guessed, I don't use the feature myself, but I'd be glad to support it as long as it doesn't cause performance problems.

Thanks for the PR. I'll look at it.

@alphapapa alphapapa removed this from the 0.5 milestone Nov 9, 2020
@alphapapa alphapapa linked a pull request Nov 25, 2020 that will close this issue
@maxchaos
Copy link
Author

Hi,

Is there any progress with checking and integrating this feature? It's been some time now and I've been using this so far without issues on my end.

Thanks.

@alphapapa alphapapa added this to the 0.7 milestone Mar 31, 2022
@alphapapa
Copy link
Owner

Hi Panagiotis,

Thanks for reminding me, and apologies for the delay. I haven't had much time to work on my Emacs projects for a while, and when I have, I've been working on other projects of mine. I will plan to merge this for v0.7 of org-ql, and I'll try to review and test this and merge it to master soon, but it may be a bit longer. Please feel free to ping me again if necessary.

@maxchaos
Copy link
Author

maxchaos commented Apr 2, 2022

No problem. Thanks for taking the time to look at it in the first place and feel free to let me know if there is anything that I can do to help.

@alphapapa
Copy link
Owner

The master branch already has a number of new features that I'd like to release, so retargeting this for v0.8. Thanks for your patience.

@alphapapa alphapapa modified the milestones: 0.7, 0.8 Mar 10, 2023
@alphapapa alphapapa self-assigned this Mar 10, 2023
@maxchaos
Copy link
Author

You are welcome. Thanks for keeping this feature in mind.

@alphapapa alphapapa removed this from the 0.8 milestone Dec 16, 2023
@maxchaos
Copy link
Author

Hi,

It would seem this issue and pull request have grown stale so, if you agree, I think it's better to close them. I also don't feel like this functionality is needed by anyone else and I can keep using my personal fork, so there's no real need for merging it upstream.

Regardless, thank you very much for keeping this feature in mind for so long.

@alphapapa
Copy link
Owner

Hi again,

Well, I'd prefer to keep it open and merge it someday. It provides missing functionality that's built-in to Org. Even if you're the only person who uses it now, it's still part of Org, so we should support it.

However, one additional complication is that the Org maintainers and I are considering trying to upstream org-ql into Org in the future, and that would require copyright assignment to the FSF for the code. Have you signed the FSF CA for Emacs/Org? If so, there's no obstacle here. If not, it's a simple process, as long as your circumstances allow it (employment, nationality, etc).

Thanks for following up.

@maxchaos
Copy link
Author

maxchaos commented Jan 6, 2024

Hi and sorry for the late reply.

Upstreaming org-ql is actually great news! It was about time, if you ask me, since packages like this and org-ml simplify the overall interaction and experience considerably.

If you feel keeping this MR around for later, then that also works for me.

Having said that, I'm not sure what is needed by me regarding the copyright assignment you mentioned. I don't believe I have any legal blockers but I'm not sure what it is required to do either. Is this necessary for contributing such a small feature to the codebase?

@yantar92
Copy link
Contributor

yantar92 commented Jan 6, 2024 via email

@maxchaos
Copy link
Author

maxchaos commented Jan 6, 2024

@yantar92 thank you for replying so fast. I'll check it out and let you know when the ca is signed.

@alphapapa
Copy link
Owner

@yantar92 Would you agree if I added a note to the readme stating the general intention to upstream org-ql and mentioning the FSF CA requirement?

@yantar92
Copy link
Contributor

yantar92 commented Jan 6, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants