From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: [elpa] 02/04: company-clang: handle multibyte chars between bol and point Date: Wed, 19 Mar 2014 23:15:43 +0200 Message-ID: <532A08FF.8020001@yandex.ru> References: <20140319033013.17542.14344@vcs.savannah.gnu.org> <87mwgm9t81.fsf@yandex.ru> <834n2u9lj7.fsf@gnu.org> <5329DA52.2030704@yandex.ru> <83vbva82cy.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1395263768 22801 80.91.229.3 (19 Mar 2014 21:16:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Mar 2014 21:16:08 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 19 22:16:17 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WQNqS-0001hV-It for ged-emacs-devel@m.gmane.org; Wed, 19 Mar 2014 22:16:16 +0100 Original-Received: from localhost ([::1]:43790 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQNqS-0008PN-4P for ged-emacs-devel@m.gmane.org; Wed, 19 Mar 2014 17:16:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38019) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQNqH-0008Bl-Vx for emacs-devel@gnu.org; Wed, 19 Mar 2014 17:16:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WQNq9-0008FC-J0 for emacs-devel@gnu.org; Wed, 19 Mar 2014 17:16:05 -0400 Original-Received: from mail-ee0-x233.google.com ([2a00:1450:4013:c00::233]:63755) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQNq0-0008EO-D8; Wed, 19 Mar 2014 17:15:48 -0400 Original-Received: by mail-ee0-f51.google.com with SMTP id c13so7043952eek.24 for ; Wed, 19 Mar 2014 14:15:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=VB+wFraCZE7NsJ6VhqPugLN71rw2ZhnaNxcNZDxa8MU=; b=a6m/tD4ko5bu9BLi+UjPsAHnLHbQe52FmocSFOUbUd19ccAhYmqSEnmwWhpo8alwZj Nrplclolyo7XXTwMN9WwLKjw4e1IFGRyG5MwwiPnE+DYr1dpDUHofPRVBGT9tIuOmg/H glbWWv04I05Takz+tL60QNdDXnCRcfulquie4kUDRqGhSpi5jXynPHoFQ1eMt843wqVq C5HknVVaZiWQUFYAiimnsQFPZPFAoUAPJcnPe0uJuvnykGGSY5LB/HYFHtSiUq/LCHZY G2qpVA5W5IjxRuHLkVoxuzvEZeXCrHeud+Hy1EUGc82bUwwY5FHPnjs29/J/FsszJxEy VnoA== X-Received: by 10.14.193.201 with SMTP id k49mr37740534een.50.1395263747171; Wed, 19 Mar 2014 14:15:47 -0700 (PDT) Original-Received: from [192.168.10.2] (62-122-52.netrun.cytanet.com.cy. [62.228.122.52]) by mx.google.com with ESMTPSA id 43sm57280932eeh.13.2014.03.19.14.15.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Mar 2014 14:15:46 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 In-Reply-To: <83vbva82cy.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c00::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:170575 Archived-At: On 19.03.2014 20:33, Eli Zaretskii wrote: > If clang can endure inaccurate counts (I don't know if it can) Only in the sense that it won't blow up, just return inaccurate results. >> But if you could point out an easy way to obtain that byte count more >> correctly, that would be quite welcome. > > I did, see below. Thank you. (Without being Cc'd, I haven't read your other email until after my previous reply). >> So, um, do I use something like >> >> (length (encode-coding-string STR buffer-file-coding-system)) >> >> ? > > Yes, I think so. Thanks.