From: Uwe Brauer <oub@mat.ucm.es>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: Uwe Brauer <oub@mat.ucm.es>, orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-fstree.el overview over directories (but no comments are possible)
Date: Sun, 30 Oct 2022 20:21:56 +0100 [thread overview]
Message-ID: <87h6zlglrf.fsf@mat.ucm.es> (raw)
In-Reply-To: 87mt9dyvys.fsf@posteo.net
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
>>> "JMM" == Juan Manuel Macías <maciaschain@posteo.net> writes:
> Uwe Brauer writes:
>> I have a file called bio-hoja4%ftag_EDO Uwe.pdf
>>
>> I use helm-locate and type %ftag_
>> but I receive nothing found see the screenshot.
>>
>>
>> helm-min
>>
>> And typing %ftag also does not work,
>>
>> What do I miss?
> Ah, sorry, I thought you used helm-locate before. helm-locate depends on
> the GNU/Linux 'locate' program. You have to install it. I don't know
> what distro you use, but the package is usually called mlocate or
> plocate (these are two different implementations of locate). I have
> mlocate installed on Arch Linux. According to the Arch wiki:
> ------------
> - mlocate (Merging Locate) is a more secure version of the locate utility,
> that only shows files accessible to the user.
> - plocate (Posting Locate) is a locate based on posting lists, consuming
> mlocates database ahead-of-time and making a much faster (and smaller)
> index out of it.
> ------------
> Generally, when you install locate it is automatically configured so
> that the database is updated every time you start a session. If you want
> to update it in the middle of a session, you must execute the updatedb
> command with sudo in the terminal.
Ah, well I have installed locate (mlocate to be precise, I am using
Ubuntu)
And I have used locate in the past, nevertheless
helm-locate keeps failing and giving me the screenshot I attached in my
earlier message, so some sort of bug in helm-locate for Ubuntu?
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-10-30 19:23 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
2022-10-30 18:48 ` Uwe Brauer
2022-10-30 19:04 ` Juan Manuel Macías
2022-10-30 19:21 ` Uwe Brauer [this message]
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=87h6zlglrf.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
/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).