@@ -169,25 +169,23 @@ will also work as GSAS-II is run directly from the git repo.
169169
170170.. tip ::
171171
172- If using pixi, be sure to use the ``pixi run install-editable `` command (Windows,
172+ If using pixi, be sure to use the ``pixi run install-editable `` command (on Windows,
173173 ``pixi run install-editable-win ``) to install GSAS-II. With ``pixi run install ``,
174174 because the files used to run GSAS-II are versions present when the install
175175 command was last run, not the latest versions. If you modified the repo
176176 files, you would need to rerun the ``pixi run install `` command to
177177 see the latest changes. Likewise, do not use pip to install GSAS-II for the
178178 same reasons.
179179
180- One could possibly modify the installed GSAS-II files, in a
181- directory along the lines of
182- ``.../pixi/.pixi/envs/default/Lib/site-packages/GSASII ``, but then
183- changed files would need to be copied over to the git repo and
184- would be at risk for an accidental overwrite if the install command
185- were used.
180+ While one could modify the installed GSAS-II files, in a directory along the lines of
181+ ``.../pixi/.pixi/envs/default/Lib/site-packages/GSASII `` during code development, but then
182+ the revised files would need to be copied over to the git repo to upload them and
183+ would be at risk for an accidental overwrite if the install command were used.
186184
187185Once GSAS-II is installed and is running, one uses git to change the
188186GSAS-II files over to the version in your copy of the repo. Before
189187doing that, note if you will be using `ssh or https access
190- <gitauthenticate> `_ to GitHub. With ssh access you will use these
188+ <# gitauthenticate> `_ to GitHub. With ssh access you will use these
191189commands::
192190
193191 cd GSAS-II
@@ -226,7 +224,7 @@ Install GSAS-II directly from your forked repo
226224
227225If you are on MacOS or Linux, you can use steps indicated in the `pixi
228226installer <install_pixi.html> `_ to install pixi. Again, knowing if you
229- will use `ssh or https access <gitauthenticate >`_ to GitHub. With ssh
227+ will use `ssh or https access <# gitauthenticate >`_ to GitHub. With ssh
230228access, the commands to download GSAS-II and install it and Python (as
231229well as compile) and will be::
232230
@@ -305,7 +303,8 @@ binaries, which can be done by copying the binary directory,
305303in the development installation. Alternately the GSASII-bin directory
306304can be moved to ``~/.GSASII `` (``%HOMEPATH%\.GSASII `` on Windows).
307305
308- Running the development version of GSAS-II
306+
307+ Running the development version of GSAS-II
309308----------------------------------------------------------------------------
310309
311310If GSAS-II is run from a directly installed version of Python or a
@@ -364,7 +363,7 @@ The command to do this is::
364363
365364 git checkout -b g2newfeature
366365
367- Note that this creates a branch named ``g2newfeature`` (do choose a better name.)
366+ Note that this creates a branch named ``g2newfeature `` (do choose a better name.)
368367
369368When your changes are complete and you are ready to communicate them
370369back, you will commit them locally and use ``git push `` to upload them
0 commit comments