From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36830@debbugs.gnu.org
Subject: bug#36830: 26.2; find-file-visit-truename is not honored as file local variable
Date: Fri, 23 Aug 2019 10:04:48 -0300 [thread overview]
Message-ID: <87h8688233.fsf@gmail.com> (raw)
In-Reply-To: <87ftlsfp3v.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
Hi Lars,
thank you for looking into this.
On Fri, Aug 23 2019, Lars Ingebrigtsen wrote:
>
> Could you include the contents of this file?
Sure. The file from which I reported, and which I include here now, was
just a dummy file with the variable of interest set to true with
`add-file-local-variable`:
#+name: TargetFile.txt
#+begin_example
;; Local Variables:
;; find-file-visit-truename: t
;; End:
#+end_example
(Also in annex)
As I send you this now, I realize I should perhaps have chosen some
other file format for the report, as text-mode does not have a
predefined comment syntax. I don’t know if this is relevant to the local
variables machinery. I suppose it isn’t, as my initial issue with this
arose in Org files, for which the comment syntax is clear. But if some
adjustments on the report for a more proper setting are somehow
desired/relevant, let me know.
Best regards,
Gustavo.
[-- Attachment #2: TargetFile.txt --]
[-- Type: text/plain, Size: 60 bytes --]
;; Local Variables:
;; find-file-visit-truename: t
;; End:
next prev parent reply other threads:[~2019-08-23 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 15:21 bug#36830: 26.2; find-file-visit-truename is not honored as file local variable Gustavo Barros
2019-08-23 5:05 ` Lars Ingebrigtsen
2019-08-23 13:04 ` Gustavo Barros [this message]
2019-08-23 18:59 ` Lars Ingebrigtsen
2019-08-23 20:07 ` Eli Zaretskii
2019-08-23 21:38 ` Gustavo Barros
2019-08-25 5:39 ` Lars Ingebrigtsen
2019-08-25 7:31 ` Eli Zaretskii
2019-10-14 21:38 ` Lars Ingebrigtsen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8688233.fsf@gmail.com \
--to=gusbrs.2016@gmail.com \
--cc=36830@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.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).