* bug#38308: INFO files changed on disk: mention rereading workaround
@ 2019-11-21 0:11 積丹尼 Dan Jacobson
2019-11-21 8:14 ` Robert Pluim
0 siblings, 1 reply; 4+ messages in thread
From: 積丹尼 Dan Jacobson @ 2019-11-21 0:11 UTC (permalink / raw)
To: 38308
(info "(info) Advanced") should add FAQ:
Q: What if the info files or top directory change on disk? Unlike
normal browsers INFO has no refresh command.
A: Kill the *info* buffer and start INFO again.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#38308: INFO files changed on disk: mention rereading workaround
2019-11-21 0:11 bug#38308: INFO files changed on disk: mention rereading workaround 積丹尼 Dan Jacobson
@ 2019-11-21 8:14 ` Robert Pluim
2019-11-21 13:04 ` Lars Ingebrigtsen
0 siblings, 1 reply; 4+ messages in thread
From: Robert Pluim @ 2019-11-21 8:14 UTC (permalink / raw)
To: 積丹尼 Dan Jacobson; +Cc: 38308
>>>>> On Thu, 21 Nov 2019 08:11:26 +0800, 積丹尼 Dan Jacobson <jidanni@jidanni.org> said:
積丹尼> (info "(info) Advanced") should add FAQ:
積丹尼> Q: What if the info files or top directory change on disk? Unlike
積丹尼> normal browsers INFO has no refresh command.
積丹尼> A: Kill the *info* buffer and start INFO again.
You donʼt have to kill the *info* buffer, you can just revert it. I do
that all the time when Iʼm writing info documentation, but I canʼt see
that being a common occurence in normal use.
Robert
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#38308: INFO files changed on disk: mention rereading workaround
2019-11-21 8:14 ` Robert Pluim
@ 2019-11-21 13:04 ` Lars Ingebrigtsen
2019-11-21 15:00 ` 積丹尼 Dan Jacobson
0 siblings, 1 reply; 4+ messages in thread
From: Lars Ingebrigtsen @ 2019-11-21 13:04 UTC (permalink / raw)
To: Robert Pluim; +Cc: 積丹尼 Dan Jacobson, 38308
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Thu, 21 Nov 2019 08:11:26 +0800, 積丹尼 Dan Jacobson
> <jidanni@jidanni.org> said:
>
> 積丹尼> (info "(info) Advanced") should add FAQ:
> 積丹尼> Q: What if the info files or top directory change on disk? Unlike
> 積丹尼> normal browsers INFO has no refresh command.
>
> 積丹尼> A: Kill the *info* buffer and start INFO again.
>
> You donʼt have to kill the *info* buffer, you can just revert it. I do
> that all the time when Iʼm writing info documentation, but I canʼt see
> that being a common occurence in normal use.
Yeah, I don't think this is a frequently asked question, so I'm closing
this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#38308: INFO files changed on disk: mention rereading workaround
2019-11-21 13:04 ` Lars Ingebrigtsen
@ 2019-11-21 15:00 ` 積丹尼 Dan Jacobson
0 siblings, 0 replies; 4+ messages in thread
From: 積丹尼 Dan Jacobson @ 2019-11-21 15:00 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: Robert Pluim, 38308
Dired says the file changed on disk, use g to...
Info doesn't.
Therefore dired shouldn't either.
Or info should at least add *one little itty bitty word* in its
documentation about the issue.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-11-21 15:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-21 0:11 bug#38308: INFO files changed on disk: mention rereading workaround 積丹尼 Dan Jacobson
2019-11-21 8:14 ` Robert Pluim
2019-11-21 13:04 ` Lars Ingebrigtsen
2019-11-21 15:00 ` 積丹尼 Dan Jacobson
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).