Uwe Brauer writes:
> I am not talking about commit messages, I am talking about ChangeLogs.
> So I still did not understand how you generated that org file.
Ah, I think you were confused by the name of the file: I wrote that
file, 100% manually :)
Best, Arash
branch: master
commit 03793072c1d05b01023ddf8efb57afc89f172e1e
Author: Arash Esbati
Commit: Arash Esbati
* tex.el (TeX-command): Adjust macOS version and name.
---
tex.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tex.el b/tex.el
index 053a0ade..c905981d 100644
---
>>> "AE" == Arash Esbati writes:
> Uwe Brauer writes:
>> Two questions:
>>
>> 1. is there any tools that convert the classical (Emacs) Changelogs
>> to the org style changelos?
> What do you mean by "org style changelogs"? Nowadays, ChangeLogs are
> generated from the commit messages. Such
Hi Arash,
> Arash Esbati writes:
>> 2. After C-c C-c LaTeXMK, in dvi+dvips case, C-c C-c View offers xdvi,
>> not postscript viewer, as default candidate. Similarly, in
>> dvi+dvipdfmx case, C-c C-c offers Dvipdfmx, not View, as default
>> candidate.
> Yes, I can confirm this. I also tried
Uwe Brauer writes:
> Two questions:
>
> 1. is there any tools that convert the classical (Emacs) Changelogs
> to the org style changelos?
What do you mean by "org style changelogs"? Nowadays, ChangeLogs are
generated from the commit messages. Such a converter wouldn't make
sense,
Tassilo Horn writes:
> It's basically a fineer-grained version of changes.texi, right?
Yes.
> So basically we could write CHANGELOG.org and summarize that in
> changes.texi before a tarball release.
Again, yes, that was my thinking.
> Well, but then the changes in the manual would be
> Arash Esbati writes:
> I did some more research on this and like to make this suggestion: We
> should add a file called 'CHANGELOG.org' to our repo and mention our
> changes there. I suggest to follow the conventions from 'keep a
> changelog'[1]; I think this is a good solution for end
Arash Esbati writes:
>> Thanks. I briefly had a look at other ELPA packages and it seems
>> there is a variety of options: ASCII files, markdown, org files. So
>> we could install a new file CHANGES.org and use that.
>
> I did some more research on this and like to make this suggestion: We
>
