[issue16814] use --directory option of make in describing how to build the docs

Éric Araujo added the comment: LGTM. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue16814] use --directory option of make in describing how to build the docs

Chris Jerdonek added the comment: I went ahead and committed this if that's okay. I wasn't sensing any strong objection but -0 from some and +1 or +0 from others. To compensate for the extra six words, I went ahead and first made the current language more concise here: http://hg.python.org/

[issue16814] use --directory option of make in describing how to build the docs

Roundup Robot added the comment: New changeset 5f24a77e7beb by Chris Jerdonek in branch 'default': Issue #16814: add "make -C Doc html" short-cut to documentation instructions. http://hg.python.org/devguide/rev/5f24a77e7beb -- nosy: +python-dev ___ Py

[issue16814] use --directory option of make in describing how to build the docs

Ezio Melotti added the comment: > I frequently go back and forth between `make html` and `hg diff`. Mercurial commands work on the whole repo, regardless on the dir you are in (unlike SVN ones). That's why I usually just cd in Doc/ and do everything (opening files with editor/browser, make *,

[issue16814] use --directory option of make in describing how to build the docs

Chris Jerdonek added the comment: For the record, we do have tutorial-like documentation and document more than one way to do things in multiple places throughout the devguide. For example: http://docs.python.org/devguide/faq.html#how-do-i-list-the-files-in-conflict-after-a-merge Unlike the s

[issue16814] use --directory option of make in describing how to build the docs

Éric Araujo added the comment: FWIW I use make -C Doc all the time but agree with Georg’s point about conciseness. Ezio, I suggest you bookmark some make doc page if you can’t remember it :) -- nosy: +eric.araujo ___ Python tracker

[issue16814] use --directory option of make in describing how to build the docs

Senthil Kumaran added the comment: I find, cd Doc easy to remember as well. If make tricks can be used then I hope readers note it rather than be exposed via Documentation. Chris's patch is helpful to me, but still I may not vote a +1 for it to be in Documentation. thanks. On Sun, Dec 30, 2012 a

[issue16814] use --directory option of make in describing how to build the docs

Ezio Melotti added the comment: FWIW even if I heard about the one-liner a few times already I can't really seem to remember it, and prefer to do "cd Doc" anyway. Using "cd Doc" also makes all the subsequent commands shorter (e.g. opening files, running other make targets). The patch proposed

[issue16814] use --directory option of make in describing how to build the docs

Georg Brandl added the comment: Well, I'm not -1 about the patch. But there is something to be said for conciseness, and sprinkling the docs with endless alternate routes will not make it easier to read quickly and get the information you need. --

[issue16814] use --directory option of make in describing how to build the docs

Tshepang Lekhonkhobe added the comment: > This is not a `make' tutorial... I find the latest patch to be a great compromise though. Many people would be grateful to learn about the -C option. I am one of them. -- ___ Python tracker

[issue16814] use --directory option of make in describing how to build the docs

Georg Brandl added the comment: This is not a `make' tutorial... -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue16814] use --directory option of make in describing how to build the docs

Chris Jerdonek added the comment: > Another option is to give the shorter option as an alternative. s/shorter option/one-liner/ -- ___ Python tracker ___ ___

[issue16814] use --directory option of make in describing how to build the docs

Chris Jerdonek added the comment: Another option is to give the shorter option as an alternative. I for one didn't know about that option but would have liked to. Patch attached. Also, this way we can give the shorter option and the reader can still see pretty easily what it is for. ---

[issue16814] use --directory option of make in describing how to build the docs

Georg Brandl added the comment: Agree with David. -- nosy: +georg.brandl status: open -> closed ___ Python tracker ___ ___ Python-bugs

[issue16814] use --directory option of make in describing how to build the docs

Changes by R. David Murray : -- title: use --directory option of make -> use --directory option of make in describing how to build the docs ___ Python tracker ___ __

[issue16814] use --directory option of make

R. David Murray added the comment: I think the fact that the cd paradigm is more commonly encountered is a fairly strong argument in favor of keeping it, but I'm only -0 on this change. -- nosy: +r.david.murray ___ Python tracker

[issue16814] use --directory option of make

Tshepang Lekhonkhobe added the comment: I like long-form options for documentation purposes since it's clearer what the option is for. -- ___ Python tracker ___ _

[issue16814] use --directory option of make

Sandro Tosi added the comment: i'd use make -C Doc html much more compact and what you would usually find on the internet for "cd into the dir and run the html target in it" -- nosy: +sandro.tosi ___ Python tracker

[issue16814] use --directory option of make

New submission from Tshepang Lekhonkhobe: This avoids having to run 2 separate commands. -- components: Devguide files: make-can-specify-build-directory.diff keywords: patch messages: 178495 nosy: ezio.melotti, tshepang priority: normal severity: normal status: open title: use --director