Commits

Peter Szilagyi committed 5c753aa

updated to-do

  • Participants
  • Parent commits b6aa440

Comments (0)

Files changed (1)

 I just moved a directory for a project that was building. Now I can
 not kill the project, because omake-mode complains that it cannot set
 the current directory to the now-gone directory.
-** Omake.setenv doesn't work when the compile isn't running
-*** nchapman:
-On Fri, Jan 4, 2013 at 7:00 AM, Nick Chapman <nchapman@janestreet.com> wrote:
-
-Files: ldn-qws-003.delacy.com:/tmp/omake-server/nchapman/bug-report/1
-
-User report:
-
-Omake.setenv doesn't work when the compile isn't running.
-Says something like: \"mo model for project ...\"
-
-But start the compile & all is okay!
-*** pszilagyi:
-I agree that this behavior is confusing.  Given some of the changes
-we've made recently, it should be possible to implement this again,
-saving the settings until the compilation is started.
 ** save commented-out defaults in ~/.omake-server/config
 *** pszilagyi:
 Nuffer points out that it was nice having defaults saved, so you could
 
 (like dired)
 
+** Omake.setenv doesn't work when the compile isn't running
+*** nchapman:
+On Fri, Jan 4, 2013 at 7:00 AM, Nick Chapman <nchapman@janestreet.com> wrote:
+
+Files: ldn-qws-003.delacy.com:/tmp/omake-server/nchapman/bug-report/1
+
+User report:
+
+Omake.setenv doesn't work when the compile isn't running.
+Says something like: \"mo model for project ...\"
+
+But start the compile & all is okay!
+*** pszilagyi:
+I agree that this behavior is confusing.  Given some of the changes
+we've made recently, it should be possible to implement this again,
+saving the settings until the compilation is started.