From: Eric Wong <e@80x24.org>
To: spew@80x24.org
Subject: [PATCH] readahead: handle queued commands properly
Date: Sat, 5 Nov 2016 01:04:51 +0000 [thread overview]
Message-ID: <20161105010451.23724-1-e@80x24.org> (raw)
We can't do much for readahead when it comes to dtas-player
running arbitrary commands.
---
bin/dtas-readahead | 1 +
1 file changed, 1 insertion(+)
diff --git a/bin/dtas-readahead b/bin/dtas-readahead
index b4b7311..6034763 100755
--- a/bin/dtas-readahead
+++ b/bin/dtas-readahead
@@ -133,6 +133,7 @@ def do_ra(fp, pos, w)
end
def do_open(path)
+ return unless path # could be a command
if path =~ /\.ya?ml\z/
File.open(path) do |fp|
buf = fp.read(4)
--
EW
reply other threads:[~2016-11-05 1:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20161105010451.23724-1-e@80x24.org \
--to=e@80x24.org \
--cc=spew@80x24.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.
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).