From owner-freebsd-doc@freebsd.org Fri Feb 12 17:28:32 2021 Return-Path: Delivered-To: freebsd-doc@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 01C9A52AC07 for ; Fri, 12 Feb 2021 17:28:32 +0000 (UTC) (envelope-from carlavilla@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DcgSv6VDYz3P3Z; Fri, 12 Feb 2021 17:28:31 +0000 (UTC) (envelope-from carlavilla@freebsd.org) Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com [209.85.167.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: carlavilla) by smtp.freebsd.org (Postfix) with ESMTPSA id CBC3D4710; Fri, 12 Feb 2021 17:28:31 +0000 (UTC) (envelope-from carlavilla@freebsd.org) Received: by mail-lf1-f52.google.com with SMTP id j19so495251lfr.12; Fri, 12 Feb 2021 09:28:31 -0800 (PST) X-Gm-Message-State: AOAM5313uF9crIIbbnp8W0TqVN6ZuKq7mO5EiyfBEqRmRnUBRFOjV6dc QwGiO+nGUdsmhGJgDf9ietfvpjnvLigBhSimiJw= X-Google-Smtp-Source: ABdhPJwKrB8B/YjcLgfGWDXxJPKLC7qsf7W3JJlAT9zzFP0TC1GNk4fw42TYns97/+uOvylBN5umsNJ7VLZFstIv/F4= X-Received: by 2002:a05:6512:1108:: with SMTP id l8mr2026009lfg.255.1613150910403; Fri, 12 Feb 2021 09:28:30 -0800 (PST) MIME-Version: 1.0 References: <20210210135028.u2mm3bhwgep557vu@nerd-thinkpad.local> <20210210140716.pr6up7uxjdf2gydu@nerd-thinkpad.local> <20210210160348.xfy3un6bx5u7cqvj@nerd-thinkpad.local> <20210212170859.lzzj5qrriovjd2ux@nerd-thinkpad.local> <20210212172317.msfh4wrb25penbhp@nerd-thinkpad.local> In-Reply-To: <20210212172317.msfh4wrb25penbhp@nerd-thinkpad.local> From: Sergio Carlavilla Date: Fri, 12 Feb 2021 18:28:18 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Regarding AsciiDoctor and long lines To: Daniel Ebdrup Jensen , freebsd-doc@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2021 17:28:32 -0000 On Fri, 12 Feb 2021 at 18:23, Daniel Ebdrup Jensen wrote: > On Fri, Feb 12, 2021 at 06:16:30PM +0100, Sergio Carlavilla wrote: > >On Fri, 12 Feb 2021 at 18:09, Daniel Ebdrup Jensen > >wrote: > > > >> On Fri, Feb 12, 2021 at 03:09:35PM +0100, Sergio Carlavilla wrote: > >> >On Fri, 12 Feb 2021 at 13:45, Marc Fonvieille > >> wrote: > >> > > >> >> Le 10.02.2021 17:03, Daniel Ebdrup Jensen a =C3=A9crit : > >> >> > Yeah, I'm perfectly fine with doing it like how manual pages work= , > ie. > >> >> > the one-sentence-per-line workflow, if I understand it. > >> >> > > >> >> > >> >> One sentence per line makes the read of diff/commit logs really > >> >> difficult. I gave up reading the commit logs because of that. > >> >> It's really a pain to find what changed without even talking about > the > >> >> edition of a long non-wrapped line in an editor. > >> >> Some languages are very verbose, so we would end with very long > lines. > >> >> For a such change seems so backward. > >> >> > >> >> > I'll be re-working the handbook/x11 chapter to that at some point= . > :) > >> >> > > >> >> > >> >> Please don't. > >> >> > >> >> -- > >> >> Marc > >> >> > >> >Hi, > >> > > >> >I know that this approach it=E2=80=99s causing some confusion with th= e diffs > >> tools. > >> >But instead of using a different way that recommended from the > AsciiDoctor > >> >team I think we should try to focus on getting a solution in the diff > >> tools. > >> > > >> >Maybe we can talk with the AsciiDoctor team. > >> > > >> >Bye. > >> > >> Hi folks, > >> > >> Marc does have a point, which I think is quite valid. A lot of people = do > >> reviews of code in the email they're sent, where - at least for the > >> commits, it's inlined - and pursuant to discussions about this > >> elsewhere, that doesn't seem likely to be changing any time soon. > >> > >> If diffs were attachments with the text/x-patch or text/x-diff > >> mime-type, it'd be up to peoples MUA and possibly their .mailcap as to > >> how it should be opened, but that's not something that's doable with t= he > >> current setup. > >> > >> So I do think wrapping to 72 columns is the better option here, if we > >> want to retain the broadest review possibilities. > >> > >> Yours, > >> Daniel Ebdrup Jensen > >> > >Hi, > > > >Ok, if we use this approach. > > > >What are we gonna do with: > > > >Headings > >Unordered list > >Ordered list > >Images > >Include macro > >AsciiDoc variables > >Custom macros > > > >And I need to test classes and links. > > > >Bye. > > Hi folks, > > That's what we, in the business, call a good question. > > Won't the + syntax work for all of those markups? > > Yours, > Daniel Ebdrup Jensen > > P.S. The business in question is the one for people with just a tiny > clue stick. ;) > Hi, No, the + character is only for paragraphs. Bye.