emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-fstree.el overview over directories (but no comments are possible)
Date: Sun, 30 Oct 2022 18:17:54 +0000	[thread overview]
Message-ID: <87sfj5yy3x.fsf@posteo.net> (raw)
In-Reply-To: <87wn8hi64m.fsf@mat.ucm.es> (Uwe Brauer's message of "Sun, 30 Oct 2022 18:16:41 +0100")

Uwe Brauer writes:

> Hm I played around with filetags and it is quite nice, I think, thanks
> for pointing it out to me.
>
> I would be extremely interested how you use helm-locate in that context,
> and you give me an example, please?
>
> For example I have the following tags added to a specific directory 
> bio-hoja4 -- EDO Uwe.tex
> and
> h1A_ECM_n -- analysis1.tex
>
> How would I use helm-locate to search those tags?

At first I used a controlled vocabulary for the tags, setting the
variables filetags-enforce-controlled-vocabulary and
filetags-controlled-vocabulary. But I was getting some false positives.
So it occurred to me to configure this other variable like this:

(setq filetags-delimiter-between-filename-and-tags "%ftag_")

This way, if I start typing in helm-locate %ftag_ I already start
getting more accurate results. Like I said, it's not a panacea, but it
more or less does the trick :-)

BTW, i don't use helm-locate directly but helm-mini with a number of
sources related to buffers, markers, and files:

(setq helm-mini-default-sources '(helm-source-buffers-list
				  helm-source-recentf
				  helm-source-buffer-not-found
				  helm-source-bookmarks
				  helm-source-bookmark-set
				  helm-source-locate))

So with a single call to helm-mini I can get information about open
buffers, recent files, bookmarks, and locate.

Best regards,

Juan Manuel 



  reply	other threads:[~2022-10-30 18:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30  9:49 org-fstree.el overview over directories (but no comments are possible) Uwe Brauer
2022-10-30 12:52 ` Juan Manuel Macías
2022-10-30 13:10   ` Uwe Brauer
2022-10-30 13:56     ` Juan Manuel Macías
2022-10-30 14:01       ` Uwe Brauer
2022-10-30 15:40         ` Juan Manuel Macías
2022-10-30 16:42           ` Uwe Brauer
2022-10-30 17:16       ` Uwe Brauer
2022-10-30 18:17         ` Juan Manuel Macías [this message]
2022-10-30 18:48           ` Uwe Brauer
2022-10-30 19:04             ` Juan Manuel Macías
2022-10-30 19:21               ` Uwe Brauer
2022-10-30 19:26                 ` [correction] (was: org-fstree.el overview over directories (but no comments are possible)) Uwe Brauer
2022-10-30 19:51                   ` [correction] Juan Manuel Macías
2022-10-30 21:23                     ` [correction] Uwe Brauer
2022-10-31 12:22                       ` [correction] Juan Manuel Macías
2022-10-31 12:55                         ` [correction] Uwe Brauer
2022-10-31 15:08                           ` [correction] Juan Manuel Macías
2022-10-31 15:48                             ` [correction] Uwe Brauer
2022-10-31 16:23                               ` [correction] Juan Manuel Macías
2022-10-31 16:33                                 ` [correction] Uwe Brauer
2022-10-31 16:58                                 ` [correction] Uwe Brauer
2022-10-31 17:35                                   ` [correction] Juan Manuel Macías
2022-10-31 17:38                                     ` [correction] Uwe Brauer
2022-10-31 21:01                                       ` [correction] Juan Manuel Macías
2022-11-01  7:13                                         ` [correction] Uwe Brauer
2022-11-01  7:16                                           ` [correction] Uwe Brauer
2022-11-01 13:52                                             ` [correction] Juan Manuel Macías

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87sfj5yy3x.fsf@posteo.net \
    --to=maciaschain@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=oub@mat.ucm.es \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).