| bio | website | fa.its.tudelft.nl/~teuwen |
|---|---|---|
| location | Delft, Netherlands | |
| age | 26 | |
| visits | member for | 2 years, 6 months |
| seen | May 1 at 14:26 | |
| stats | profile views | 103 |
About me
I'm a PhD candidate in analysis (harmonic analysis). I have a Master of Science degree in mathematics (analysis).
I am interested in many topics in analysis, but in particular: harmonic analysis, functional analysis, operator theory and special functions.
My email address is jonasteuwen@gmail.com.
I would appreciate it if you would correct my spelling and grammatical errors.
Me elsewhere
|
Oct 17 |
accepted | Automatic branching for versions and git |
|
Oct 17 |
comment |
Automatic branching for versions and git Thank you! This is helpful. Also thanks for not forgetting it :-). |
|
Oct 9 |
comment |
Automatic branching for versions and git The idea is that I only modify the main file and the generated files do not have the goal to be merged (otherwise I could use latexdiff if I really wanted to), but more to send to people so they can start working on it. More like a fork. Most mathematicians do not use git. |
|
Oct 9 |
comment |
Automatic branching for versions and git Perhaps, as I use emacs anyway, Org-mode is the way to go... |
|
Oct 9 |
comment |
Automatic branching for versions and git @Seamus The fact that simple conditions are fine to compile different versions, but I not only want simple conditions, I also want the content removed when it is put in another branch. The .tex should not contain the stuff which does not satisfy the conditional. Those different ones could be put in another branch. |
|
Oct 8 |
comment |
Automatic branching for versions and git @Brent.Longborough I am looking forward to it :-). |
|
Oct 8 |
comment |
Automatic branching for versions and git Thanks. I have added a possible workflow! I hope it makes more sense now. |
|
Oct 8 |
revised |
Automatic branching for versions and git added 822 characters in body |
|
Oct 8 |
asked | Automatic branching for versions and git |
|
Sep 13 |
awarded | Popular Question |
|
Aug 9 |
comment |
Dynamically size arrow \mapsto in function definition Thanks. This a nice answer. I use mathtools already, so I will remember this. |
|
Jul 22 |
accepted | Testing if \BODY is empty in Environ |
|
Jul 22 |
comment |
Testing if \BODY is empty in Environ Great. This is what I have changed in the end! I also added the capitalize of the stringstring package. One issue was that I would like to mix the commands makesection and defenviron. The problem is of course that after multiple inputs I will get errors! Perhaps I need to have a test that checks if this is already done. After that I can iterate over an etoolbox list. That worked but gave errors about something not being found while it was typeset. In any case, that would be a new question! |
|
Jul 22 |
revised |
Testing if \BODY is empty in Environ added 297 characters in body |
|
Jul 22 |
revised |
Testing if \BODY is empty in Environ added 342 characters in body |
|
Jul 22 |
revised |
Testing if \BODY is empty in Environ Removed the \ignorespaces |
|
Jul 22 |
comment |
Testing if \BODY is empty in Environ @David: Thanks. I think I have fixed it now. So I remove \ignorespaces and fix it elsewhere? What test would work? |
|
Jul 22 |
comment |
Testing if \BODY is empty in Environ Should be working now. |
|
Jul 22 |
revised |
Testing if \BODY is empty in Environ Fixed the missing `}` and removed an irrelevant line. |
|
Jul 22 |
comment |
Testing if \BODY is empty in Environ My apologies,I manually shortened the file. Will fix it in a couple a hours when I can access a real computer. |