« first day (2219 days earlier)      last day (2700 days later) » 

7:57 AM
^.how can i latex something like this, but with thin lines and not so blurry
 
8:45 AM
@Null A simple tabular with lines: what have you tried?
@PauloCereda I've got a Fedora VM set up (largely for a 'safe' place to use Python3 for something): looks quite good
 
@JosephWright the normal tabels are way too small, is there an already "big" template?
 
@Null I don't follow: is the only issue that you want to make it bigger than normal?
 
@JosephWright mmh, i guess yes, in addition that the text is bigger too.
 
9:43 AM
Yay: finally migrated beamer to GitHub
 
10:11 AM
Morning @DavidCarlisle
 
@JosephWright morning
@Null \fontsize{5cm}{6cm}\selectfont how big do you want?
@JosephWright was there some automatic tool to port issues etc or did you have to re-enter them?
 
@DavidCarlisle Automatic tool: finally got it working! (The other stuff was all moved by hand but with far fewer issues to shift)
@DavidCarlisle One 'interesting' point: for some reason, issue #140 is missing on BitBucket which confused the script a bit, took a couple of attempts to get everything across
 
@JosephWright ah. s/loose/lose/
 
@DavidCarlisle Fixed
@DavidCarlisle Script has a pull request which I think would have dealt with my 'gap' automatically: if I did it again, I'd grab the fork
@DavidCarlisle Meanwhile, actually making progress on siunitx v3 (mainly due to prodding by @egreg)
 
10:42 AM
I see Frank's published the latest news
 
 
1 hour later…
11:45 AM
@DavidCarlisle I see our user from the north asked a nice question again :-)
 
@Johannes_B :(
 
@DavidCarlisle The question is deleted
Oh, he asked many questions these days. Gotta have a quick read :-)
 
@Johannes_B that would be an improvement:-)
 
In other news. I was going to a concert yesterday. It was really really great. vvvvvvvv
Not the music @barbara or @egreg would apprecate, but maybe @Paulo likes it :-)
@Masi As usual, I cannot read your mind. — egreg 2 days ago
@egreg ^^ :-)
Oh for heavens sake?
0
Q: How to fix this abnormal second line of reference with Vancouver style?

MasiThere is a strange second line in the output of Fig. 1 where dot at the beginning of the line and big space. Code but with Vancouver style leads to the output in Fig. 1 \documentclass[english,12pt,a4paper,pdftex,sci,utf8]{aaltothesis} % https://wiki.aalto.fi/display/Aaltothesis/Aalto+Thesis+LaT...

2
Q: How to cite a DynaMed publication correctly using the "vancouver" bibliography style

MasiI am trying to the cite the following thing correctly. I have these instructions. How to cite: National Library of Medicine, or "Vancouver style" (International Committee of Medical Journal Editors): DynaMed Plus [Internet]. Ipswich (MA): EBSCO Information Services. 1995--. Record N...

 
12:32 PM
I see the move to GitHub has already attracted @samcarter's attention ;)
Anyone used Projects on GitHub?
@PauloCereda perhaps?
 
@JosephWright Hi! No idea of what it is. :)
@Johannes_B ooh
 
@PauloCereda Like Trello, I think
 
@JosephWright Great to hear! Have fun! :)
@JosephWright Oh I saw those card thingies. Not tried them, though.
 
12:52 PM
@PauloCereda She did wear a Dirndl yesterday. :-)
 
1:35 PM
I was wondering whether we can convince Victor Eijkhout to leave that Quora place and join us here on TeX-SX.
Does anyone have a personal correspondence with him?
 
@percusse Maybe if one could pronounce his last name correctly. :)
 
@PauloCereda its eykhaut with a very open E in the beginning as in ...aaaand.... @AlanMunn a bit help ?
 
@percusse related:
Eyjafjallajökull (Icelandic pronunciation [ˈeɪjaˌfjatlaˌjœːkʏtl̥]), English Eyjafjalla Glacier, is one of the smaller ice caps of Iceland, north of Skógar and west of Mýrdalsjökull. The ice cap covers the caldera of a volcano with a summit elevation of 1,651 metres (5,417 ft). The volcano has erupted relatively frequently since the last glacial period, most recently in 2010. == GeographyEdit == Eyjafjallajökull consists of a volcano completely covered by an ice cap. The ice cap covers an area of about 100 square kilometres (39 sq mi), feeding many outlet glaciers. The main outlet glaciers are to...
:)
 
@PauloCereda :) Yes but slightly more logical
 
@percusse oooh :)
 
