[bug #62934] [gropdf] sometimes \(em becomes a different char when rendered

[Deri James]

Follow-up Comment #5, bug #62934 (project groff):

I'm not sure what happened, both of my last commits were one liners where I
used kompare to change the single line which was relevent from my working copy
of gropdf. This is the workflow which I have always used:-

git stash
git pull
Run kompare to copy relavent changes to git version.
Make
Run test of current fix with test-groff.
Edit Changelog (copy text into clipboard).
git add Changelog gropdf.
git commit (copy clipboard).
git push
git stash pop

My "working copy" of gropdf is actually 1.22.4 which lives in /usr/bin.

I have always done this, without whitespace issues. One thought is a vim: line
has been added to the git copy of gropdf and something is adjusting the white
space to follow the vim settings when it saves the file, which would point at
kompare which probably shares code with the kde editor which I think does
parse modelines in files.

Do you have any idea how I can stop this happening?




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62934>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/