Set strings.xml as the default at the first option of the popup. [315524924]

Bug

Reviewed (L1)

Migrated-Tools-editing

Status Update

No update yet.

Description

ng...@gmail.com

created issue #1

Dec 9, 2023 02:22AM

Android Studio Iguana | 2023.2.1 Canary 17

STEPS TO REPRODUCE:
1. Pres shortcut Shift + Command + O to open File
2. Type 'strings.xml"
3. If the app localized more than 10 languages, the default strings.xml is showed at very bottom and I have to scroll to see it.

Expect result:
the default strings.xml should always show at the top. Most of time devs want to open defaults strings.xml instead opening others localized strings.

------------------

Screenshot 2023-12-08 at 9.41.35 AM.png

268 KB

View

Download

Comments

sr...@google.com <sr...@google.com> Dec 11, 2023 08:30PM

Assigned to an...@google.com.

an...@google.com <an...@google.com> #2Dec 12, 2023 06:59PM

I don't think the IntelliJ platform allows us to customize the order of search results. Platform team, can you weigh in?

ya...@google.com <ya...@google.com> #3Dec 12, 2023 08:18PM

Thanks for your request. We will investigate this issue and see if we can implement the behavior you've requested.

an...@google.com <an...@google.com> #4Dec 14, 2023 06:04PM

Status: New

As an additional alternative, it should be possible to specify a label in the options for GmailApp.sendEmail().

A work-around is proposed in StackOverflow:

http://stackoverflow.com/a/18727687/1677912

an...@google.com <an...@google.com> Jan 2, 2024 09:38PM

Assigned to kd...@google.com.

kd...@google.com <kd...@google.com> #5Jan 2, 2024 10:43PM

Are there any news on adding the ability to archive and add a label to specific emails (not threads)? From a corporate shared mailbox perspective auto threading emails by subject is a serious issue (eg. we recive two emails from the same person with same subject but with different description).

Since it's available in pure mailbox view is that such a big effort to make it available also in Google Script?

Tue Jan 02 2024 14:42:54 GMT-0800 (Pacific Standard Time).png

97 KB

View

Download

ng...@gmail.com <ng...@gmail.com> #6Jan 3, 2024 02:32AM

Looking forward to having this implemented. As has been mentioned automatic threading based on subject is a big no-no for our enterprise. We get automated reports and other documents sent to us by customers and suppliers and they are lumped together in threads making it very difficult for me to let Apps Script process them automatically since labels (i.e. outlook folders) have to be applied to entire threads (even though the messages in these threads often need to be treated differently).

kd...@google.com <kd...@google.com> #7Jan 3, 2024 07:15PM

Please add this function (and message.getlabel too) we need to scan message not only the thread.

kd...@google.com <kd...@google.com> #8Jan 3, 2024 08:54PM

Will there be any progress on this issue? Threading is great for humans, but if you are scripting, accessing and manipulating individual messages is MUCH more important, especially if it can be done from the normal user interface. Anything you can do to the thread you should be able to do at the message level.

kd...@google.com <kd...@google.com> #9Jan 3, 2024 09:11PM

Unassigning

kd...@google.com <kd...@google.com> #10Jan 3, 2024 09:12PM

Reassigned to bu...@google.com.

Activate advanced google services/gmail api and use the gmail api functions.
I have resolved the same issue :)

Message last modified on Jan 3, 2024 09:14PM

bu...@google.com <bu...@google.com> #11Jan 3, 2024 10:18PM

Accepted by bu...@google.com.

Thanks!

bu...@google.com <bu...@google.com> #12May 1, 2024 07:06PM

Assigned to kd...@google.com.

The advanced service provides this functionality.

an...@google.com <an...@google.com> #13May 17, 2024 06:17PM

Reassigned to bu...@google.com.

Bugjuggler: https://youtrack.jetbrains.com/issue/IDEA-232305/Go-to-file-ranks-exact-match-at-the-bottom

bu...@google.com <bu...@google.com> #14May 17, 2024 06:18PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://youtrack.jetbrains.com/issue/IDEA-232305 to be resolved and then assign the bug to kdresner@google.com.

bu...@google.com <bu...@google.com> Jul 18, 2024 09:57AM

Assigned to kd...@google.com.

kd...@google.com <kd...@google.com> #15Jul 23, 2024 06:21PM

My guess is that this is fixed now that the underlying IJ issue is fixed. I am going to juggle this for a little longer until we get this downstreamed into AS.

kd...@google.com <kd...@google.com> #16Jul 23, 2024 06:21PM

Reassigned to bu...@google.com.

Bugjuggler: Q4 2024

bu...@google.com <bu...@google.com> #17Jul 23, 2024 06:21PM

Reassigned to kd...@google.com.

Something went wrong parsing your comment: Unexpected "Q4" when parsing obstacle. See

http://go/bugjuggler#how-to-use-it for examples.
Error highlighted: Bugjuggler: *Q4* 2024

kd...@google.com <kd...@google.com> #18Jul 23, 2024 06:22PM

Reassigned to bu...@google.com.

Bugjuggler: wait until next quarter

bu...@google.com <bu...@google.com> #19Jul 23, 2024 06:23PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait until 2024-10-01 00:00 -0700 PDT and then assign the bug to kdresner@google.com.

bu...@google.com <bu...@google.com> Oct 1, 2024 07:02AM

Assigned to kd...@google.com.

kd...@google.com <kd...@google.com> #20Oct 25, 2024 09:08PM

Reassigned to gh...@google.com.

We're going to try re-enabling the search everywhere ML plugin to see if that addresses this.

