Jarmo Hurri <jarmo.hu...@syk.fi> writes: > Greetings John. > > John Hendy <jw.he...@gmail.com> writes: > >> This comes up all the time. > > Perhaps we could lower the frequency by making a small change to the > manual? > >> The key is to put it 1) before results (as you've done) and 2) to use >> a named source block (with #+name: foo above your babel code) so that >> Org knows what the results block actually is. Otherwise, as you >> currently have it, if you re-run the babel block, you'll keep the >> results section you already have and it will spit out another one >> below it since it no longer recognizes that the babel block and >> current, modified results block go together. > > Done. For some reason not doing 2) also worked correctly, but I agree > that it is still a good idea to name the blocks. >
Yes, Eric fixed that problem some months ago, so the urgency of naming code blocks has gone way down - but it should still be considered "best practice" imo. -- Nick
