|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Andres Freund <andres(at)anarazel(dot)de>|
|Cc:||Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Typo: llvm*.cpp files identified as llvm*.c|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2019-01-23 12:01:10 +0900, Michael Paquier wrote:
>> I am not sure if anybody uses them for anything automatically, still I
>> find myself from time to time looking at them to remember on which
>> path the file is located when opened in emacs.
> I often want to know that too - isn't it easier to just meta-x f and see
> the directory displayed? Because that doesn't require jumping to the
> head of the file...
My own workflow often involves editing copies that are not in the original
directory, so that answer doesn't work for me. In general it won't work
anytime you are looking at a file out-of-context.
regards, tom lane
|Next Message||Alvaro Herrera||2019-01-23 16:58:07||Re: ArchiveEntry optional arguments refactoring|
|Previous Message||Andres Freund||2019-01-23 16:51:50||Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory|