« first day (2098 days earlier)      last day (2827 days later) » 

1:05 AM
Finally :( Got a trouble and had to solve it :P
@DavidCarlisle Hahahaha!!! I hope, I'm happy to see people trying! :P
 
 
7 hours later…
7:54 AM
Hi TeX, LaTeX and Friends men
 
8:26 AM
@EnthusiasticStudent People ;-)
 
@JosephWright and ducks
 
8:51 AM
@DavidCarlisle and... Enthusiastic!
 
 
1 hour later…
10:20 AM
@barbarabeeton No need to apologize! After a long conference day, the brain is not guaranteed to be working until, perhaps, after a good dinner. :)
 
 
7 hours later…
5:00 PM
Last glass of wine on the train until September! :D
 
 
2 hours later…
6:30 PM
Ack from São Paulo!
Quack!
 
6:44 PM
@DavidCarlisle Does \extrarowheight not work in tabularx?
 
@AlanMunn yes
 
@DavidCarlisle Yes it does or yes it doesn't?
 
@AlanMunn oh didn't read your negated form: yes it works:-)
 
@DavidCarlisle Ok, thanks. I see now it does. I had just set the value too small.
 
@AlanMunn tabularx is just tabular with X being defined to be p{something}
 
6:47 PM
@DavidCarlisle Yes, that's what I thought, which is why I was surprised when it didn't seem to work.
 
7:26 PM
@DavidCarlisle ok thanks. I will look on this week-end
 
8:00 PM
@DavidCarlisle The cgloss4e package part of gb4e defines a couple of commands delimited by \\ . So the user syntax is \gll Line one \\ Line Two \\ . Can you think of a way to insert such code into a table cell?
 
Today I installed TeX Live 2016 ^_^
 
@DavidCarlisle Crucially the \\ are not newlines but simply the line delimiter. For example the \gll command begins its definition as \gdef\getwords(#1,#2)#3 #4\\ { ... }
@EnthusiasticStudent On what platform?
 
@AlanMunn windows
 
@EnthusiasticStudent You have my sympathies. :)
 
@AlanMunn why?
 
8:07 PM
@EnthusiasticStudent I'm a Mac user. :)
 
@EnthusiasticStudent Windows is not universally popular!
 
@JosephWright I tried to move to ubuntu... but it was too hard for me
moreover, most of the softwares in my country are windows-based
shifting to linux was like swimming against river's direction
 
@AlanMunn should just work?
@AlanMunn im on windows too (although since I use cygwin i can be in denial most of the time)
 
@DavidCarlisle Yes, I'm starting to see that. It works in a very simple example, but not in my real example (which is a tabularx inside an environment using the environ package.) So I'll need to dig further.
 
8:12 PM
@DavidCarlisle :) Yes, the idea that you would use Windows is so counterintuitive. Almost as if you were using vim like @PauloCereda.
 
@StefanKottwitz (@barbarabeeton, etc.) Sounds like the meeting was good
 
8:29 PM
@JosephWright any chance you looked at the \newinsert diff (or the update generally) I was wondering if not guarding the fix with \IncludeInrelease is breaking our own rules, but i couldn't see any reason anyone would ever want the previous version so adding it directly via a patch release seemed sort of Ok,even though it's actually the 2015/10/01 release that the code was added
 
@DavidCarlisle I've had a quick look but will do a proper job: give me a few mins
 
@JosephWright wasn't planning to push it tonight so not that much of a rush (I guess Frank is travelling)
 
@DavidCarlisle Looks OK to me
@DavidCarlisle I'd not bother with \IncludeInrelease here: it's a definite bug which no-one can reasonably want
 
@JosephWright yes the only reason for doing it would be to go the other way, if we called it 2016/08/01 and guarded with includeinrelease then someone with 2016/03/31 could in theory use a (new) latexrelease.sty and roll forward to fix the bug, but as it's easier just to let texlive install the patched format I'm not really convinced it would ever be used. (a bit different when we change code that's been there forever)
 
@DavidCarlisle Yes, for these recent changes the likely user base for such roll-forward fixes is tiny. Really not worth it.
 
8:39 PM
@JosephWright thanks I'll send team mail suggesting I release it, but give Frank time to get back before doing so.
 
8:51 PM
@DavidCarlisle GitHub pages stuff looks quite easy
 
@JosephWright yes although since there is no gh-pages branch now, I couldn't see where the staging thing gets built but then I never read all the gh docs on that:-) I was just looking to see if there was a small edit i could do somewhere, just as a test...
 
@DavidCarlisle I've just done one :-)
@DavidCarlisle Two branches, master and live
 
@JosephWright yes i see that, but on github what makes a change to master rebuild the html view at latex3.github.io I thought you had to use the magic gh-pages branch to enable that
@JosephWright ooh linked in:-)
 
@DavidCarlisle Seems not
@DavidCarlisle Yes, decided 'what's the point' basically
@DavidCarlisle I think the naming makes it work
 
@JosephWright so you just edit while in master, push, check on github then switch to live and push again and dante picks it up?
 
9:00 PM
@DavidCarlisle Yes (merge from master to live)
@DavidCarlisle At least, that's what I've done, just need to see when DANTE picks up
 

« first day (2098 days earlier)      last day (2827 days later) »