Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/5] Several cosmetic fixes
Date: Mon, 8 Aug 2016 09:36:08 -0700	[thread overview]
Message-ID: <20160808163608.GJ3482@linux.vnet.ibm.com> (raw)
In-Reply-To: <32c543fd-cad8-f3da-4b1f-15ed2fd919c0@gmail.com>

On Tue, Aug 09, 2016 at 12:00:35AM +0900, Akira Yokosawa wrote:
> >From 572ae1f4ad166e144ceb0306100cb4f5a1235a4e Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Mon, 8 Aug 2016 23:06:10 +0900
> Subject: [PATCH 0/5] Several cosmetic fixes
> 
> Hi,
> 
> This patch series consists of mostly cosmetic fixes.
> 
> 1st one introduces 'extdash' package to enable hyphenation
> of fairly long cmnpound words such as "eventually-consistent".

I like this one a lot!  Much better than looking each word up in
the dictionary and ending up with something like this:

	e\-ven\-tu\-al\-ly-con\-sist\-ent

I had to do this a lot in a recent paper, quite annoying.  Also makes
string-searching painful.

The form enabled by your patch is a -lot- better, thank you!

	eventually\-/consistent

> 2nd one removes a line break between "lines" and "n-m".

Good!

> 3rd one adds \nbco{} command ("nbco" stands for non breakable co)
> to make sure short code snippet not to be broken.

This is very nice, good show!

> 4th one replaces "..." with \ldots for better looking ellipsis.

I was not all that excited about this one, but ended up taking it.
There aren't -that- many ellipses, and this patch really does make
them look better.

> 5th one is just a trial of marking up numbers to avoid using
> hyphens as minus signs. There are two types of mark up.
> One is \txnum{} which is to be used for values in running text.
> The other is \conum{} which is to be used for a value which appears
> in a nearby code snippet. This patch contains small number of example
> uses. I don't use math mode directly because you can modify the
> appearance of each mark-up by modifying just the definition in the
> preamble.
> 
> The effect of this series can be seen in the first paragraph of
> Section 6.1.2.3 "Hashed Double-Ended Queue" in the two column layout.
> Before the changes, the following line break looks ugly.
> 
> ... decreasing numbers (-1, -2, -
> 3, ...), while a series of ...
> 
> There are other ways to prevent the line break here, but I think using
> math mode or \nbco{} command is natural enough. 

But I did not take this one.  I am a bit concerned about everyone having
to type extra LaTeX commands for each and every number.

You could probably talk me into something for only the negative numbers.
Is it possible to make the "-" signs look nicer while still having the
positive and negative numbers not look different from each other?

							Thanx, Paul

>                                            Thanks, Akira
> 
> ----------------------------------------------
> Akira Yokosawa (5):
>   Trial use of extdash package with shortcuts option
>   formal/ppcmem: Avoid break-line after 'lines' in source
>   Add \nbco{} command for code snippet without line break
>   Use \ldots for ellipsis
>   Trial of marking up numbers in text
> 
>  SMPdesign/SMPdesign.tex              | 4 ++--
>  SMPdesign/partexercises.tex          | 4 ++--
>  advsync/memorybarriers.tex           | 2 +-
>  appendix/rcuhist/RCUinLinux.tex      | 2 +-
>  appendix/rcuimpl/rcupreempt.tex      | 6 +++---
>  appendix/whymb/whymemorybarriers.tex | 2 +-
>  count/count.tex                      | 4 ++--
>  datastruct/datastruct.tex            | 2 +-
>  formal/ppcmem.tex                    | 7 ++++---
>  future/htm.tex                       | 2 +-
>  howto/howto.tex                      | 2 +-
>  intro/intro.tex                      | 6 +++---
>  locking/locking.tex                  | 2 +-
>  perfbook.tex                         | 6 ++++++
>  rt/rt.tex                            | 2 +-
>  toolsoftrade/toolsoftrade.tex        | 4 ++--
>  16 files changed, 32 insertions(+), 25 deletions(-)
> 
> -- 
> 1.9.1
> 


  parent reply	other threads:[~2016-08-08 16:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 15:00 [PATCH 0/5] Several cosmetic fixes Akira Yokosawa
2016-08-08 15:02 ` [PATCH 1/5] Trial use of extdash package with shortcuts option Akira Yokosawa
2016-08-08 15:03 ` [PATCH 2/5] formal/ppcmem: Avoid break-line after 'lines' in source Akira Yokosawa
2016-08-08 15:05 ` [PATCH 3/5] Add \nbco{} command for code snippet without line break Akira Yokosawa
2016-08-08 15:06 ` [PATCH 4/5] Use \ldots for ellipsis Akira Yokosawa
2016-08-08 15:07 ` [PATCH 5/5] Trial of marking up numbers in text Akira Yokosawa
2016-08-08 16:36 ` Paul E. McKenney [this message]
2016-08-09 14:04   ` [PATCH v2 0/1] Trial of replacing hyphens with minus signs Akira Yokosawa
2016-08-09 14:06     ` [PATCH v2 1/1] Trial of replacing hyphens of negative values with minus Akira Yokosawa
2016-08-10 22:42     ` [PATCH v2 0/1] Trial of replacing hyphens with minus signs Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160808163608.GJ3482@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akiyks@gmail.com \
    --cc=perfbook@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox