On 24.4.2013, at 11:38, Bastien wrote:
> Hi Carsten,
>
> Carsten Dominik writes:
>
>> I think only doing this at the beginning of the prompt is better,
>> anywhere else it is too magic.
>
> Okay, I implemented this by checking if we are at the start of the
> prompt with `looking-back'. Us
Hi Carsten,
Carsten Dominik writes:
> I think only doing this at the beginning of the prompt is better,
> anywhere else it is too magic.
Okay, I implemented this by checking if we are at the start of the
prompt with `looking-back'. Using "prompt" here would raise a
compiler warning -- we wou
Hi Bastien
On Wed, Apr 24, 2013 at 10:51 AM, Bastien wrote:
> I have no strong opinion on this, but I think it's better if "." does
> one single thing at the time.
Then I don't mind.
And oh, by the way, thank you for taking care of the regression of "3
1 . 1 2 ." now solved.
Michael
On 24.4.2013, at 10:31, Bastien wrote:
> Carsten Dominik writes:
>
>> On 24.4.2013, at 10:06, Bastien wrote:
>>
>>> Hi Michael,
>>>
>>> Michael Brand writes:
>>>
Yes, this is how it worked and I was used to before too, very
convenient.
>>>
>>> This is how it works again.
>>
>>
On Wed, Apr 24, 2013 at 10:43 AM, Michael Brand
wrote:
> (= (point) (1+ (length prompt))) would be a regression of "3 1 . 1 2 .".
Sorry, it is not a regression when reloading lisp properly and not
only with eval-buffer of org.el. Would be ok for me if not echoing "."
at the beginning is intended.
Michael Brand writes:
> On the other side the current (= (char-before) ?.) does still not echo
> the "." at the beginning which I found convenient but don't insist if
> there is a reason for not to echo.
I have no strong opinion on this, but I think it's better if "." does
one single thing at th
On Wed, Apr 24, 2013 at 10:31 AM, Bastien wrote:
> Carsten Dominik writes:
> [...]
>> How about testing for
>>
>>(= (point) (1+ (length prompt)))
>>
>> instead of
>>
>>(= (char-before) 32)
>>
>> ?
>>
>> - Carsten
>
> Yep, as you wish -- I though it was somehow nice to still be able to
> q
Carsten Dominik writes:
> On 24.4.2013, at 10:06, Bastien wrote:
>
>> Hi Michael,
>>
>> Michael Brand writes:
>>
>>> Yes, this is how it worked and I was used to before too, very
>>> convenient.
>>
>> This is how it works again.
>
> How about testing for
>
>(= (point) (1+ (length prompt
On 24.4.2013, at 10:06, Bastien wrote:
> Hi Michael,
>
> Michael Brand writes:
>
>> Yes, this is how it worked and I was used to before too, very
>> convenient.
>
> This is how it works again.
How about testing for
(= (point) (1+ (length prompt)))
instead of
(= (char-before) 32)
Hi Michael,
Michael Brand writes:
> Yes, this is how it worked and I was used to before too, very
> convenient.
This is how it works again.
Thanks for insisting on this!
--
Bastien
On Thu, Apr 4, 2013 at 3:18 PM, Karl Voit wrote:
> [...]
> AFAIR I was able to use "." (to jump to $today) *and*
> type "31.12." (without C-q . or similar) before.
>
> So in my opinion, it is not interfering at all: It can be solved by
> interpreting "." (as goto-today) *only* if nothing else has
Hi Bastien,
* Bastien [04. Apr. 2013]:
> Karl Voit writes:
>> A couple of weeks ago[1] the datepicking dialog got modified such
>> that a dot "." jumps to the current day. Handy for most Org-mode
>> users I guess.
>
> "." is also the character used in M-x calendar RET to jump to today's
> date.
* Bastien wrote:
> Hi Karl,
Hi Bastien!
> Karl Voit writes:
>
>> A couple of weeks ago[1] the datepicking dialog got modified such
>> that a dot "." jumps to the current day. Handy for most Org-mode
>> users I guess.
>
> "." is also the character used in M-x calendar RET to jump to today's
> da
Hi Karl,
Karl Voit writes:
> A couple of weeks ago[1] the datepicking dialog got modified such
> that a dot "." jumps to the current day. Handy for most Org-mode
> users I guess.
"." is also the character used in M-x calendar RET to jump to today's
date.
> However, this interferes with another
Hi!
A couple of weeks ago[1] the datepicking dialog got modified such
that a dot "." jumps to the current day. Handy for most Org-mode
users I guess.
However, this interferes with another feature I used quite often: I
was able to enter "31.12." to quickly select 31st of December, for
example.
Pl
15 matches
Mail list logo
