#441 (feature request) avoiding to show the preview directory in the left toolbar

[Andrei Akhmetzhanov]

When I edit my page, I am used to preview it. If, while doing that, I choose to show the project directory from the left toolbar and open it in a new tab of my browser, I will be redirected to the preview directory rather than to the original directory. Would it be possible to change that and to redirect me to the original project? (I don't remember, but i had a small inconvenience with that)

ps: see the attachment

[Lee Worden]

Thank you! (Great graphics!)

With the current design, you can get to the preview version of the
project by clicking on the sidebar link, and you can get to the
persistent version by clicking the sidebar link and then clicking the
"special page" tab at the top of the project page.

If I were to make the sidebar link to the persistent version of the
project, I'm not clear how you'd be able to get to the preview copy...

[Jonathan Dushoff]

Alternatively, you can click "page" or "history" at the top of the edit page to get a non-preview view on the page. "history" is usually quick.

[Andrei Akhmetzhanov]

Thanks, I see

I am not sure why I need the directory for my preview session. Only in some rare cases.

[Lee Worden]

I use the preview directory pretty regularly. For example, when I'm
writing code for a new target in a makefile, I keep it in a preview
session while I test whether it's working - if it doesn't work, often I
want to delete the target file and hit preview to make it again.

[Anonymous]

I used to think that the preview directory was not useful, but Lee pointed out that you can try important experiments there. In particular, you can clear the working directory and make sure that all your make rules are chaining without losing all of your files.

Lee, I'm not sure why you're deleting a target to make it again; I rarely do that. Using fake dependencies (foo.mk; /proc/uptime) while developing is usually easier.

JD

[Lee Worden]

On 11/04/2013 04:39 PM, noreply@in.sf.net wrote:

Lee, I'm not sure why you're deleting a target to make it again; I
rarely do that. Using fake dependencies (foo.mk; /proc/uptime) while
developing is usually easier.

Your example is better. I was just thinking of mine because I'm working
on one today that has two dependencies named in the make rule, and uses
$^ to include them as command arguments:

 target : dep1 dep2
         command $^ > $@

so I didn't want to make it also depend on the command script or the
makefile. Easier to just delete and remake. Laziness on my part - I
know I could rewrite it to do it right. (Though, to be candid, I was
doing the delete-remake cycle at my laptop's command line, not in the
preview session.)