W*****7 发帖数: 830 | 1 用的TEXMAKER 和MIKTEX, 有没有简单点的TRACK change 的办法?多谢。 |
b*******t 发帖数: 33714 | 2 我想说命令行里用diff...
【在 W*****7 的大作中提到】 : 用的TEXMAKER 和MIKTEX, 有没有简单点的TRACK change 的办法?多谢。
|
p*********w 发帖数: 23432 | 3 就是软件源代码的版本管理吧
【在 W*****7 的大作中提到】 : 用的TEXMAKER 和MIKTEX, 有没有简单点的TRACK change 的办法?多谢。
|
i*****a 发帖数: 160 | 4 请问有能够像word那样子的track的吗?
多人协作上面 latex编辑器有些吃力呀 |
S**I 发帖数: 15689 | 5 use version control software, e.g. SVN.
【在 i*****a 的大作中提到】 : 请问有能够像word那样子的track的吗? : 多人协作上面 latex编辑器有些吃力呀
|
b*******t 发帖数: 33714 | 6 你可以用word编辑source code lol
【在 i*****a 的大作中提到】 : 请问有能够像word那样子的track的吗? : 多人协作上面 latex编辑器有些吃力呀
|
r****t 发帖数: 10904 | 7 wdiff, or git diff -colors-word, 最好 alias 成 wdiff
【在 b*******t 的大作中提到】 : 我想说命令行里用diff...
|
b*******t 发帖数: 33714 | 8 学习了
【在 r****t 的大作中提到】 : wdiff, or git diff -colors-word, 最好 alias 成 wdiff
|
r****t 发帖数: 10904 | 9 我也是才学来的,还写错了,是 git diff --color-words
在 ~/.gitconfig 里面加
[alias]
wdiff = diff --color-words
然后听说最好在 repository 下面写一个文件 .gitattributes, 里面加一行:
*.tex diff=tex
【在 b*******t 的大作中提到】 : 学习了
|
b*******t 发帖数: 33714 | 10 加的那行是做什么用的?
【在 r****t 的大作中提到】 : 我也是才学来的,还写错了,是 git diff --color-words : 在 ~/.gitconfig 里面加 : [alias] : wdiff = diff --color-words : 然后听说最好在 repository 下面写一个文件 .gitattributes, 里面加一行: : *.tex diff=tex
|
r****t 发帖数: 10904 | 11 git 内置了一些关于 latex 的知识,加了 gitattributes 以后,diff 的时候应该会
在 hunk header 里面告诉改动发生在哪个 section, 不过我没有验证。 这个是 man
gitattributes, 里面还建议 *.bib diff=bibtex
Each group of changes (called a "hunk") in the textual diff output is
prefixed with a line of the form:
@@ -k,l +n,m @@ TEXT
This is called a hunk header. The "TEXT" portion is by default a
line that begins with an alphabet, an underscore or
a dollar sign; this matches what GNU diff -p output uses. This
default selection however is not suited for some
contents, and you can use a customized pattern to make a
selection.
First, in .gitattributes, you would assign the diff attribute for
paths.
*.tex diff=tex
Then, you would define a "diff.tex.xfuncname" configuration to
specify a regular expression that matches a line that
you would want to appear as the hunk header "TEXT". Add a section
to your $GIT_DIR/config file (or $HOME/.gitconfig
file) like this:
[diff "tex"]
xfuncname = "^(\\(sub)*section\{.*)$"
Note. A single level of backslashes are eaten by the
configuration file parser, so you would need to double the
backslashes; the pattern above picks a line that begins with a
backslash, and zero or more occurrences of sub
followed by section followed by open brace, to the end of line.
There are a few built-in patterns to make this easier, and tex is
one of them, so you do not have to write the above
in your configuration file (you still need to enable this with
the attribute mechanism, via .gitattributes). The
following built in patterns are available:
【在 b*******t 的大作中提到】 : 加的那行是做什么用的?
|
b*******t 发帖数: 33714 | 12 认真学习中...
a
【在 r****t 的大作中提到】 : git 内置了一些关于 latex 的知识,加了 gitattributes 以后,diff 的时候应该会 : 在 hunk header 里面告诉改动发生在哪个 section, 不过我没有验证。 这个是 man : gitattributes, 里面还建议 *.bib diff=bibtex : Each group of changes (called a "hunk") in the textual diff output is : prefixed with a line of the form: : @@ -k,l +n,m @@ TEXT : This is called a hunk header. The "TEXT" portion is by default a : line that begins with an alphabet, an underscore or : a dollar sign; this matches what GNU diff -p output uses. This : default selection however is not suited for some
|