Commits

Matthew Turk committed 67134a1

Some minor fixes to development docs.

  • Participants
  • Parent commits 9b0df93
  • Tags 2.3, 2.3-build1

Comments (0)

Files changed (1)

File source/advanced/developing.rst

 
 If you just want to *look* at the source code, you already have it on your
 computer.  Go to the directory where you ran the install_script.sh, then
-go to ``<INSTALL_DIR>/src/yt-hg`` .  In this directory are a number of 
+go to ``$YT_DEST/src/yt-hg`` .  In this directory are a number of 
 subdirectories with different components of the code, although most of them
 are in the yt subdirectory.  Feel free to explore here.  If you're looking
 for a specific file or function in the yt source code, use the unix find 
 
 .. code-block:: bash
 
-   $ find <DIRECTORY_TREE_TO_SEARCH> -exec grep <KEYWORD_TO_FIND> '{}' \; -print
+   $ grep -R <KEYWORD_TO_FIND> <DIRECTORY_TREE_TO_SEARCH>
 
 This can be very useful for tracking down functions in the yt source.
 
 
 .. code-block:: bash
 
-   $ ``cp <INSTALL_DIR>/src/yt-hg/*.cfg <REPOSITORY_NAME>``
+   $ cp $YT_DEST/src/yt-hg/*.cfg <REPOSITORY_NAME>
 
 and then every time you want to "activate" a different repository of yt.
 
 After running these commands on your local testing copy of yt, you will
 want to use this testing yt as your default (at least temporarily) so that
 you can test how this version of yt behaves with whatever testing scripts.
- You can "activate" it by going into the new yt-testing directory and
-running:
+You can "activate" it by going into the new yt-testing directory and running:
 
 .. code-block:: bash