From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/75931 Path: news.gmane.org!not-for-mail From: "Rogers, Michael K" Newsgroups: gmane.comp.tex.context Subject: Re: Problem with \inmargin on \item lines Date: Wed, 2 May 2012 11:30:10 +0000 Message-ID: <012DEF64-C353-436E-915B-F494CC67490C@emory.edu> References: <6AD49FC8-3558-4538-B5C3-21D14D3C3A3B@stien.de> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1335958241 21412 80.91.229.3 (2 May 2012 11:30:41 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 2 May 2012 11:30:41 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Wed May 02 13:30:40 2012 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SPXlW-0007Jr-7W for gctc-ntg-context-518@m.gmane.org; Wed, 02 May 2012 13:30:38 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 2ACEF101EF; Wed, 2 May 2012 13:30:37 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id DOHhCSUDU9s6; Wed, 2 May 2012 13:30:34 +0200 (CEST) Original-Received: from [127.0.0.1] (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id C1AB7101E9; Wed, 2 May 2012 13:30:34 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 627CA101E9 for ; Wed, 2 May 2012 13:30:33 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id aFRvp4aeZ-IW for ; Wed, 2 May 2012 13:30:31 +0200 (CEST) Original-Received: from filter2-ams.mf.surf.net (filter2-ams.mf.surf.net [192.87.102.70]) by balder.ntg.nl (Postfix) with ESMTP id 0BB38101E8 for ; Wed, 2 May 2012 13:30:30 +0200 (CEST) Original-Received: from ndb-mr2.cc.emory.edu (ndb-mr2.cc.emory.edu [170.140.52.250]) by filter2-ams.mf.surf.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id q42BUS8P025489 for ; Wed, 2 May 2012 13:30:29 +0200 Original-Received: from e14edge2n.Emory.Edu (emoryfloatdmz.cc.emory.edu [170.140.52.254]) by ndb-mr2.cc.emory.edu (8.13.8/8.13.1) with ESMTP id q42BUAr3007832 for ; Wed, 2 May 2012 07:30:10 -0400 Original-Received: from E14CH4W.Enterprise.emory.net (10.240.10.116) by e14edge2n.Emory.Edu (170.140.53.162) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 2 May 2012 07:30:10 -0400 Original-Received: from E14MBX20N.Enterprise.emory.net ([fe80::e9ea:8c9d:f94e:7cd3]) by e14ch4w.Enterprise.emory.net ([::1]) with mapi id 14.02.0283.003; Wed, 2 May 2012 07:30:10 -0400 Thread-Topic: [NTG-context] Problem with \inmargin on \item lines Thread-Index: AQHNKBzgLGOZUZU6m06y89PfMh55QJa2oLCA In-Reply-To: <6AD49FC8-3558-4538-B5C3-21D14D3C3A3B@stien.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [170.140.30.131] Content-ID: <209F242F4AAF0D4598A0AC26713F77D1@Enterprise.emory.net> X-Emory-MailScanner-Information: Please contact the ISP for more information X-Emory-MailScanner-ID: q42BUAr3007832 X-Emory-MailScanner: Found to be clean X-Emory-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-0.01, required 8, autolearn=disabled, T_RP_MATCHES_RCVD -0.01) X-Emory-MailScanner-From: mroge02@emory.edu X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN) X-CanIt-Geo: ip=170.140.52.250; country=US; region=GA; city=Atlanta; postalcode=30322; latitude=33.7952; longitude=-84.3248; metrocode=524; areacode=404; http://maps.google.com/maps?q=33.7952,-84.3248&z=6 X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 0QH4Xushp - eb934c375fed - 20120502 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.87.102.70 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:75931 Archived-At: Hi, It is not a bug. It is standard TeX: a space counts after "}" and is ignored immediately after a control sequence such as "\item". To override either, you have to be explicit, "\ignorespaces" as Hans suggested in your case and "\ " (backslash-space) in the other to put a space in. My preferred, idiosyncratic, pedantic way to ignore spaces in this case is a comment symbol and newlines: \starttext \startitemize \item This is just a normal completely innocent paragraph against which one will be able to judge the amount of indentation of the next paragraph. \item\inmargin{Duck}% This paragraph has a duck inmargin comment \stopitemize \stoptext But I like newlines in my code, probably because I started editing text on 24x80 crt that would show only the first 80 characters of a line. Michael On May 2, 2012, at 12:33 AM, Malte Stien wrote: > Hi everyone, > > I am experiencing a problem with \inmargin{some text} in \itemized lists. I am using them a lot in my documents, and it is kind of annoying. It appears that if one uses the \inmargin macro just prior to the \item macro, the in-margin text is typeset against the previous line, not the line with the \item. Minimal example. > > \starttext > \startitemize > \item This is just a normal completely innocent paragraph against which one will be able to judge the amount of indentation of the next paragraph. > \inmargin{Duck}\item This paragraph has a duck inmargin comment > \stopitemize > \stoptext > > That seems fair enough and even makes sense on some level. If however, one reverses the two macros, like so: > > \item\inmargin{Duck} This paragraph has a duck inmargin comment > > the leading space just after the closing brace is actually printed. I take this to be a bug, or is this by design? The only way I can around this is to not use a space, like so: > > \item\inmargin{Duck}This paragraph has a duck inmargin comment > > But I don't find that to be a satisfying solution. After all I am using ConTeXt because I am a bit pedantic about text, even the source code in this case. > > Regards, > Malte. > ________________________________ This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments). ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________