« first day (3729 days earlier)      last day (45 days later) » 

9:06 AM
*sits by computer working
*picks up post-it block to write note
*writes note on post-it
*presses Ctrl+S on computer keyboard
*stares at post-it
maybe I should take a break from the computer XD
7
 
@Plergux Just use a virtual postit. Reality is not worth it.
 
9:37 AM
@StephanLehmke heh heh heh... I suppose I could try that. I'm not sure it would have the same effect though. :p But it would probably decrease the piles of paper I have scattered around me with various thoughts, notes, and reminders. :p
 
Finally we are safe! @PauloCereda is banned.
PSLATEX UPDATED AT CTAN All the users who have been clamouring for updates since the last one in 1996 will be happy.
3
 
@DavidCarlisle Mean
 
@DavidCarlisle oh
 
Jun 29 '17 at 16:15, by Paulo Cereda
@DavidCarlisle you are not mean :)
 
@DavidCarlisle, @UlrikeFischer (@HenriMenke) Looking yet again at stroke/fill colour for l3draw, I think I'm back switching to using the stack where it's available. I think I'll use a single stack as HO does in pdfrender. Thoughts?
 
9:52 AM
@JosephWright sounds good in principle.
 
@DavidCarlisle Yes: I've been back and forward, as Till doesn't do that, but once you look at pdfrender you realise that fill/stroke colour might be wanted for running text
@DavidCarlisle I'll probably try it and we can see if there are any issues; not like there are 1000s of l3draw users ATM
 
@JosephWright there is still the local/global error in the newest xetex/l3backend-color. \int_set:Nn \l_@@_backend_stack_int
 
@UlrikeFischer On my list for today :)
@UlrikeFischer WE are getting closer to something workable, but this is quite tricky stuff - the backend variations do not help
 
@JosephWright yes I know. And we should try to finalize/merge some of the PR's - I'm currently building local branches like "l3bitset+dest+color-tmp-branches" and similar on the latex2e side and that is getting confusing ;-)
 
@UlrikeFischer Should be fixed: for dvipdfmx, we need both a local int (the stack in use) and a global one (the last allocated stack)
@UlrikeFischer Yes, would be good
@UlrikeFischer dest should be OK to merge I think, bitset of course more interesting; not sure what the colour one is
 
10:10 AM
@JosephWright well actually I was more the other way round: imho the interface for bitset is fine now after I merged the key/index stuff in one and the name seem to settle as no other suggestion came (only internally one should perhaps replace the regex with something faster, but this is not pressing). For the dest stuff I still wonder after the discussion if one can merge the box variant in somehow (and create a variant which makes a 0-size-box).
 
@UlrikeFischer Ah, right: so a new PR for bitset
 
@JosephWright why new? It is there?
 
@UlrikeFischer I meant that we closed the other one: did I miss a new one?
@UlrikeFischer Oh, ignore me!
 
@JosephWright hm, just in case: I also made a pull request towards xref to change the name back (and added a test).
 
10:30 AM
@PhelypeOleinik, @UlrikeFischer, @DavidCarlisle github.com/pgf-tikz/pgf/issues/982
 
I like how the BBC reporter says they will ban flights from Brazil and South America. We are part of South America...
 
10:44 AM
@PauloCereda we are not very good at continents, some people find the idea of us being part of Europe tricky as well
 
@DavidCarlisle ooh
@DavidCarlisle it was easier when the rest of the world were just crown colonies. :)
 
@PauloCereda are they not now?
@JosephWright hmm having half the loop syntax in one file and the end of the loop body in another seems a bit brave but I guess it used to work
 
11:10 AM
@DavidCarlisle That's not the issue, though
LaTeX3 Project has vanished (more or less) from latex3 sources!
@PauloCereda :)
 
@DavidCarlisle the question is what to do here? remove the file hooks from \input? Create a new (expandable?) raw input command for such cases?
 
@PauloCereda So is Portugal, apparently!
@UlrikeFischer I think this might be a 'tough' one: it's almost impossible to support (I wonder what happened with filehooks in any case)
 