1:39 PM
He seems to enjoy answering questions so maybe we can get another big shot among the ranks :)
Just ration the oxygen for our resident wizards eheheh
 
@JosephWright Cool, it's a way to organize issues.
 
@PauloCereda Quite possibly: I'm trying it out, really (see the beamer move)
 
@JosephWright :)
 
2:19 PM
It's so weird to see Sandi Toksvig hosting QI...
 
@JosephWright Now you are under my git radar too :D
 
@percusse I think you mean 'on', but one never knows ...
 
@JosephWright haha that was freudian i guess
 
@percusse o.O
 
@JosephWright By the way, I always wanted to switch to some pgfkeys syntax for beamer but starting from scratch I was quickly exhausted.
Do you have a strategy for layering the work ?
Especially colors are really bugging me since day 1
It would also break backwards compatibility instantly too but I think this time its worth the effort
 
2:35 PM
@percusse Not really following what you mean
 
3:10 PM
@JosephWright So instead of the templates using a \beamerset{...}, say, you have \usebeamercolor[fg]{alerted text}
It would be much more easier to use \pgfkeysvalueof{/beamer/color/foreground color}
In other words, changing the settings to a key-based framework
Or a shorthand notation, expandable \beamercolor{foreground}
 
4:06 PM
@JosephWright Is this expected?
\documentclass{article}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{expl3}

\begin{document}

\ExplSyntaxOn
\tl_mixed_case:n { école }
\ExplSyntaxOff

\end{document}
 
@egreg 'Works for me'
@egreg What are you getting?
 
@JosephWright I get
! Missing \endcsname inserted.
<to be read again>
                   \protect
l.9 \tl_mixed_case:n { école }
 
@egreg Oh, sorry: wrong engine
@egreg Yes, to-be-expected: you'd need to \protected@edef the input first to get it into a manageable LICR form
 
@JosephWright OK
 
@egreg Possibly this still needs more work: it gets complex trying to cover UTF-8 in pdfTeX fully!
 
4:22 PM
@JosephWright I understand. Anyway the code is working now. :-)
 
@egreg I think for most cases that are coming from existing 2e usage a two-part non-expandable route via \protected@edef is OK: does that sound right?
 
@JosephWright See updated answer at tex.stackexchange.com/questions/34796/…
 
@egreg Take that as a 'yes' :)
 
5:09 PM
@JosephWright Pull Request sent ;)
 
@percusse Indeed, already merged
 
@JosephWright I wish everything goes as quick as that. Thanks!
 
@percusse Translations tend to be pretty easy to accept ;)
@percusse Spent quite a bit of the day on beamer: I had a 'push' to get the issue tracking sorted, so wanted to get the GitHub move fixed, and once that was done felt I should triage the open issues
@percusse Planning at least a couple of releases over coming months
 
Hello guys. I have a quick question about inserting PDF pictures into LaTeX. It's not completely serious and therefore I do not want to ask it officially. Is that ok for the chat here?
 
Time to try out some GitHub features I've not used before ...
@Dr.ManuelKuehner You can always ask :)
 
5:15 PM
@JosephWright It would be also easy for us to get out of the way while you are fixing other parts.
 
@JosephWright Deadlines deadlines .... :)
 
Thanks. I made a fun picture that was inspired by a 9GAg post. Here in the German website/blog post I just created: manuelkuehner.de/2016/11/27/female-anatomy
In the PDF I see sometimes a tzhin border around the inserted picture depending on the zoom factor.
I already cropped the pucture using \includegraphics[width=120mm,trim=1mm 1mm 1mm 1mm, clip]{Frau.pdf}
 
@percusse Thought I should give myself some targets
 
5:17 PM
@Dr.ManuelKuehner Viewer glitches. That's normal. Happens with table rules as well.
 
@JosephWright Healthy amount of pressure is always productive
 
@Johannes_B Thanks. So I have to life with it. :()
 
@Dr.ManuelKuehner What kind of project is this?
 
@Johannes_B I released a new vidoe tutorial yesterday, I also mentioned the AND for multiple authors as u suggested
 
@Dr.ManuelKuehner You can put the picture inside a TikZ node. Then paint the borders with white overlapping the edges of the jpg. That would hide it.
 
5:19 PM
@Johannes_B BibLaTeX
 
@Dr.ManuelKuehner Oh, for a moment i thought the picture above would be the theme of the tutorial.
 
@percusse Thanks.
@Johannes_B Haha. No, I tried to improve this 9gag.com/gag/aG0DN0n
 
Or a very thick framebox overlapping the picture
 
