Detect a line in a file and then edit it

xuanbao · · 366 次点击

这是一个分享于的资源，其中的信息可能已经有所发展或是发生改变。

Hi everyone, I'm trying to go through a file through a Scanner or a Reader line by line, then check if each line matches a certain pattern. Once this is done, I'd like to record the position of the line to edit it, but file.Seek(0,1) doesn't work well, as Scanner and Reader are buffered and will only show the position of their buffer (every 4096 bytes if I'm not wrong) which does not help a lot. Any idea about how I could tackle that? Thank you! Edit: why the downvotes, did I miss something? <hr/>**评论：** TheMerovius: <pre>You can simply <a href="https://play.golang.org/p/71SU2zAw1oe" rel="nofollow">count the bytes</a> you get from the Scanner. This still has a caveat, though, if you have non-unix line endings. A way around that is to supply <a href="https://play.golang.org/p/pc27YHolgfv" rel="nofollow">your own SplitFunc</a> and have that take track -- but I found the SplitFunc API to be somewhat hard to use and it includes a bunch of subtleties. Be aware, that the code I linked isn't actually well-tested, so it might be totally wrong. Also, as others have pointed out, keep in mind that editing files is non-trivial, unless your replacements are 1:1 in number of bytes. Like, if you want to delete (or shorten) a line, you'd have to move all bytes after that line forward and truncate the file. If you want to insert text, you have to actually take care of buffering the overwritten contents. Like, in a sense, files behave like <code>[]byte</code>: You can <code>append</code>, you can <code>copy</code>, but you can't delete or insert (and the <a href="https://github.com/golang/go/wiki/SliceTricks#insert" rel="nofollow">common tricks</a> for slices use the fact that the language will hide a bunch of the book-keeping and buffering for you, which you'll have to do manually). Of course, if you'd change the length of a file, you'd also invalidate all the other line-offsets after it. So, unless you always want to do 1:1 replacement, it's far easier, more sensible and probably just as performant, to write a new file line-by-line and rename it over the old one.</pre>Vaglame: <pre>Oh thank you very much that's exactly what I was looking for!</pre>iCurlmyster: <pre>If I understand your question correctly you could open it as an *os.File object and use WriteAt. I mean you would have to record the byte position though</pre>Vaglame: <pre>Thanks for the answer. It's not exactly the writing part that bothers me, it is the reading part. I have found no way to keep track of the actual position when reading a file with a Scanner or a Reader. For example if I have two lines <pre><code>this is line one this is line two </code></pre> and I do scanner.Scan(), even if I only get the text of the first line, the file.Seek methods returns the offset of the end of the file.</pre>iCurlmyster: <pre>Oh okay, yeah, I read it wrong then. The only thing I can think of right now is you could keep track of how many bytes you are reading with Reader.Read. But other than that I can’t think of anything off the top of my head with scanner, but I also don’t claim to be a golang guru. Sorry I can’t be more help than that.</pre>Vaglame: <pre>I'll give it a try, thanks :)</pre>albatr0s: <pre>It's much easier to open a second file and write the results there, once you are done you just rename it.</pre>shovelpost: <pre>You could use <a href="https://golang.org/pkg/bufio/#example_Scanner_lines" rel="nofollow">Scanner</a> which by default reads the input as a set of lines.</pre>Vaglame: <pre>Yes but it reads it using a buffer, which makes it very difficult to record its actual position in the file, so far I haven't found a seek() function that could say what the Scanner has read so far. In short I'm looking for something like this: <a href="https://golang.org/pkg/text/scanner/#Scanner.Pos" rel="nofollow">https://golang.org/pkg/text/scanner/#Scanner.Pos</a>, but for bufio.</pre>shovelpost: <pre><blockquote> I'm trying to go through a file through a Scanner or a Reader line by line, then check if each line matches a certain pattern. Once this is done, I'd like to record the position of the line to edit it </blockquote> It might be helpful to tell us why you want to do this. Manipulating files has never been the easiest of tasks. Depending on what you are trying to achieve there might be a better way.</pre>Vaglame: <pre>I'm trying to keep a record of ip adresses of a few devices. I write them in a file with this format: <pre><code>device1 address1 device2 address2 </code></pre> etc. So, every time this address changes, I (try to) update this information in the file</pre>shovelpost: <pre><blockquote> I'm trying to keep a record of ip adresses of a few devices. I write them in a file with this format: <pre><code>device1 address1 device2 address2 </code></pre> etc. So, every time this address changes, I (try to) update this information in the file </blockquote> Based on what you said, I can't see any good reason to save the information in a file. You're only making your life harder. Save yourself from all the trouble and use an embedded database like <a href="https://github.com/boltdb/bolt" rel="nofollow">Bolt</a>.</pre>Vaglame: <pre>I'll give it a try, thank you :) </pre>tgaz: <pre>If your file is line-based text, you usually don't edit in-place since line lengths generally change (as <a href="/u/albatr0s" rel="nofollow">/u/albatr0s</a> points out)... So for a generic "framework/scaffolding" for this problem, I'd use the scanner and output the result to a new temporary file, and when you hit the thing you want to change, you output that instead while discarding the input. Then rename the temp file to the old file. Remove the temp file on error (use a <code>defer</code> and just ignore the error). Oh, and I have no idea why you were downvoted. Maybe because the question is about a trivial problem and better suited for StackOverflow or such. But the downvoting feels like it breaks the first subreddit rule.</pre>Vaglame: <pre>Thanks a lot. Would you consider this solution even if the file must accessed to relatively frequently? </pre>tgaz: <pre>It's the only sane option in a POSIX environment, so yes. Depends on the file size, I guess. But if you care about performance, you should probably not be using a text format anyway. More importantly, it's the only atomic way of modifying a file, which solves concurrency correctness. Just use a buffered writer, or you might pay a penalty for writing the small <code>Scanner</code> fragments.</pre>Vaglame: <pre>What format would you advise instead of the text one? </pre>tgaz: <pre>That's impossible to say without knowing your use-case. If this is data you have to interface with some other system, you may of course not have a choice. I've never had the need to modify a text file from Go. For quick things, I'd normally use a Shell script with <code>awk</code> or <code>sed</code>, or a Python script. Manipulating text in Go isn't that bad, but for simple text file manipulation, Python code is definitely nicer.</pre>0xjnml: <pre><code>sed</code></pre>