@UlrikeFischer it's not that it's not expandable (\input has never been expandable`)
 
@DavidCarlisle no I know, but as we want an expandable input for e.g. tabulars anyway we would catch two flies.
 
@UlrikeFischer yes I was going to say a proper interface to \@@input would be good for tabular as well especially if we can use the new primitive \input with braces form
 
11:14 AM
@PhelypeOleinik Is the gh839 branch ready to go?
 
@JosephWright oh, you meant the filehooks package, I had already pushed it out of my mind that this ever existed ;-)
 
11:40 AM
@Plergux post-it.com/3M/en_US/post-it/ideas/app is actually quite cool, but there are lots of other tools like miro.com/online-sticky-notes
 
@StephanLehmke My monitor is already full of sticky notes on the outside and you suggest to bring more to the inside as well? :)
 
@PauloCereda You can fill your phone or tablet with them :-)
 
@StephanLehmke ooh
@UlrikeFischer /poke <3
 
12:13 PM
@PauloCereda ?
 
@UlrikeFischer miss you <3
@UlrikeFischer and secret update :)
 
@PauloCereda I saw, I will check later, I have to do lunch now.
 
@JosephWright Yes, and gh795 (will push online in a bit) should be done today too
@JosephWright I'm expecting to merge these two into latex3/master, then import all the changes as 'update xparse.dtx' to the latex2e repo. Is that okay?
 
@UlrikeFischer ooh lunch
 
@PauloCereda quack
 
12:23 PM
@DavidCarlisle I am... confused
@DavidCarlisle quack
 
@PauloCereda lunch
 
@DavidCarlisle oh no
<3
 
@PauloCereda order restored to the universe
 
@DavidCarlisle phew
 
@PhelypeOleinik Fine with me
 
 
1 hour later…
1:34 PM
@StephanLehmke :D (I'll be spending the rest of the day ooh-ing and aah-ing over all the "reality post-its" available on M3, thanks :p)
 
1:45 PM
@Plergux ooh
 
2:26 PM
@Plergux In my opinion (yeah, I know, nobody asked for it) electronic post-its are not so useful. I find the physical ones useful because I hate to have the desktop littered with them and so I solve them. If I could remove that with a click ("I will come back asap...") they will be completely useless.
 
 
1 hour later…
3:27 PM
@Rmano Yeah, I sort of agree. If it's just something you need to remember, like a piece of code or a phone number it's fine to have a little note somewhere in your computer for when you need it, but if you actually have to get to doing the coding or phoning that person then the real ones are much better :)
 
4:22 PM
@PauloCereda if you use rabbitfy without -r, it would be better to switch to mode=HTML and not define the colours individually (pxpic just defines macros, not the colours, so you're just adding an overhead here).
 
@Skillmon Ah sorry
 
@PauloCereda no problem, I just wanted to inform you :)
 
@Skillmon I fail to read documentation. :)
@Skillmon Thanks! <3 One for future update
 
@PauloCereda @DavidCarlisle would be so proud of you! :)
 
@Skillmon ooh
 
4:26 PM
@PauloCereda or one I should update. Maybe it would be faster (and less error-prone on the xcolor side) if I defined named colours locally and switch to {\color{pxpic@<name>}\px} for output.
 
@Skillmon ooh
 
@Skillmon unlikely
 
@DavidCarlisle oh
 
@PauloCereda it won't matter anyway, soon be dinner time.
 
@DavidCarlisle oh no
 
 
4 hours later…
8:51 PM
If I've defined a colour (e.g., via \definecolor) in xcolor, is there a faster way to use this colour than \colour{<name>}?
 
 
1 hour later…
9:53 PM
Hello everyone, for this answer tex.stackexchange.com/a/564995/2288, why are the example images a bit lower than the text in the first column?
 
10:06 PM
@Skillmon in color package you could use \@declaredcolor{name} to save one level of looking for optional arguments but really in the scheme of things, I wouldn't.
@Diaa see section 4.6 of textdoc adjustbox, t puts the reference point a little bit below the top but you can adjust with \adjboxvtop just how much it raises the image.
@Diaa oh sorry actually the t there is defined (incompatibly) by graphobox (which I hadn't heard of) which according to the footnote on page 5 of its documentation says it is (for some reason) (36/31)ex in the current font. but it has a vshift key to shift it up more
 
10:23 PM
@DavidCarlisle on page 5 of what?
 
@UlrikeFischer graphobox
 
@DavidCarlisle graphbox, but what is a "documentation"?
 
@UlrikeFischer no idea, I suspect I didn't type that. Can't have been me there are typos.
 
10:55 PM
@DavidCarlisle and no teh at all.
 
11:15 PM
@UlrikeFischer I found a file on CTAN that I have not got write access to (actually Nelson Beebe found it) I didn't think there were any left:-) You'd think given the author I would have access...
 
@DavidCarlisle ? which one?
 
@UlrikeFischer this :-) (but look quickly before Petra deletes it)
 
@DavidCarlisle did he change something or why did he make a private copy?
@DavidCarlisle there is also a copy of ot1pag.fd.
 
@UlrikeFischer He couldn't really recall but thinks it was used to get access to the condensed courier and he copied it locally as it was marked obsolete so he was worried it would be deleted, but didn't intend to upload it to ctan, yes he's going to zap the fd files as well. The pdf version of the guide isn't maintained anyway
 
@DavidCarlisle one wonder why anybody finds this ;-)
 
11:28 PM
@UlrikeFischer Nelson, not anybody
 
@DavidCarlisle does he regularly look through the tree for such stuff?
 
@DavidCarlisle Is there another lazy different way to align the image without having to manually do it with vshift?
@DavidCarlisle Never mind! adjustbox with valign=t does the job right.
 
11:55 PM
@UlrikeFischer I think he has multiple scripts running all kinds of consistency checks on things, I assume that he will find any duplicate of any updated file on ctan just as part of his mirroring,I doubt he looked for this by hand.
 
@DavidCarlisle I guess he didn't find the ot1pag.fd when I updated psnfss because it is cunningly hidden in a zip ;-)
 

« first day (3729 days earlier)      last day (45 days later) »