Dror Atariah writes:
> I'm sorry I keep bugging with this... ;)
>
> On Dec 14, 2013, at 22:06 PM, Nick Dokos wrote:
>
>> Nick Dokos writes:
>>
>>> Dror Atariah writes:
>>>
2. What's next? I believe this is a bug... How can I report it?
>>>
>>> Consider it reported - thanks for checking
I'm sorry I keep bugging with this... ;)
On Dec 14, 2013, at 22:06 PM, Nick Dokos wrote:
> Nick Dokos writes:
>
>> Dror Atariah writes:
>>
>>> 2. What's next? I believe this is a bug... How can I report it?
>>
>> Consider it reported - thanks for checking it. I'll push the proposed fix
>> l
Dror Atariah writes:
> On Jan 12, 2014, at 14:26 PM, Bastien wrote:
>
>> Hi Dror,
>>
>> Dror Atariah writes:
>>
>>> So what's the point of the daily updates of the ELPA packages?
>>
>> To get bug fixed when you use ELPA.
>
> Wasn't the issue discussed originally in this thread a bug (and its
>
Dror Atariah writes:
> Wasn't the issue discussed originally in this thread a bug (and its
> fix)? Why it is not reflected in the ELPA? I just want to understand
> what's going on... No criticism or anything like that :)
Yep, no problem: as I said, the bug was fixed in master, that's why it
was
On Jan 12, 2014, at 14:26 PM, Bastien wrote:
> Hi Dror,
>
> Dror Atariah writes:
>
>> So what's the point of the daily updates of the ELPA packages?
>
> To get bug fixed when you use ELPA.
Wasn't the issue discussed originally in this thread a bug (and its fix)? Why
it is not reflected in t
Hi Dror,
Dror Atariah writes:
> So what's the point of the daily updates of the ELPA packages?
To get bug fixed when you use ELPA.
--
Bastien
On Jan 12, 2014, at 13:53 PM, Bastien wrote:
> Dror Atariah writes:
>
>> Update: I have just updated from ELPA, and the patch is not
>> there... I had to re-patch the missing line.
>
> The ELPA packages are built from the maint branch, from the
> master branch, so patches in the master branch d
Dror Atariah writes:
> Update: I have just updated from ELPA, and the patch is not
> there... I had to re-patch the missing line.
The ELPA packages are built from the maint branch, from the
master branch, so patches in the master branch do not show up
there, that's why you had to re-patch this.
On Dec 15, 2013, at 15:17 PM, Nick Dokos wrote:
> Dror Atariah writes:
>
>> On Dec 14, 2013, at 22:06 PM, Nick Dokos wrote:
>>
>>> Nick Dokos writes:
>>>
Dror Atariah writes:
> 2. What's next? I believe this is a bug... How can I report it?
Consider it reported - t
Dror Atariah writes:
> On Dec 14, 2013, at 22:06 PM, Nick Dokos wrote:
>
>> Nick Dokos writes:
>>
>>> Dror Atariah writes:
>>>
2. What's next? I believe this is a bug... How can I report it?
>>>
>>> Consider it reported - thanks for checking it. I'll push the proposed fix
>>> later
>>>
On Dec 14, 2013, at 22:06 PM, Nick Dokos wrote:
> Nick Dokos writes:
>
>> Dror Atariah writes:
>>
>>> 2. What's next? I believe this is a bug... How can I report it?
>>
>> Consider it reported - thanks for checking it. I'll push the proposed fix
>> later
>> on today. If it is wrong, we can
Nick Dokos writes:
> Dror Atariah writes:
>
>> 2. What's next? I believe this is a bug... How can I report it?
>
> Consider it reported - thanks for checking it. I'll push the proposed fix
> later
> on today. If it is wrong, we can revert it later, but at least for now
> it seems to fix the bug
Dror Atariah writes:
> Bingo! Adding this line allowed me to complete org-mobile-push successfully!
> Amazing. I have three closing questions:
>
> 1. What made you look into lines #460-464? Now when you pointed, it is
> somehow straightforward to check line #470, but there seems to be no
> indic
On Dec 13, 2013, at 23:08 PM, Nick Dokos wrote:
> Dror Atariah writes:
>
>> Managed to get [backtrace] output...
>>
>> You can find it here: https://gist.github.com/drorata/7950857
>>
>> I could not find my way in this output... :(
>>
>
> If you look at the top of the backtrace it shows thi
Dror Atariah writes:
> Managed to get [backtrace] output...
>
> You can find it here: https://gist.github.com/drorata/7950857
>
> I could not find my way in this output... :(
>
If you look at the top of the backtrace it shows this:
,
| Debugger entered--Lisp error: (wrong-type-argument seq
On Dec 13, 2013, at 20:51 PM, Nick Dokos wrote:
> Dror Atariah writes:
>
>> On Dec 13, 2013, at 16:08 PM, Nick Dokos wrote:
>>
>>> Dror Atariah writes:
>>>
Today I realized that I cannot execute successfully 'org-mobile-push'. In
particular here is the output from '*Messages*':
>>
Dror Atariah writes:
> On Dec 13, 2013, at 16:08 PM, Nick Dokos wrote:
>
>> Dror Atariah writes:
>>
>>> Today I realized that I cannot execute successfully 'org-mobile-push'. In
>>> particular here is the output from '*Messages*':
>>>
>>> Creating agendas...
>>> Agenda written to Org file /Us
On Dec 13, 2013, at 16:08 PM, Nick Dokos wrote:
> Dror Atariah writes:
>
>> Today I realized that I cannot execute successfully 'org-mobile-push'. In
>> particular here is the output from '*Messages*':
>>
>> Creating agendas...
>> Agenda written to Org file /Users/drorata/Dropbox/MobileOrg/ag
Dror Atariah writes:
> Today I realized that I cannot execute successfully 'org-mobile-push'. In
> particular here is the output from '*Messages*':
>
> Creating agendas...
> Agenda written to Org file /Users/drorata/Dropbox/MobileOrg/agendas.org
> Creating agendas...done
> Saving all Org-mode bu
Today I realized that I cannot execute successfully 'org-mobile-push'. In
particular here is the output from '*Messages*':
Creating agendas...
Agenda written to Org file /Users/drorata/Dropbox/MobileOrg/agendas.org
Creating agendas...done
Saving all Org-mode buffers...
(No files need saving)
Savi
20 matches
Mail list logo