\node[anchor=south west,inner sep=0] (image) at (0,0) {
	% texblog.org/2012/02/23/crop-figures-with-includegraphics
	\includegraphics[width=120mm,trim=1mm 1mm 1mm 1mm, clip]{Frau.pdf}
	};
This is how I do it atm
 
@Dr.ManuelKuehner Seems I have to log in to watch the content. I am not signed up there.4
 
5:21 PM
Wait. I send a screenshot
 
@Dr.ManuelKuehner :-)
 
That node would encapsulate the picture perfectly which also might be the problem since the picture could be leaking since you trim it. After the node add \draw[draw=white, linewidth=1mm] (image.south east) rectangle (image.north west);
That should paint over the border
 
@percusse I just tried \node[anchor=south west,inner sep=0,line width=3mm,draw=black] which didn't work.
If I choose white I still get the thin lines.
 
@Dr.ManuelKuehner That would still draw around the image. You need an overlapping rectangle. See my previous comment
 
I just saw
Thanks
Works!
 
5:28 PM
@Dr.ManuelKuehner Ah lucky shot :)
 
@percusse Thanks. I update the website now. Very cool of you.
Bye all together.
@Johannes_B Bye
 
@Dr.ManuelKuehner Glad to be of help. Bye
 
@Dr.ManuelKuehner Bye
 
 
2 hours later…
7:25 PM
Anyone using MacOS El Capitan?
Or earlier ...
 
7:52 PM
@JosephWright Here I am
 
@egreg Can you check latex-project.org from Safari?
 
@JosephWright There's advertising!
 
@egreg Yes, but that's to be expected (I'd forgotten about that as in my normal browser I of course avoid such things)
 
@JosephWright Which I killed
 
@egreg Key point is that it works at all
 
7:55 PM
@JosephWright I see no problem
 
@egreg Franks' been having some issues with an invalid certificate or something
 
@JosephWright I'm at halftime of Palmeiras' match.
 
@egreg I'm working on beamer bugs ;)
 
@JosephWright making them?
 
@JosephWright I'm anxious to see the new ones
 
7:57 PM
@DavidCarlisle S&* off
 
@JosephWright @egreg had same thought it seems
 
@DavidCarlisle Feel free to check over my checkins
@egreg Pull requests gratefully received: @percusse has already helped out today ;)
 
8:53 PM
@egreg, @DavidCarlisle Thus far mainly closing bugs as 'not my fault'
 
@PauloCereda Campeões!!!
 
user227867
I appreciate that the beamer and pgf manuals are very long. But sometimes I think, wouldn't it be better if it were short? Hmm...
 
@JasperLoy The problem with a 'quick start' guide is that whatever you put, someone things you've missed out the 'really important' thing they use all of the time ...
 
user227867
@JosephWright My favourite line in the movie Good Will Hunting is It's not your fault.
 
@JasperLoy It's not my fault is more the LaTeX team position ;)
 
user227867
8:59 PM
@JosephWright By the way, that is my favourite movie. I watch it all the time to keep myself alive.
 
user227867
After ten years or so, I am still deciding whether to learn pstricks or pgf in full. =P
 
user227867
However, at least I have finally bought More math into LaTeX.
 
user227867
I got the fifth edition published this year.
 
user227867
I am extremely surprised to find that this book is not listed at tug.org.
 
@JasperLoy Ooh, good idea: I have some Amazon vouchers to spend
 
user227867
9:02 PM
Maybe someone should put it there, together with a review.
 
@JasperLoy Mail Karl
 
user227867
@JosephWright Yes, it is a good time to get, since it just got published.
 
@JasperLoy Or ping @barbarabeeton
 
user227867
@JosephWright By the way, I already know that you are not a duck. =P
 
@JasperLoy Drat
 
9:12 PM
@egreg yaaaaaaaaaaaaaaaaaaaaaay! <3
 
9:27 PM
@JasperLoy that's obvious from the picture that he's not a real duck, unlike @PauloCereda
 
@DavidCarlisle Quack! <3
 
@PauloCereda dinner!
 
@DavidCarlisle oh no!
 
yo'
9:47 PM
Evening, everybody!
 
@JosephWright You might find this template useful for commits.
API: an (incompatible) API change
BLD: change related to building numpy
BUG: bug fix
DEP: deprecate something, or remove a deprecated object
DEV: development tool or utility
DOC: documentation
ENH: enhancement
MAINT: maintenance commit (refactoring, typos, etc.)
REV: revert an earlier commit
STY: style fix (whitespace, PEP8)
TST: addition or modification of tests
REL: related to releasing numpy
NumPy and SciPy people use it consistently. It's really good to figure out at the first look what you are looking at
 
