« first day (1449 days earlier)      last day (3482 days later) » 

6:34 AM
@Johannes_B: Guten Morgen nach Freiberg
 
@ChristianHupfer Guten Morgen zum Sonnenaufgang
 
@Johannes_B: Bei uns ist die Sonne noch hinter etwa 1100 Metern hohen Bergen versteckt ;-)
 
@ChristianHupfer Didn't think of the mountains.
 
@Johannes_B: I like mountains
 
@ChristianHupfer We are the free one :-p
 
6:41 AM
@Johannes_B: Any news from Banana/the enumerate guy etc?
 
@ChristianHupfer None.
 
@Johannes_B: Well, I had not much time for TeX the last days and won't have it for about a week. We'll move on Friday
 
@ChristianHupfer I am confident, that you can do it. </motivate>
 
@Johannes_B: I think so, thanks. I think I will rewrite my 'problem/solution' package in L3 style ... I have something to learn ;-)
 
@ChristianHupfer aren't there a few out there?
@ChristianHupfer Namely exsheets by @cgnieder and probsoln by @JosephWright
 
6:50 AM
@Johannes_B: I know, but I wanted to do it on my own. I wanted to implement them with work sheet headers, class examen headers, functionality to connect to a MySQL database etc, standalone-exercise-books
 
@ChristianHupfer Actually, i can understand that. But i wouldn't do it for packages of those two.
@ChristianHupfer Ooh, databases
 
@Johannes_B: We'll see ;-)
 
@Johannes_B: Well, that's nice ... I did not thought about an exercise 'generator' . I'll keep in my mind
 
@ChristianHupfer I was searching for luatex sql and found that.
 
7:00 AM
@Johannes_B: It will take some time to rebuild it, but I think it's worth to do so
@Johannes_B: Ok, it's time to work, see you later ;-)
 
@ChristianHupfer See you, sei fleißig.
 
@Johannes_B: I am always fleißig :-P
 
 
7 hours later…
1:43 PM
@cgnieder Why can't tasks be nested?
 
2:07 PM
@HarishKumar tasks isn't a list that uses LaTeX's list mechansim. The environment is a pseudo-environment: it collects the environment body and splits its contents at every appearance of \task which makes nesting difficult to implement (at least for me – and I was too lazy to look for a working solution)
 
2:54 PM
@cgnieder: Thanks. So there is nothing much to expect in the near future?
 
3:16 PM
@Harish I'm afraid not. Especially since I haven't as much time for LaTeX as I'd like to
 
@cgnieder: Thanks again Clemens. Hope you will get free time some day :-)
 
 
1 hour later…
4:32 PM
Does anyone have any suggestion for full width tables (that goes into the margins) with longtable and KOMA-Script?
I am using twosided document, which seems to mess up everything
I tried the changepage package and adjustwidth, but it doesn't seem to work with the table
 
@Ahlqvist hi! Two-sided or two-column?
 
4:54 PM
hum, everything seems to be fixed when I switched to xtab package instead
 
 
2 hours later…
7:10 PM
@percusse Isn't \makeabbrev nice?
 
@egreg Ah yes it is but you need some acquaintance with the L3 syntax.
I'm after the badges :P
 
@percusse On Math.SE there was a question by one who claimed to have solved P=NP based on the limit at infinity of 2^n/n. It is 1, isn't it? OMG!
 
@egreg it is zero of course. Or undefined, at best
 
7:28 PM
@tohecz Well, apparently the wonderful one million dollar worthy proof depended on the limit being 1. I hope my first year students will do a bit better. ;-)
 
7:56 PM
I think I need a mechanical engineer to reopen and answer my question below.
0
Q: How to describe the motion of a box initially at rest on a table rotating with an increasing angular speed?

In PSTricks we trustConsider the following diagram. A box is on a table that can move circularly and the box is connected by a string attached to the fixed bearing. At $t=0$, the box is at rest, the string of length $L$ is loose so the distance between the axis to the box is $R_0<L$. The coefficients of static a...

 
@egreg It is for N=1
@InPSTrickswetrust You can solve for static friction case right? Centrifugal equals static friction in terms of omega. That's the limit rot speed. Then since you say the string can't twist or whatever. Observer notion is irrelevant here. You are not considering relativistic effects anyhow.
 
8:13 PM
@percusse For inertial observer there will be no centrifugal force (aka fictitious force). :-)
Observer is very important here. :-)
 
@InPSTrickswetrust Not really. Same applies to a mass on a running mill. It's a matter of coordinate selection. Trust me. You don't need an observer notion. It's not relevant. You need to express the velocities with respect to a point on the disk. That's less fancy but more correct.
Just a point. Observing or not.
@InPSTrickswetrust By the way, Hot licks seems to answer the question already.
 
@percusse Choosing the type of observers (inertial or non-inertial) is very important to establish the equation. But for both observers the mathematical representation will be the same. Hot Licks's answer might be correct.
 
@InPSTrickswetrust It is important for other things but not for this problem. Relative velocity != relativity
This is only relative coordinate system derivation depending on where you select your coordinates. On the shaft on the disk, on the mass or ambient.
 
@percusse No. It is not about relativity.
 
So you don't need the notion of an observer to complicate things. Hotlick's answer is correct.
 
8:26 PM
@percusse His answer is NOT complete, what happens if we increase omega, when the box and the table have different angular speed, etc.
 
8:57 PM
@InPSTrickswetrust Are you using the ideal or the realistic scenarios? Why would they have different velocities?
By velocity I mean the angular speed. Sorry.
 
@percusse They can stick together in synchronous motion if there is enough friction between the clutch plates. It is my idea.
If the table moves too fast, there is a chance the box slip.
 
What would be the xparse's signature of a command like foreach? Or it isn't possible out of the box?
 
@InPSTrickswetrust Why would it slip in the ideal case?
 
@percusse What is the ideal case you meant?
 
The second argument in \foreach is {a,b,c,d}` or \tokenlist, in case the next token is not a \bgroup it expands the variable once.
And the third argument is, in case next token is \bgroup just an usual argument. And in case it's not, the argument is delimited by the next ;.
 
9:08 PM
@percusse: Let's continue it tomorrow (if you think it is necessary) as I cannot open my eyes. :-)
 
@InPSTrickswetrust Why do you think the mass can slip? You need some additional real stuff for the slip to happen. In other words what would make the box not accelerate in your formulation as fast as the disk?
@InPSTrickswetrust OK Good night.
@Manuel @egreg Just answered a question like that tex.stackexchange.com/questions/207985/…
He used clists
 
@Manuel Using a command with “variable behavior” is to be discouraged, in my opinion. I'd much prefer \foreach for an explicit list and \foreach* for an implicit one.
So you could do \NewDocumentCommand{\foreach}{smm}{\IfBooleanTF{#1}{\manuel_foreach:on{#2}{#3}}‌​{\manuel_foreach:nn{#2}{#3}}}. Then define \manuel_foreach:nn and create the variant \manual_foreach:on
 
9:41 PM
@percusse So I read :)
@egreg Okey, and for the last part there's no way to combine the option to have one argument or a weird argument delimited by ; without an auxiliar command?
 
@Manuel Avoid weird argument for high level commands.
 
@egreg Okey, okey, it's just curiosity.
To see which would be the “most straightforward way” of doing a check for a next token (t\bgroup?) and then calling an auxiliar command delimited by ;.
 
@Manuel \peek_catcode:NTF
 
\foreach{x,y,z,t}{Do something with #1} or \foreach[\x]{x,y,z}{Do something with \x} is absolutely readable for me.
@egreg Yes, I know that. It was more about understanding xparse's signatures (I only play with m, o, O, s, d, and D arguments).
I think { … m g }{ … \IfValueTF{#3}{\auxiliarwithbraces}{\auxiliaruntilsemicolon} } does more or less what I was looking for.
 

« first day (1449 days earlier)      last day (3482 days later) »