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: [correction]
Date: Mon, 31 Oct 2022 13:55:42 +0100 [thread overview]
Message-ID: <87eduorw35.fsf@mat.ucm.es> (raw)
In-Reply-To: 87h6zkgp2d.fsf@posteo.net
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
>>> "JMM" == Juan Manuel Macías <maciaschain@posteo.net> writes:
> Uwe Brauer writes:
>> I see, thanks. Last most likely trivial question, where, in which file
>> does filetags save the relevant information, i.e tags
> I haven't looked at the code, but I imagine that the information is
> stored in the variables I mentioned before, when you use a controlled
> vocabulary for the tags. You can also store them in a .filetags file.
> See: https://github.com/DerBeutlin/filetags.el#usage
Thanks, just some comments.
I played bit with the format of the separators.
1. I don't want space in my file names, so I set
(setq filetags-delimiter-between-tags "_")
2. I want filetags-delimiter-between-filename-and-tags to be
- Clearly visiable
- Easily to find
- not in conflict with other programs.
- So I tried (setq filetags-delimiter-between-filename-and-tags
"_**_") not good for searching
- "_::_" is not very visiable
- "_##_" is in conflict with the latexviewers when you have
forward and backward search on in pdf files.
- "_&&_" seems to be ok but I am not entirely sure about it
Any comments?
Regards
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-10-31 12:58 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
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 ` Uwe Brauer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eduorw35.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.