lb...@gmail.com <lb...@gmail.com> #21Oct 25, 2024 09:21PM

@20 Why the need to have ML/AI for this? It's just sorting by what's the default first, especially if we specifically write it...

kd...@google.com <kd...@google.com> #22Oct 25, 2024 09:25PM

@21 because IJ only fixed it for the case where that plugin is enabled. See https://youtrack.jetbrains.com/issue/IDEA-232305

So our options are

Re-enable the plugin and see if that works or
Try to get IJ to fix it for the case where the plugin is not present and then wait for that fix to merge into Android Studio

lb...@gmail.com <lb...@gmail.com> #23Oct 25, 2024 10:49PM

@22 So are you saying that it only started when AI/ML was added to the IDE, and that if I disable it somehow, it will show default strings as first item on the list?

Pretty sure this issue existed way before.

kd...@google.com <kd...@google.com> #24Oct 28, 2024 05:41PM

I am not saying that.

lb...@gmail.com <lb...@gmail.com> #25Oct 28, 2024 06:34PM

@24 So what are you saying?

The issue has existed before AI was used for this. Right?

How would AI be related here, if the issue has existed before?

el...@gmail.com <el...@gmail.com> #26Oct 28, 2024 07:03PM

FWIW I originally reported this

issue 9

years ago (

https://issuetracker.google.com/issues/37068695) and recently was merged into this ticket.

I'd be surprised if that linked IntelliJ ticket is related to this since multiple "exact matches" of `strings.xml` will exist, and the secondary sort is the issue at stake. So even if that issue is fixed and the exact match is shown first, this issue has always been about showing the default exact match first when multiple overrides exist. The ticket also mentions it being a recent regression and I don't believe this was ever fixed, I've just been scrolling to the bottom throughout the years ;_;.

kd...@google.com <kd...@google.com> #27Oct 28, 2024 07:16PM

comment#25 Correct, it has existed before the Search Everywhere ML plugin was created. When JB addressed the linked YouTrack issue, they fixed it by making changes to that plugin, so it is only "fixed" for cases where that plugin is enabled. Since Android Studio has not used that plugin by default, it remains unfixed in Android Studio. Thus as mentioned in comment#22, our options to get it fixed are either to enable the plugin or continue to lobby JB to fix it in the general case.

lb...@gmail.com <lb...@gmail.com> #28Oct 28, 2024 07:27PM

@27 Guys it should be possible to fix whether it's using or used AI or not.

The list is sorted in some way. Just prioritize the one that's the default to be at the top.

gh...@google.com <gh...@google.com> Oct 28, 2024 07:29PM

Reassigned to kd...@google.com.

kd...@google.com <kd...@google.com> Oct 28, 2024 08:44PM

Status: New

Issue 315524924

Description

Issue summary

Comments

sr...@google.com <sr...@google.com> Dec 11, 2023 08:30PM

an...@google.com <an...@google.com> #2Dec 12, 2023 06:59PM

ya...@google.com <ya...@google.com> #3Dec 12, 2023 08:18PM

an...@google.com <an...@google.com> #4Dec 14, 2023 06:04PM

an...@google.com <an...@google.com> Jan 2, 2024 09:38PM

kd...@google.com <kd...@google.com> #5Jan 2, 2024 10:43PM

ng...@gmail.com <ng...@gmail.com> #6Jan 3, 2024 02:32AM

kd...@google.com <kd...@google.com> #7Jan 3, 2024 07:15PM

kd...@google.com <kd...@google.com> #8Jan 3, 2024 08:54PM

kd...@google.com <kd...@google.com> #9Jan 3, 2024 09:11PM

kd...@google.com <kd...@google.com> #10Jan 3, 2024 09:12PM

bu...@google.com <bu...@google.com> #11Jan 3, 2024 10:18PM

bu...@google.com <bu...@google.com> #12May 1, 2024 07:06PM

an...@google.com <an...@google.com> #13May 17, 2024 06:17PM

bu...@google.com <bu...@google.com> #14May 17, 2024 06:18PM

bu...@google.com <bu...@google.com> Jul 18, 2024 09:57AM

kd...@google.com <kd...@google.com> #15Jul 23, 2024 06:21PM

kd...@google.com <kd...@google.com> #16Jul 23, 2024 06:21PM

bu...@google.com <bu...@google.com> #17Jul 23, 2024 06:21PM

kd...@google.com <kd...@google.com> #18Jul 23, 2024 06:22PM

bu...@google.com <bu...@google.com> #19Jul 23, 2024 06:23PM

bu...@google.com <bu...@google.com> Oct 1, 2024 07:02AM

kd...@google.com <kd...@google.com> #20Oct 25, 2024 09:08PM

lb...@gmail.com <lb...@gmail.com> #21Oct 25, 2024 09:21PM

kd...@google.com <kd...@google.com> #22Oct 25, 2024 09:25PM

lb...@gmail.com <lb...@gmail.com> #23Oct 25, 2024 10:49PM

kd...@google.com <kd...@google.com> #24Oct 28, 2024 05:41PM

lb...@gmail.com <lb...@gmail.com> #25Oct 28, 2024 06:34PM

el...@gmail.com <el...@gmail.com> #26Oct 28, 2024 07:03PM

kd...@google.com <kd...@google.com> #27Oct 28, 2024 07:16PM

lb...@gmail.com <lb...@gmail.com> #28Oct 28, 2024 07:27PM

gh...@google.com <gh...@google.com> Oct 28, 2024 07:29PM

kd...@google.com <kd...@google.com> Oct 28, 2024 08:44PM

Add comment

Issue metadata