Open Source Telephony
 help / color / mirror / Atom feed
From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: ofono@ofono.org
Subject: Re: [PATCH v3 2/2] huawei: add gprs context
Date: Tue, 10 Aug 2010 21:56:30 -0700	[thread overview]
Message-ID: <1281502590.9561.141.camel@localhost.localdomain> (raw)
In-Reply-To: <87hbj8urpr.fsf@potku.valot.fi>

[-- Attachment #1: Type: text/plain, Size: 2285 bytes --]

On Fri, 2010-08-06 at 10:26 +0300, Kalle Valo wrote: 
> Inaky Perez-Gonzalez <inaky@linux.intel.com> writes:
> 
> > Hi Kale
> 
> Hola,
> 
> > On Thu, 2010-08-05 at 08:54 +0300, Kalle Valo wrote: 
> >>
> >> This is my setup:
> >> 
> >> ; from linux/Documentation/CodingStyle
> >> (defun c-lineup-arglist-tabs-only (ignored)
> >>   "Line up argument lists by tabs, not spaces"
> >>   (let* ((anchor (c-langelem-pos c-syntactic-element))
> >> 	 (column (c-langelem-2nd-pos c-syntactic-element))
> >> 	 (offset (- (1+ column) anchor))
> >> 	 (steps (floor offset c-basic-offset)))
> >>     (* (max steps 1)
> >>        c-basic-offset)))
> >
> > Thanks! Phew ... this is a handful of lisp! I don't understand anything
> > that is not basic anymore :)
> 
> It sure is. I just copied it from Linux CodingStyle document and it
> seems to work somehow.
> 
> > -- I gave it a whiz and one thing I saw was that
> >
> > struct tx_queue_entry *__ofono_sms_txq_submit(struct ofono_sms *sms,
> > 						GSList *list,
> > 						unsigned int flags, unsigned msg_id,
> > 						ofono_sms_msg_stch_cb_t stch_cb,
> > 						void *data, ofono_destroy_func destroy)
> >
> > is being formatted as:
> >
> > struct tx_queue_entry *__ofono_sms_txq_submit(struct ofono_sms *sms,
> > 					GSList *list,
> > 					unsigned int flags, unsigned msg_id,
> > 					ofono_sms_msg_stch_cb_t stch_cb,
> > 					void *data, ofono_destroy_func destroy)
> >
> > ie: one c-basic-offset less than it should -- I really can't figure out where to poke.
> 
> That's my problem as well. Currently I just manually add one more tab to
> each line with M-i. If you find a way to fix this, please let me know.

I think I found it, seems to cut it; replace:

(steps (floor offset c-basic-offset)))

with

         (steps (floor (+ offset (- c-basic-offset 1)) c-basic-offset)))

Lisp nuts me out, but it is doing the:

steps = floor(offset/c-basic-offset);

with

steps = floor((offset + c-basic-offset - 1) / c-basic-offset);

thus making sure there is always one more tab except when the offset is
right on a tab boundary that we keep the same.

So far, so good -- probably it fails in some case, because this is
totally trial and error as unscientific as it can :)



      reply	other threads:[~2010-08-11  4:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 14:06 [PATCH v3 0/2] Huawei GPRS support Kalle Valo
2010-05-19 14:06 ` [PATCH v3 1/2] huawei: detect SecondaryDevice which is used for events Kalle Valo
2010-05-19 13:40   ` Denis Kenzior
2010-05-20  7:15     ` Kalle Valo
2010-05-19 14:06 ` [PATCH v3 2/2] huawei: add gprs context Kalle Valo
2010-05-19 13:44   ` Denis Kenzior
2010-05-20  7:35     ` Kalle Valo
2010-08-04 19:59       ` Inaky Perez-Gonzalez
2010-08-05  5:54         ` Kalle Valo
2010-08-05 17:29           ` Inaky Perez-Gonzalez
2010-08-06  7:26             ` Kalle Valo
2010-08-11  4:56               ` Inaky Perez-Gonzalez [this message]

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=1281502590.9561.141.camel@localhost.localdomain \
    --to=inaky@linux.intel.com \
    --cc=ofono@ofono.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