On 27 January 2011 18:42, Jon Senior <[email protected]> wrote: > On Wed, 26 Jan 2011 20:23:50 -0500 > Randy Kramer <[email protected]> wrote: > >> Ok, from Neil's response to this thread, I see that there is a >> misunderstanding somewhere--I did not intend to say that the changes >> would be visible in both (or all) instances of the editor. >> >> But, that doesn't keep me from working on them just fine. >> >> (And, if I save the file in one instance of the editor after making >> changes, when I go to that file in an other instance of the editor, >> I'm warned that the file on disk doesn't match the one I'm about to >> edit, and I'm prompted to do things like reload the file. (Nedit is >> an example.)) > > geany will do the same (I've made use of this in the past. Open a log > file in geany then re-run the code that generates the file and geany > will ask me if I want to reload the file). As I understand things, you > can force a new instance of geany, and you could open a file in both > instances. Personally if I want to look at one part of a file and edit > another, I prefer to use something passive like "less", which is far > less prone to accidental overwriting. > > Jon
Hi Jon, You don't have to forgo Geany if you only want to read the file in another instance, just set Document->read only and you don't have to accept anything less (boom boom :-). The problems are when editing prefs/projects/files in more than one instance. Cheers Lex > _______________________________________________ > Geany mailing list > [email protected] > http://lists.uvena.de/cgi-bin/mailman/listinfo/geany > _______________________________________________ Geany mailing list [email protected] http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
