On Thu, 26 Oct 2023 at 10:34, Martin Michlmayr wrote:
> * Vishesh Handa [2023-10-26 10:27]:
> > 2022-03-10 * "Test"
> > Expenses:B 42.0 EUR
>
> Why don't you change this to 42.00 EUR and everything will work the
> way you expected.
>
Thank you.
T
Expenses:A 117.92 EUR
Assets:P-159.98 EUR
test.beancount:72: Transaction does not balance: (0.06 EUR)
2022-03-10 * "Test .04"
Expenses:B 42.0 EUR
Expenses:A 118.04 EUR
Assets:P-159.98 EUR
Adding a `option "inferred_tolerance_default" "
https://bugs.kde.org/show_bug.cgi?id=331932
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|stefan.bruens@rwth-aachen.d
the license of the Beancount v3 parser that generates
> protobufs may have anything to do with you being able to test a
> different implementation of the parser against it. The license of
> Beancount would matter only if you were to redistribute Beancount code,
> not if use it to as a r
e
"new core" part of Beancount with the protobufs only has Martin as a
contributor, so that part should be straightforward, and that way I
can easily test my parser by making it generate the same protobufs.
--
Vishesh Handa
[1] https://gitjournal.io
[2]
https://opensource.stackexchang
vhanda added a comment.
Sorry. I'm removing myself as a reviewer. I barely remember this code base.
It has been way too many years.
REPOSITORY
R114 Plasma Addons
REVISION DETAIL
https://phabricator.kde.org/D27070
To: alex, #plasma
Cc: vhanda, plasma-devel, Orage, LeGast00n, The-Feren-OS
or underscore, will all of
them I get an 'Error: Invalid date'.
--
Vishesh Handa
--
---
You received this message because you are subscribed to the Google Groups
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ledger-cli
On Sun, Mar 18, 2018 at 10:42 PM, jungle boogie wrote:
> Thus said Vishesh Handa on Sun, 18 Mar 2018 06:22:00 -0700 (PDT)
>>
>>
>> * For now how do people generally store the time? I was planning on
>> storing
>> it as a "Metadata value".
>>
>&
mately map my transaction data with my location data. It's also
useful for trading accounts with many transactions a day.
--
Vishesh Handa
--
---
You received this message because you are subscribed to the Google Groups
"Ledger" group.
To unsubscribe from this group and stop
vhanda added a comment.
In https://phabricator.kde.org/D9712#191746, @ltoscano wrote:
> May I observe that relying on the command line output is fragile in the
best case?
> Unless the command can produce the output in some formatted way (like the
openstack CLI, which can enable a spe
vhanda added a comment.
To give some history - Strigi used to do this guessing, and when I
implemented KFileMetaData, I decided to do the same. I don't have an opinion on
whether it is a good idea or not.
REPOSITORY
R286 KFileMetaData
REVISION DETAIL
https://phabricator.kde.org/D8007
T
vhanda added a comment.
> @vhanda do you know if there is something to do to update Baloo database
when metadata returned by KFileMetaData are changed even if the file itself did
not change ?
I'm starting to forget the code base and what all I implemented. But I don't
think such a thing
vhanda accepted this revision.
vhanda added a comment.
This revision is now accepted and ready to land.
Looks good.
Maybe we should wait and see if someone who works on Dolphin has an opinion.
This widget is only used in Dolphin.
REPOSITORY
R824 Baloo Widgets
BRANCH
origin_url_38626
vhanda added a comment.
Since I was added as a reviewer, I thought I'll comment.
I am not currently maintaining Baloo or using it, so I don't want to really
discuss the specifics. Though from a technical point of view this change will
work. If nobody has any objections, I would say go fo
vhanda accepted this revision.
vhanda added a comment.
This revision is now accepted and ready to land.
This is awesome. Good work.
Ship it! (If you don't have commit access, please ask for it, you can add me
as a reference)
(Optionally, one could even add a unit test)
REPOSITORY
https://bugs.kde.org/show_bug.cgi?id=377720
Bug ID: 377720
Summary: Variable names in comments are highlighted
Product: kdev-python
Version: 5.0.3
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
vhanda added a comment.
I'm not the maintainer of Baloo any more, so I don't want to give it a clear
Yes / No.
This patch is going to be a big CPU hog. For files this will barely have an
impact, but for folders of a large enough size, it's going to result in tons of
dbus signals, and mo
w.r.t the EventLoop.
Diffs
-
autotests/convertertest.h 8129a48
autotests/convertertest.cpp ae4298e
src/currency.cpp 715233c
Diff: https://git.reviewboard.kde.org/r/122183/diff/
Testing
---
Test now passes.
Thanks,
Vishesh Handa
https://bugs.kde.org/show_bug.cgi?id=332421
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
ith this.
I've already expressed my opinion. You all are free to make a decision.
--
Vishesh Handa
On Fri, Oct 7, 2016 at 8:08 PM, Christoph Cullmann wrote:
>
> I did experiments and search works with tracker, but yes, a problem is
> tagging,+
> which ATM doesn't work. Nor do I say that is a ready solution now, just a
> possibility
> to avoid having to maintain low level code with at most 1 p
we want instant feedback. This was an integral requirement.
> I doubt e.g. tracker has different requirements, as it is used in similar
> places by GNOME.
>
> But all that left besides, have you an proposal how to fixup the current
> situation?
> Are you willing to invest some work to fix the current issues or an idea what
> would be a good way to tackle them?
>
I probably will not work more in Baloo.
I'll have to investigate the problems a bit more. From the cursory
look of this thread, it doesn't seem that the problems are that dire.
But I may not be reading into it correctly.
--
Vishesh Handa
.
An analogy could be that we get commit emails, but we get to choose
which projects we are interested in. We don't make everyone subscribe
to kde-commits, and then put their own complex filters on top.
--
Vishesh Handa
eview requests.
It was just too much noise for me, and I found the noise/signal ratio
way lower in kde-devel. Baloo-devel was specifically not chosen as it
would just an another silo in kde. Nepomuk used to suffer from that.
--
Vishesh Handa
.
An analogy could be that we get commit emails, but we get to choose
which projects we are interested in. We don't make everyone subscribe
to kde-commits, and then put their own complex filters on top.
--
Vishesh Handa
eview requests.
It was just too much noise for me, and I found the noise/signal ratio
way lower in kde-devel. Baloo-devel was specifically not chosen as it
would just an another silo in kde. Nepomuk used to suffer from that.
--
Vishesh Handa
On Fri, Oct 7, 2016 at 5:57 PM, Kevin Funk wrote:
> On Friday, 7 October 2016 17:24:26 CEST Vishesh Handa wrote:
>> Hey guys
>>
>> I was told there is a thread about scrapping Baloo. All Baloo
>> discussion used to happen on kde-devel and that's where the revi
On Fri, Oct 7, 2016 at 5:57 PM, Kevin Funk wrote:
> On Friday, 7 October 2016 17:24:26 CEST Vishesh Handa wrote:
>> Hey guys
>>
>> I was told there is a thread about scrapping Baloo. All Baloo
>> discussion used to happen on kde-devel and that's where the revi
ly taken.
How about requirements such as resource consumption, ease of
integration, search speed are taken into consideration? Come on guys.
We're engineers over here.
(If the discussion continues on kde-frameworks-devel, I probably won't see it)
--
Vishesh Handa
ly taken.
How about requirements such as resource consumption, ease of
integration, search speed are taken into consideration? Come on guys.
We're engineers over here.
(If the discussion continues on kde-frameworks-devel, I probably won't see it)
--
Vishesh Handa
On Oct 7, 2016 12:07, "Martin Bednar" wrote:
>
> Hi,
>
> thanks for answering.
>
> On Friday, 7 October 2016 10:44:02 CEST Vishesh Handa wrote:
> > Hey Martin
> >
> > Baloo is only designed for searching for files. It is not a meta-data
> > st
additional context. Therefore, adding actor information, is not
something I would want to ship.
--
Vishesh Handa
On Fri, Sep 30, 2016 at 9:47 PM, Martin Bednar wrote:
> Hi,
>
> having very fond memories of the potential I saw in the tvshows://
> experimental kioslave (from the days of n
https://bugs.kde.org/show_bug.cgi?id=333652
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
On Mon, Sep 19, 2016 at 1:11 PM, Boudhayan Gupta wrote:
> Hi,
>
> On 19 Sep 2016 4:34 p.m., "Vishesh Handa" wrote:
>> >> If someone else wants to maintain it, I can help with the transition.
>
> I have a ton of questions; I'll send you a list sometime
On Mon, Sep 19, 2016 at 11:43 AM, Bhushan Shah wrote:
> Hey Vishesh,
>
> On Mon, Sep 19, 2016 at 3:06 PM, Vishesh Handa wrote:
>> I've been steadily loosing motivation to work on Baloo.
>>
>> I've removed myself from all the bugs, as it doesn't seem like
On Mon, Sep 19, 2016 at 11:43 AM, Bhushan Shah wrote:
> Hey Vishesh,
>
> On Mon, Sep 19, 2016 at 3:06 PM, Vishesh Handa wrote:
>> I've been steadily loosing motivation to work on Baloo.
>>
>> I've removed myself from all the bugs, as it doesn't seem like
If someone else wants to maintain it, I can help with the transition.
--
Vishesh Handa
If someone else wants to maintain it, I can help with the transition.
--
Vishesh Handa
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/128892/#review99115
---
Ship it!
This is awesome. Ship it.
- Vishesh Handa
On
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/128892/#review99115
---
Ship it!
This is awesome. Ship it.
- Vishesh Handa
On
> On Aug. 19, 2016, 8:52 a.m., Vishesh Handa wrote:
> > Could you please attach some screenshots of the before and after?
>
> James Smith wrote:
> I don't think it's really necessary, the existing indexed tag was erased
> if a tag higher up was selected, or
t;
So if we only have tag in the form -
"Fire/Water"
at that point unless one also has the tag "Fire", it will just never show
up.
- Vishesh Handa
On Aug. 20, 2016, 10:58 p.m., James Smith wrote:
>
>
hard to reason what
is going on.
Eg - `baloosearch 'tag:Death Fire'` and `baloosearch tag:Death Fire` now yield
different results since "Fire" is considered part of the tag in the first query.
I would rather not ship this.
- Vishesh Handa
On Aug. 24, 2016, 3:26 p.m
time post Wednesday to
actually try all your patches out.
- Vishesh Handa
On Aug. 24, 2016, 3:26 p.m., James Smith wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard
https://bugs.kde.org/show_bug.cgi?id=173668
Vishesh Handa changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
after?
- Vishesh Handa
On Aug. 19, 2016, 12:05 a.m., James Smith wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.
don't understand it.
From a cursory glance it seems that this code will assert. `q` is of type
`EngineQuery::Phrase` and is a leaf query so `Transaction::PostingIterator`
will assert it `Q_ASSERT(0)`
- Vishesh Handa
On Aug. 18, 2016, 11:56 p.m., James Smith wrote:
>
>
vhanda accepted this revision.
vhanda added a comment.
This revision is now accepted and ready to land.
Looks good.
REPOSITORY
rMILOU Milou
REVISION DETAIL
https://phabricator.kde.org/D2395
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/
To: broulik, #pl
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/128554/#review97999
---
Ship it!
Ship It!
- Vishesh Handa
On July 29, 2016, 5
https://bugs.kde.org/show_bug.cgi?id=341990
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=352494
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
e completion of each run. As such a broken blog can
> cause some problems.
What kind of problems?
I'm guessing it would just be ignored and eventually over time we can
remove ones which have been broken for a very long time.
--
Vishesh Handa
_
e completion of each run. As such a broken blog can
> cause some problems.
What kind of problems?
I'm guessing it would just be ignored and eventually over time we can
remove ones which have been broken for a very long time.
--
Vishesh Handa
https://bugs.kde.org/show_bug.cgi?id=365753
Vishesh Handa changed:
What|Removed |Added
CC|m...@vhanda.in|
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=365753
Vishesh Handa changed:
What|Removed |Added
CC|m...@vhanda.in|
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=364480
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=353696
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=211409
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=355273
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=364579
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=360903
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=360838
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=363552
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=351467
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=364315
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=361663
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=364993
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=364353
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=346522
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=358667
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=358998
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=358797
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=344749
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=363973
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=340283
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=355232
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=355446
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=364471
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=360587
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=361912
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=362621
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=350124
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=358179
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=356333
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=351450
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=349408
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=344328
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=360932
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=357043
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=358805
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=355213
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=350125
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=351000
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=363282
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|k...@privat.broulik.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=353848
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=359057
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|kdepim-b...@kde.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=333823
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|kdepim-bugs@kde.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=361259
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=333823
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|kdepim-b...@kde.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=333743
Vishesh Handa changed:
What|Removed |Added
Assignee|m...@vhanda.in|pinak.ah...@gmail.com
--
You are receiving
1 - 100 of 3066 matches
Mail list logo