@percusse Sounds far too organised for me, and it's in capitals! (I use those only for STATUS comments)
 
@JosephWright This is only meant for the initial letters of the commit
as in BUG: Avoid expansion of '\frame' in section name
 
@percusse Yes, I see that - uses up five of the letters one has available!
 
Well you have the commit description box for longer explanations :)
 
9:52 PM
@percusse I'm surprised they have BUG - I'd expect ... (fixes #n) (which is what I use when I remember)
@percusse Sure, but I find the one-liners hard enough as it is :)
 
Those links are converted automatically if you also include it in the commit descriptions. And also closes the issue. But I think you know that anyhow
 
@percusse The only formulaic thing I use at the mo' is for expl3 where we have Step version (CTAN snapshot) when things go to CTAN
 
yo'
@JosephWright I think they use both: BUG fixes #532 error in sqrt, I'm more surprised they call it BUG and not FIX
 
@percusse Yes, hence why I do it
@yo' Yes, but that's poor: doesn't say what's changed. I'd expect 'Altered XXX (fixes #n)`
@yo' This is also true
 
It has to be related to the cause :)
Everything is a fix
 
9:55 PM
@yo', @percusse I think one has to bear in mind that such approaches make sense with a larger team where there is some value, but less so when it's one person (or a small team)
@percusse See comments from @egreg and @DavidCarlisle above!
 
git commit -m "BUG: bla baasdf" -m "Description Closes #45346";
@JosephWright Hahah nevermind them :)
 
yo'
@JosephWright right, I'm aware of that and didn't mention it as it appears implicit to me here :-)
 
@yo' also look at the numbers of PRs and issues github.com/scipy/scipy/issues
That's just crazy. Numpy is even worse
 
@percusse Interesting: they favour --ff-only
 
@JosephWright Yes otherwise the merging would be a mess. They even want me to rebase before the merge so that only one commit msg shows up in the master branch
It is usually the other way around that you want all the increments
 
10:03 PM
@percusse Yes, I can see why they say it!
@percusse Rather like the LaTeX team 'one true version' approach :)
 
@JosephWright That and also one other problem:
 
yo'
@percusse 296 labeled defect
 
@JosephWright Imagine you did some nonconflicting changes and out of fanciness updates your fork with the latest changes from the remote. Then all those will get tagged as valid commits on your branch too
So when merging you reintroduce them and hell breaks loose (I did it that's how I know) :D
 
@percusse This I take your word for: my experience with Git is pretty limited (ask @DavidCarlisle)
 
@yo' Yes I think they are from the old days. You can also see the old issue numbers atteched to them when someone very clever moved the whole thing to GitHub
@JosephWright I wash my hands before and after. It's just a user-hostile thing.
There is a reason why this has this many votes :D
1699
Q: Undoing a git rebase

webmatDoes anybody know how to easily undo a git rebase? The only way that comes to mind is to go at it manually: git checkout the commit parent to both of the branches then create a temp branch from there cherry-pick all commits by hand replace the branch in which I rebased by the manually-created...

 
10:10 PM
@percusse I think I've said before that my feeling is Mercurial is easier to use but that realism suggests Git has won
 
@JosephWright When it is working, it is pretty flawless. It's just too damn difficult to understand the nerd-lingo. I'm sure you won't regret it.
 
@percusse My workflows are all basically SVN, just with easier (to me) tagging :)
 
yo'
@percusse +2 in last minute :-)
 
@JosephWright Can't compare due to absence of experience. With Travis CI I'm really relieved a lot. Testing was really bothering me.
Add Coveralls on top of it and I'm good to go
(or Circle CI)
@yo' :)
 
@percusse What does this do?
@percusse Travis CI very nice though again probably more use on bigger projects (does pick up stuff for L3 but not a major issue to do the same by hand)
 
10:20 PM
@JosephWright It's similar to Travis CI
random google search came up with it
 
I have a new palindrome reputation:
user image
2
 
yo'
10:46 PM
@Kurt Wait for @DavidCarlisle to explain you that it's not a palindrome.
 
@yo' I'm not so mean: you should do it
 
yo'
@DavidCarlisle that's your privilege :-)
 
@Kurt I think @yo' is worried that your comma is not centrally placed, compare with
 
@DavidCarlisle That is half evil :-)
 
@Johannes_B blame @yo'
@Johannes_B er half evil, twice: that makes....
 
yo'
11:09 PM
@Johannes_B s/,/+/
 

« first day (2219 days earlier)      last day (2700 days later) »